CompuServe Messages

I was very confused last night… I was convinced I'd stripped the machine's config and autoexec down to nothing (null files) and I'd run the MOUSE.COM and still I'd get no movement. This new office computer came with DOS 6.21, which I've never installed here before, so I decided to re-install DOS 5.0 (as well as undergoing the tedious "emergency repair" of the boot loader because this machine also has WinNT on it.) Wow, even that didn't make it go away, but at least I could boot with null config and autoexec and run MOUSE and I would get mouse movement. (I know I was twiddling two variables at once here, but heh, I'm a scientist. 🙂 Through process of elimination on the autoexec, I discovered a line 'set SERIALDEBUG=00' that had migrated from the autoexec on a development machine. Yes, new rodent was on COM1. Yes, that machine was running 3DS v3.1.5 $$$. Problem solved, left as an exercise to the IPAS-savvy reader. 🙂 It works now. Gentle Public, suffice it to say that this bug will never appear on consumer machines, it's a developer-specific virus. Jonas, add it to the log book.