VOGONS


First post, by webodan

User metadata
Rank Newbie
Rank
Newbie

Hello everyone,

I've recently acquired an i440ZX based motherboard (it's DTK PRM-0080I ZX with BIOS version 1.02), and I wanted to use something better than those old spotty IDE hard drives, since this motherboard will for some reason not detect some hard drives while other mobos did.

I ended up going with a Silicon Image Sil3512A-based PCI SATA RAID card connected to a 120GB SSD that I had lying around ,and after reading around this forum and googling for a while, I managed to flash the proper SATALink bios to this card, and got a SATALink driver for my Windows 98 installation. Booting up the SSD and all was smooth sailing from there as well. Just to make sure, I flashed using both UPDFLASH and flashrom on DOS.

My problem is that I just can't get Windows to stop using Compatibility mode. You know, this "Drive X is using compatibility mode" thingy, although I did install the 440zx chipset drivers i found in philscomputerlab's web page, and the relevant SATALink Win98 driver. I don't see any warnings in Device Manager either.

How do I go about solving this issue? there's nothing in my AUTOEXEC.BAT (apart from setver) or in my CONFIG.SYS that could be conflicting, as per the Help system claims could be the cause I cleaned those up just in case, but nothing.

I also installed the NOIDE.inf file in the utilities folder of the WIN98 CD, since some web site said that this could be what caused the problem. No dice.

Reply 1 of 6, by darry

User metadata
Rank Oldbie
Rank
Oldbie
webodan wrote on 2020-05-23, 02:36:
Hello everyone, […]
Show full quote

Hello everyone,

I've recently acquired an i440ZX based motherboard (it's DTK PRM-0080I ZX with BIOS version 1.02), and I wanted to use something better than those old spotty IDE hard drives, since this motherboard will for some reason not detect some hard drives while other mobos did.

I ended up going with a Silicon Image Sil3512A-based PCI SATA RAID card connected to a 120GB SSD that I had lying around ,and after reading around this forum and googling for a while, I managed to flash the proper SATALink bios to this card, and got a SATALink driver for my Windows 98 installation. Booting up the SSD and all was smooth sailing from there as well. Just to make sure, I flashed using both UPDFLASH and flashrom on DOS.

My problem is that I just can't get Windows to stop using Compatibility mode. You know, this "Drive X is using compatibility mode" thingy, although I did install the 440zx chipset drivers i found in philscomputerlab's web page, and the relevant SATALink Win98 driver. I don't see any warnings in Device Manager either.

How do I go about solving this issue? there's nothing in my AUTOEXEC.BAT (apart from setver) or in my CONFIG.SYS that could be conflicting, as per the Help system claims could be the cause I cleaned those up just in case, but nothing.

I also installed the NOIDE.inf file in the utilities folder of the WIN98 CD, since some web site said that this could be what caused the problem. No dice.

That is strange .

On the off chance you have missed something significant , would you mind sharing the contents of your autoexec.bat and config.sys, just in case ?

Also how many drives do how have connected and do they all show up as using compatibility mode .?

Reply 2 of 6, by Horun

User metadata
Rank Oldbie
Rank
Oldbie

Curious, you say you had issues with regular IDE drives on that motherboard ? When you switched to the PCI SATA card did you disable the onboard IDE ? It is possible that even if you did the drivers for the onboard IDE are still being loaded. Win98 is not a very smart OS and you could have a driver conflict which flagged the Compatibilty mode. I remember having a bad IDE CDROM under Win98 and it reverted to compat mode and could not clear it even after replacing the cdrom with a working one. Took some reg fix but am tired and cannot recall exact what was needed...

Hate posting a reply and have to edit it because it made no sense 😁 First computer was an IBM 3270 workstation with CGA monitor. 🤣

Reply 3 of 6, by darry

User metadata
Rank Oldbie
Rank
Oldbie

According to https://www.techrepublic.com/article/solve-ms … eshooting-tips/

another scenario is a boot sector virus .

I would add to that the presence of an old DDO (dynamic drive overlay) on the SSD as another scenario .

Reply 5 of 6, by webodan

User metadata
Rank Newbie
Rank
Newbie
Horun wrote on 2020-05-23, 03:21:

Curious, you say you had issues with regular IDE drives on that motherboard ? When you switched to the PCI SATA card did you disable the onboard IDE ? It is possible that even if you did the drivers for the onboard IDE are still being loaded. Win98 is not a very smart OS and you could have a driver conflict which flagged the Compatibilty mode. I remember having a bad IDE CDROM under Win98 and it reverted to compat mode and could not clear it even after replacing the cdrom with a working one. Took some reg fix but am tired and cannot recall exact what was needed...

