VOGONS


First post, by megatron-uk

User metadata
Rank l33t
Rank
l33t

Ok, so I've put my new 486 together (AMD X5 133, Asus PVI486SP3, Matrox Millenium 2, AWE32, XR385, GUS Max, MPU-IPC-T, Ultra ATA controller... the works!) and have transferred the drive that I was using in the previous machine (a Pentium Pro, running Win 98SE in dos-only mode).

I have a small OS/Boot partition (120Mb), with the rest of the (huge) drive partitioned into a couple of large fat32 chunks.

I've done the following from a Win98SE boot floppy to initialise the OS partition and clear out the previous Linux Grub boot loader (the P-Pro dual booted between Linux and Win98-dos)

fdisk /mbr
format c: /s

This gets me a bootable drive and I can copy back the various driver and util directories I made a backup of (SB16, ULTRASND and some UTILS folders with stuff like Norton Utilities, SDD, Sysspeed, Cutemouse etc). Access to the remaining fat32 partitions is fine - all of the games, demos etc previously installed are working without issue.

Everything goes well, until I copy back the config.sys that I was using previously. More specifically, when there is *any* config.sys *at all* I get the Windows 98 startup menu with the following text:

"Warning: Windows has detected a registry/configuration error.
Choose, Command prompt only, and run SCANREG."

It then hangs whichever of the options are chosen.

Now, there is no trace of windows on the drive, and no registry to scan. I've gone so far as to explicitly set bootgui=0 and logo=0 in msdos.sys to always boot straight to dos.

At this point the only recourse to get past the above error is to reboot via floppy and remove msdos.sys and config.sys, of course, this means that next reboot it tries to load windows and shows the Windows 98 splash screen.

Can anyone see anything wrong here?

My collection database and technical wiki:
https://www.target-earth.net

Reply 1 of 4, by megatron-uk

User metadata
Rank l33t
Rank
l33t

Think I may have this solved - checking msdos.sys I removed the [Path] option block, so that only the [Options] block remained. It seems to work now - I guess with that section enabled it then tries to link to some part of the Windows installation to check that necessary files are there.

My collection database and technical wiki:
https://www.target-earth.net

Reply 2 of 4, by megatron-uk

User metadata
Rank l33t
Rank
l33t

Ok. Yet more wierdness.

When booting from floppy, himem.sys loads fine. When booting from hd the system will lock up when encountering "DEVICE=C:\DOS\HIMEM.SYS"

I even copied the config.sys and himem.sys from the floppy to the hd to see if my himem.sys was corrupt - exactly the same thing. Everything else in config.sys is commented out.

I've also tried himem.exe from FreeDos and himemx.exe from Jemm - both result in a system lockup. I would be suspecting memory at this point, if it were not for the fact that without a XMS driver installed, or when booting from floppy with Himem everything works great, including syspeed, cache check, cpuchk, norton si. No other issues.

My collection database and technical wiki:
https://www.target-earth.net

Reply 3 of 4, by megatron-uk

User metadata
Rank l33t
Rank
l33t

And the answer is.....

it's the Sil0680A pci Ultra ATA controller card.

Yep. I have no idea why either. But I've just taken the controller card out, and replaced it with an LSI/AMI/Dell I4 IDE pci raid controller, which, admittedly, with an i960 cpu and 16mb of cache is completely overkill for a 486. But with *no other* changes Himem.sys in my config.sys started loading and booting to the dos prompt.

I'm satisfied that its fixed, but if anyone has an explanation of why the disk controller would make a difference to himem loading, it would be interesting to know!

My collection database and technical wiki:
https://www.target-earth.net