Re:If 16-bit Windows had a single input queue, how did you d...
by th0ma5 on Wednesday November 26, 2014 @01:43PM
(#8663915)
I remember meeting some hackers at their house a friend of mine took me to in the middle of nowhere, and I asked them where they got their software cracks, and they kind of blinked, and showed me the first dual monitor setup I had ever seen in person, with a regular system on the left, and the output of SoftICE on the right. I guess before that I had just assumed lower level things were unknowable, but after that I sure didn't.
Re:If 16-bit Windows had a single input queue, how did you d...
by DrPhish on Wednesday November 26, 2014 @01:58PM
(#8663987)
Was it the old VGA/Hercules combination? That was so badass
It was also the only way to run dual-screen for a while, since it used a different memory region than colour displays. There was literally no way to run multiple colour adapters on the same computer at one point
Re:If 16-bit Windows had a single input queue, how did you d...
by th0ma5 on Wednesday November 26, 2014 @02:03PM
(#8664016)
Man I am just not sure. I had a Hercules green screen / more shades than CGA setup myself, but if it helps I do think both of their screens were color. I know Hercules probably did other stuff, but I guess I think monochrome whenever I think about it, heh. I do believe this was the old DOS version, not the Windows version of SoftICE, although when I was over there seemed was just before the time of Windows 95 possibly.
Re:If 16-bit Windows had a single input queue, how did you d...
by chinpokomon on Thursday November 27, 2014 @02:37AM
(#8666350)
I used the DOS version of SoftICE on a retail Windows 95 machine, to circumvent the upgrade prevention check in Windows 95 OSR2. OSR2 was an OEM only release, but I figured there had to be a way. Setting breakpoints and single stepping through the setup, I discovered that it checked for krnl386.exe. If that for existed, it was considered an upgrade. If you were a clever young hacker, you renamed that file and went ahead with the upgrade.
Re:If 16-bit Windows had a single input queue, how did you d...
by biot on Wednesday November 26, 2014 @03:43PM
(#8664470)
Talk about a blast from the past! Watcom C/C++ with external amber debugging display was the best.
Re:If 16-bit Windows had a single input queue, how did you d...
by zwieback on Wednesday November 26, 2014 @04:17PM
(#8664639)
Watcom was the best - with Dos Extender and 16-32 cross compiler. Worst IDE, though.
Re:If 16-bit Windows had a single input queue, how did you d...
by zwieback on Wednesday November 26, 2014 @02:22PM
(#8664116)
We used SoftICE extensively for driver debugging. I seem to remember a pushbutton that slid into the ISA slot to trigger a NMI but now I'm not quite sure anymore if it was SoftICE or Periscope that had that.
Re:If 16-bit Windows had a single input queue, how did you d...
by kosma on Wednesday November 26, 2014 @07:07PM
(#8665295)
I used to trigger NMI by shorting the first two pins on an empty ISA slot with a screwdriver (conveniently NMI and GND); stopped when the screwdriver slipped once. Thankfully nothing died on that day, but the cascade of sparks convinced me to install a proper button. ;)
Re:If 16-bit Windows had a single input queue, how did you d...
by markbnj on Wednesday November 26, 2014 @08:30PM
(#8665575)
Same, but that was all we used it for. I do recall running into some horrible memory issues on another project (Iona's Orbix, but that's another story) and wishing I had SoftICE to tear it apart with. But for most application issues it was overkill. The existing debugging tools (and 3rd party stuff like Bounds Checker) were usually good enough.
With this bad boy:
http://en.wikipedia.org/wiki/SoftICE