All right, gonna check that up...

I've just tried disabling the IDE controller on the BIOS (I remember disabling it from the Device Manager itself before, but yeah, maybe it's not as effective as doing it on the BIOS). I can see it is disabled since the IDE Bus Master device inside the Hard Disk Controllers section says it is disabled. Good. So then I check out the Performance section under System and..... nope, still using MS-DOS compatibility mode.

darry wrote on 2020-05-23, 03:10:

That is strange .

On the off chance you have missed something significant , would you mind sharing the contents of your autoexec.bat and config.sys, just in case ?

Also how many drives do how have connected and do they all show up as using compatibility mode .?

Sure, I'm going to check them up again, hold on....

Nope, as I said before, both autoexec.bat and config.sys are empty of any relevant files. I even removed my 2 sound cards while trying to remove any conflicts that I could be having.

The system is as bare as it could be (just a video card, a network card and the SATA card).

I've only got the SSD and then an IDE DVD-ROM that I used to install windows into. Actually, good point, I'm gonna try plugging in a spare IDE hard drive that I have as slave on the same channel (since I don't have another 40-pin IDE cable) and see how that goes...

I was able to get my older hard drives with windows 98 installed on them working, but ONLY when I set the jumper in the Capacity Limit pins, so it can only see the first 32 GB of the drives. Why is this? spotty detection when in full size, but perfectly fine in 32GB capacity limit....

Oh, also yeah, running the Win98 installed on this HDD connected to the IDE bus (after letting Windows install the 440ZX chipset drivers on its own) made it run with no compatibility mode!!! so yeah, something about the SIL3512 or the SSD seems to be forcing it to run in compatibility mode.

Is it OK to use the IDE HDD like this? it has a 114 GB partition, and Windows sees the full size of this partition just fine, but in theory it's now capacity-limited to 32GB through the jumper, and it's already 20 GB full. Could it corrupt any data saved beyond 32GB or something? if anyone else knows about this I would be grateful that he'd enlighten me about this deal.

darry wrote on 2020-05-23, 03:25:

According to https://www.techrepublic.com/article/solve-ms … eshooting-tips/

another scenario is a boot sector virus .

I would add to that the presence of an old DDO (dynamic drive overlay) on the SSD as another scenario .

Just saying... I heavily doubt there's a virus here since the system has been barely used at all (couldn't even get to games since the compatibility mode was bugging me all the time).

How do I check for that DDO thing? any way I can disable or remove it? the way I installed 98 on this machine was to let Win98 Setup format the disk by itself after FDISK made a 17 gig (?) partition on the SSD. Then after booting up Setup it formatted that on its own, and went on to installing Windows 98... Just saying, I'm not sure since I haven't got much experience with 98, but maybe it didn't like that?...

Oh, and I also expanded that 17 gig to the full 120 gig size of the SSD, but I did that in gparted, with the SSD plugged into another machine, while I was grabbing drivers for the 440zx and putting them on it, so I could save on wasting CDs for that, since this install of Win98 didn't even have network drivers for this card.

darry wrote on 2020-05-23, 03:35:

Another site with some recommendation that you may or may not have seen/tried .

https://www.cdrinfo.com/Sections/FAQ/SingleQu … QuestionId=1363

Oh! maybe this works, I'm going to try it immediately, and to try isolating things, I'm going to do it with the IDE channels disabled...

OK, so I've just typed in 32BitDiskAccess=On inside of the [386Enh] in SYSTEM.INI, then rebooted (didn't do any of the other things since I've got no weird drivers on them) I was initially hopeful since I didn't have any 32BitDiskAccess string at all on it.... sadly it didn't do it. Windows keeps using compatibility mode. I just tried setting it to Off just in case, then rebooted. Same result. Bummer.

Last edited by webodan on 2020-05-23, 19:48. Edited 8 times in total.

Reply 6 of 6, by webodan

User metadata
Rank Newbie
Rank
Newbie

One more thing I'd like to ask, I want to update the BIOS of this motherboard, since maybe it'll fix this hard drive detection "spottiness" that it has, but AWDFLASH said that the EEPROM chip is write protected, I've checked the manuals of the motherboard and the jumpers but i see no wire-protect pins, only one that gives 5V or 12V to the EEPROM; since I don't want to burn the chip out, I've seen the datasheet of the EEPROM (Winbond W29C020-12) and it says it is a 5-volt only chip, good thing I didn't mess with that.

So I assume that is not the jumper I need to use so I can update this BIOS; is there any way I can unlock it, do I need some specific utility for that (i tried using AWDFLASH)? or is using one of those minipros the only way considering I've got no other motherboard to flash this chip?