pouët.net

superplek information 2313 glöps

• general:
• level: user
• personal:
• first name: -
• last name: -
• cdcs:
• cdc #1: Teddybear's Revenge by Eclipse [web]
• cdc #2: The nonstop Ibiza experience by orange
• cdc #3: burra by Aardbei [web]
• cdc #4: Hyperventilation by Byterapers [web]
• cdc #5: mechasm by Fairlight [web]
• cdc #6: gaia - poetry of life by Marquee Design [web]

• intro Windows cloaked device by Cactus
• "this shit crashed my w2k so I had to click reset. don't like that all.."
  
  how gay, i'm not the only one.
  
  now mac,
  
  for starters your remark was written in a way that showed off clear tendencies to 'prove me wrong'. besides that, i do not believe that a stable detonator driver will cause a stop error out of itself when treated in a normal way. this way we can easily conclude that the software has triggered by faulty treatment, and the only thing in this situation i'd like to agree with you on, is that the self-protection scheme of the drivers at hand has flaws and/or isn't sufficient.
  
  these still aren't real driver bugs ;)
  
  
• isokadded on the 2002-09-23 10:11:41
• intro Windows cloaked device by Cactus
• oh and p.s, i made my first statement so perhaps the producer of this production could fix a few bugs. besides the kernel stop part, i also experienced 'faulty' graphics output. this is something that can always occur, certainly when it's your first production that's actually being shown to the masses.
  
  so, no diss, just a little signal.
• isokadded on the 2002-09-23 00:52:05
• intro Windows cloaked device by Cactus
• mac, it's pretty damn well possible to trigger kernel stops (these drivers *seem* to be controlled by Direct3D/OGL, which *seems* to be in the hands of a program running in user space, and besides that, i've succesfully tried a few times to trash the Windows 2000 SP1 kernel as hard as i possibly could). A second argument would be the question why other software utilizing either Direct3D or OGL has been running reliably on this personal computer for a long time now.
  
  Either this is stupid coincidence, or it's the software providing the drivers with a few good blows in the stomach.
  
  I'd opt for the latter.
  
  So next time you want to look smart by "dissing" others with theories adapted from the Windows design scheme, which as one of it's targets had to make sure that what happened here indeed was not caused by the software, please doublecheck reality against theory.
  
  And i'm not going to tell other people to shut up in a serious manner. I leave that to other sceners who are quite keen on writing buggy English ;)
  
  
  
  
• isokadded on the 2002-09-23 00:49:49
• intro Windows cloaked device by Cactus
• kernel stop errors are not funny.
  
• isokadded on the 2002-09-22 23:07:04
• demo Windows prospects by Unique [web]
• it si nice
• rulezadded on the 2002-09-21 12:55:06
• demo Windows captured dream team by Plastic [web] & Floppy
• more dxm more colors
• isokadded on the 2002-09-21 02:47:53
• demo Windows captured dream team by Plastic [web] & Floppy
• more dxm more colors
• isokadded on the 2002-09-21 02:47:44
• demo Windows captured dream team by Plastic [web] & Floppy
• sorry for posting twice ;)
• isokadded on the 2002-09-21 01:29:53
• demo Windows captured dream team by Plastic [web] & Floppy
• anyway, thumbs down for:
  - running in the desktop res
  - the bugging nearly-everything
  - the low amount of polies
  - the abusive colors
  - the crash at the end
  
  people did nicer things back in like.. '98? :)
  
  
• sucksadded on the 2002-09-21 01:28:55
• demo Windows captured dream team by Plastic [web] & Floppy
• anyway, thumbs down for:
  - running in the desktop res
  - the bugging nearly-everything
  - the low amount of polies
  - the abusive colors
  - the crash at the end
  
  people did nicer things back in like.. '98? :)
  
  
• isokadded on the 2002-09-21 01:28:55