Ha! (Thank you Chris Matthews for the Ha!) OMG it F'n works!
Okay. The only files that needed to be replaced by the older 98SE backed up files were the set with NETAPI, NETAPI32, NETDI, and NETOS dll's. The sets before that didn't work so I returned the Me files to the System folder.
So, whatever those 98SE versions do is not done properly on 98SE by the Me updated versions.
I did have to update the driver. For each set I updated the driver and at the end of the update it would say I needed to reboot. Then I would boot up to the same unstarted situation. However, the last time with this set of files, it did not ask to reboot. But I needed to so the driver would work. I was pleased to see the modem lights return. The exact message in the Device Manager properties tab for the unworking DCM-202 USB Modem was: "The NDIS.VXD, NTKERN.VXD device loader(s) for this device could not load the device driver. (Code 2) To fix this, click Update Driver to update the device driver."
What does this mean for 98SE2ME? Would not updating these files in 98SE2ME adversly effect anything else? I'm sure if the Me files effected my USB Cable Modem driver this way then other folks would run into the problem as well.
Now, if I could figure out why sometimes when clicking "Add" to add files to a multi-session cdr with Nero 6 Express turns the display off and I need to either ctrl-alt-delete 2x to reboot, or if that doesn't work then reset the tower. And although previously this had made Windows turn my scanner into an Unknown Device, the last time it did not lose a thing. And then Nero worked properly. I was adding the folders BKUP (with the 98SE versions of the dll files) and BKUPME (with the 98SE2ME versions). I wanted to make sure I had them on a cd just in case. (Although that wouldn't have helped in Command Prompt Only Mode, I would have been able to use my Ms-Dos Game Mode shortcut with the cd driver on it if Windows had some problem. I don't know, I thought it best to be prepared.)
Well, it was fun to discover that my HP Recovery Disc worked on my generic Asus SPAX-M motherboard with an HP bios that reads for a Pavilion 4440. My discs came with my first computer, a Pavilion 4430. Apparently the software for both models is the same. The 4440 simply came with a 333MHz K6-2 and 64MB SDRAM whereas my 4430 came with a 300MHz K6-2 and 32MB SDRAM. I'm using a 366 with 256MB Crucial SDRAM now, and a Jaton Video 118 G-Force2 MX400 32MB PCI. I also have a Lite-on DVD-ROM, CDRW Combo drive. PowerDVD 3.0 is the latest that will play DVD's semi-okay. Heh, it struggles to get the video to match up with the lips synch and never really gets it. This MB just can't cope. Everest puts the memory latency at over 700ms! Far worse than anything else on its chart.
I do uninstall nearly everything on the HP disc, but it was fun to see some of the old stuff. And I have a 98SE updates (the $20 thing) cd so that's how I make it 98SE. The HP disc comes with 98Gold. I now have my original computer and 2 Asus SPAX-M boards and also 2 366MHz AMD processors. I mean, the stuff was so cheap (except for the new memory) that I couldn't resist.
Now, I do have a question regarding the HD size. I noticed that the Bios reports my Western Digital 80GB HD as 65,535MB. However, using the updated FDISK Windows does detect the entire drive. To try to negate possible file corruption I only partitioned the whole thing the first time just to see what would happen. I now only have 64,400MB partitioned as a single Fat32 formatted partition. I leave the rest unpartitioned. I'm using the last Bios HP provided for these boards, the Puma 2 1.04 Bios of January 1999. I have a feeling, since it is a Pheonix Bios, it is using that Phoenix workaround instead of Int13. So that's why until the 98SE Service Pack was installed I was getting extremly sluggish file copying whether within the folders on the HD or from CD to HD. It would copy some files, then wait for the HD to catch up, then copy some more. I was like when I used to use GoBack. The system would wait until the HD stopped working before continuing. After the Service Pack and probably the HD over 32GB Microsoft Patch for Pheonix Bios's it probably has, this problem went away.
The question is, did I need to restrict the partition size? Or since Windows and even format at the end recognized the whole thing, is it safe to use the whole drive? The Bios reports the lower number but Windows will see the whole thing if I partition for it. Or did I do right by just setting the partition to a size within the Bios reported number?
And, of course, thanks so much for helping me to get the modem driver working. And I think this helps since you now know that that set of dll files stopped it from working.
This post has been edited by Eck: 10 June 2005 - 06:34 PM