Mumak wrote on 2021-07-05, 07:29:

That's right, MSDOS 7.x is no longer the "good old" real mode DOS as it used to be.
Regarding the wrong CPU clock on VIA Eden, I'd need to see the HWiNFO Report and Debug Files (run HWINFO -r -d) to check what might be wrong.

Yes it is. It just has FAT32 support added. Which is dam handy. There should be a directory on the win98 installation CD called OLD DOS with all the programs prior to Dos 7.1 had. Also the Editor is stand alone, free of BASIC. You do the same tasks as MS/PC Dos 6.x if the software will run on it.

Way back the China Dos Union made a distribution of Dos 7.1 with a ton of freeware utilities.

Your preogram should run on Dos 7.1 exactly the same as prior Dos versions.

IMSs Real32 Dos is a different mater. It is a true 32-bit operating system that can have multiple user unlike PC/MS Dos 7.1 You have the choice of multi-user or single user doing the installation routine. Only one MS Windows 3.x session though. Version 7.92 from 07-01-01 has fat32 support.

MickySoft just decided Dos 7.1 wasn't going to support any cpu below a 386. https://en.wikipedia.org/wiki/MS-DOS_7 There is no reason that 286s a below can't support fat32. I've seen FreeDos compiled kernals to do just that on XT class computers that support the fat32 file system. http://wiki.freedos.org/wiki/index.php/Hardwa … e_compatibility

Disk images http://jorisvr.nl/article/freedos https://sites.google.com/site/rugxulo/

It's really there to boot strap Win 9.x and supply Dos backwards compatibility.

Mumak wrote on 2021-07-06, 14:59:

Thanks. Looks like it doesn't like some of the VGA checks, but it won't be easy to figure out exactly what is causing this.
It should be displaying detection progress at the bottom, are you perhaps able to spot what's shown as the last one?

I did a slow mo capture on the screen from my phone and it does these but after the Matrox one they're so quick it's hard to see!

Checking: Matrox MGA-I, -II, -64
Checking: MOS ?
Checking: Logic ?

Then the screen starts rolling

SteveC wrote on 2021-07-06, 19:54:

I did a slow mo capture on the screen from my phone and it does these but after the Matrox one they're so quick it's hard to see […]
Show full quote

Mumak wrote on 2021-07-06, 14:59:

Thanks. Looks like it doesn't like some of the VGA checks, but it won't be easy to figure out exactly what is causing this.
It should be displaying detection progress at the bottom, are you perhaps able to spot what's shown as the last one?

I did a slow mo capture on the screen from my phone and it does these but after the Matrox one they're so quick it's hard to see!

Checking: Matrox MGA-I, -II, -64
Checking: MOS ?
Checking: Logic ?

Then the screen starts rolling

Thanks, that helps me to narrow down the issue. What graphics adapter is in the system?

Mumak wrote on 2021-07-06, 20:03:

SteveC wrote on 2021-07-06, 19:54:

I did a slow mo capture on the screen from my phone and it does these but after the Matrox one they're so quick it's hard to see […]
Show full quote

Mumak wrote on 2021-07-06, 14:59:

Thanks. Looks like it doesn't like some of the VGA checks, but it won't be easy to figure out exactly what is causing this.
It should be displaying detection progress at the bottom, are you perhaps able to spot what's shown as the last one?

I did a slow mo capture on the screen from my phone and it does these but after the Matrox one they're so quick it's hard to see!

Checking: Matrox MGA-I, -II, -64
Checking: MOS ?
Checking: Logic ?

Then the screen starts rolling

Thanks, that helps me to narrow down the issue. What graphics adapter is in the system?

The IBM PS2 VGA one - no idea what it actually is!

Here are the files of the other 486-DX2-66, the CPU is Cyrix with green heatsink included, 1MB CL GD5424 video card, RAM 30 Pin 8MB total, the L2 cache unfortunately has a problem, despite there being 128kb on-board when is active the PC freezes in the BIOS initial screen (POST card error 96), if instead I deactivate it the PC works even if obviously it loses some performance.
The motherboard is VLB OPTi 486 Model Z4DVP, on the board there is an abbreviation 495SLC REV. T.1, the cache and TAG chips are all 20ns, the 30 PIN RAMs are from a 1MB X8PZ 70ns IBM PC.
The slots are three VLBs, three ISA 16bit and two ISA 8bit, the BIOS is from AMI.

PC@LIVE wrote on 2021-07-06, 20:44:

Here are the files of the other 486-DX2-66, the CPU is Cyrix with green heatsink included, 1MB CL GD5424 video card, RAM 30 Pin 8MB total, the L2 cache unfortunately has a problem, despite there being 128kb on-board when is active the PC freezes in the BIOS initial screen (POST card error 96), if instead I deactivate it the PC works even if obviously it loses some performance.
The motherboard is VLB OPTi 486 Model Z4DVP, on the board there is an abbreviation 495SLC REV. T.1, the cache and TAG chips are all 20ns, the 30 PIN RAMs are from a 1MB X8PZ 70ns IBM PC.
The slots are three VLBs, three ISA 16bit and two ISA 8bit, the BIOS is from AMI.

Thanks, I will add this mainboard into database so next time it shall be recognized. The rest looks OK to me in HWiNFO 😀

Mumak wrote on 2021-07-06, 21:38:

PC@LIVE wrote on 2021-07-06, 20:44:

Here are the files of the other 486-DX2-66, the CPU is Cyrix with green heatsink included, 1MB CL GD5424 video card, RAM 30 Pin 8MB total, the L2 cache unfortunately has a problem, despite there being 128kb on-board when is active the PC freezes in the BIOS initial screen (POST card error 96), if instead I deactivate it the PC works even if obviously it loses some performance.
The motherboard is VLB OPTi 486 Model Z4DVP, on the board there is an abbreviation 495SLC REV. T.1, the cache and TAG chips are all 20ns, the 30 PIN RAMs are from a 1MB X8PZ 70ns IBM PC.
The slots are three VLBs, three ISA 16bit and two ISA 8bit, the BIOS is from AMI.

Thanks, I will add this mainboard into database so next time it shall be recognized. The rest looks OK to me in HWiNFO 😀

I just found the manufacturer from the BIOS line 40-0108-428031 ... the number 428031 corresponds to the manufacturer Zida, in fact the model of the motherboard is precisely Z4DVP, this info is there because I have the original MB booklet .
So I would say a ZIDA Z4DVP. While 495SLC REV. T.1 is silk-screened on the MB, I don't know if it can be considered indicative, but it should be useful if you need to look for the manual to set the jumpers.

SteveC wrote on 2021-07-06, 20:05:

Mumak wrote on 2021-07-06, 20:03:

SteveC wrote on 2021-07-06, 19:54:

I did a slow mo capture on the screen from my phone and it does these but after the Matrox one they're so quick it's hard to see […]
Show full quote

I did a slow mo capture on the screen from my phone and it does these but after the Matrox one they're so quick it's hard to see!

Checking: Matrox MGA-I, -II, -64
Checking: MOS ?
Checking: Logic ?

Then the screen starts rolling

Thanks, that helps me to narrow down the issue. What graphics adapter is in the system?

The IBM PS2 VGA one - no idea what it actually is!

I have created a special build that waits for a key press prior to performing each particular video check. This should make it easy to narrow down which exact test is causing the screen corruption.
Could you please try this build and let me know when it goes wrong:

It would be also useful if you could run the following tool (it will dump BIOS contents) and attach the resulting files:

PC@LIVE wrote on 2021-07-06, 22:11:

Mumak wrote on 2021-07-06, 21:38:

PC@LIVE wrote on 2021-07-06, 20:44:

Here are the files of the other 486-DX2-66, the CPU is Cyrix with green heatsink included, 1MB CL GD5424 video card, RAM 30 Pin 8MB total, the L2 cache unfortunately has a problem, despite there being 128kb on-board when is active the PC freezes in the BIOS initial screen (POST card error 96), if instead I deactivate it the PC works even if obviously it loses some performance.
The motherboard is VLB OPTi 486 Model Z4DVP, on the board there is an abbreviation 495SLC REV. T.1, the cache and TAG chips are all 20ns, the 30 PIN RAMs are from a 1MB X8PZ 70ns IBM PC.
The slots are three VLBs, three ISA 16bit and two ISA 8bit, the BIOS is from AMI.

Thanks, I will add this mainboard into database so next time it shall be recognized. The rest looks OK to me in HWiNFO 😀

I just found the manufacturer from the BIOS line 40-0108-428031 ... the number 428031 corresponds to the manufacturer Zida, in fact the model of the motherboard is precisely Z4DVP, this info is there because I have the original MB booklet .
So I would say a ZIDA Z4DVP. While 495SLC REV. T.1 is silk-screened on the MB, I don't know if it can be considered indicative, but it should be useful if you need to look for the manual to set the jumpers.

Thanks, will adjust this accordingly.

Mumak wrote on 2021-07-06, 22:11:

I have created a special build that waits for a key press prior to performing each particular video check. This should make it e […]
Show full quote

SteveC wrote on 2021-07-06, 20:05:

Mumak wrote on 2021-07-06, 20:03:

Thanks, that helps me to narrow down the issue. What graphics adapter is in the system?

The IBM PS2 VGA one - no idea what it actually is!

I have created a special build that waits for a key press prior to performing each particular video check. This should make it easy to narrow down which exact test is causing the screen corruption.
Could you please try this build and let me know when it goes wrong:
HWINF614.ZIP

It would be also useful if you could run the following tool (it will dump BIOS contents) and attach the resulting files:
GETBIOS.ZIP

When it has "Checking MXIC" on screen then the moment I press space it corrupts the screen. (https://photos.app.goo.gl/H8z5pi33HuhGJkRK9)

ROM files attached!

SteveC wrote on 2021-07-06, 22:50:

Mumak wrote on 2021-07-06, 22:11:

I have created a special build that waits for a key press prior to performing each particular video check. This should make it e […]
Show full quote

SteveC wrote on 2021-07-06, 20:05:

The IBM PS2 VGA one - no idea what it actually is!

I have created a special build that waits for a key press prior to performing each particular video check. This should make it easy to narrow down which exact test is causing the screen corruption.
Could you please try this build and let me know when it goes wrong:
HWINF614.ZIP

It would be also useful if you could run the following tool (it will dump BIOS contents) and attach the resulting files:
GETBIOS.ZIP

When it has "Checking MXIC" on screen then the moment I press space it corrupts the screen. (https://photos.app.goo.gl/H8z5pi33HuhGJkRK9)

ROM files attached!

Thanks, checking now how to fix.. GETBIOS didn't produce a VBIOS file (C000.ROM) ? That would be quite important.

Mumak wrote on 2021-07-07, 07:36:

SteveC wrote on 2021-07-06, 22:50:

Mumak wrote on 2021-07-06, 22:11:

I have created a special build that waits for a key press prior to performing each particular video check. This should make it e […]
Show full quote

I have created a special build that waits for a key press prior to performing each particular video check. This should make it easy to narrow down which exact test is causing the screen corruption.
Could you please try this build and let me know when it goes wrong:
HWINF614.ZIP

It would be also useful if you could run the following tool (it will dump BIOS contents) and attach the resulting files:
GETBIOS.ZIP

When it has "Checking MXIC" on screen then the moment I press space it corrupts the screen. (https://photos.app.goo.gl/H8z5pi33HuhGJkRK9)

ROM files attached!

Thanks, checking now how to fix.. GETBIOS didn't produce a VBIOS file (C000.ROM) ? That would be quite important.

No it doesn't I'm afraid.

However I have noticed a couple things:

1 - if I load normal config.sys so emm386.exe loads (and hwinfo moans) then the screen doesn't go scrolly corruptness, it just goes blank. Not sure if that means anything?

2 - Also if I continue to press a key after the screen corrupts then on the 3rd press the image comes back (saying Checking: Cyrix) then press it again - Checking: Hualon, then press it again and it corrupts and then the PC is fully hung - continued pressing of the space bar eventually beeps once the keyboard buffer is full. A temporary corruption is fine, just need to work out what's freezing the machine.

SteveC wrote on 2021-07-07, 08:26:

No it doesn't I'm afraid. […]
Show full quote

Mumak wrote on 2021-07-07, 07:36:

SteveC wrote on 2021-07-06, 22:50:

When it has "Checking MXIC" on screen then the moment I press space it corrupts the screen. (https://photos.app.goo.gl/H8z5pi33HuhGJkRK9)

ROM files attached!

Thanks, checking now how to fix.. GETBIOS didn't produce a VBIOS file (C000.ROM) ? That would be quite important.

No it doesn't I'm afraid.

However I have noticed a couple things:

1 - if I load normal config.sys so emm386.exe loads (and hwinfo moans) then the screen doesn't go scrolly corruptness, it just goes blank. Not sure if that means anything?

2 - Also if I continue to press a key after the screen corrupts then on the 3rd press the image comes back (saying Checking: Cyrix) then press it again - Checking: Hualon, then press it again and it corrupts and then the PC is fully hung - continued pressing of the space bar eventually beeps once the keyboard buffer is full. A temporary corruption is fine, just need to work out what's freezing the machine.

Thanks! I think I might have a workaround for this issue and I also added a progress bar to the CPU screen where it took most time to scan the chipset.
Please try this build and let me know the result:

Mumak wrote on 2021-07-07, 08:48:

Thanks! I think I might have a workaround for this issue and I also added a progress bar to the CPU screen where it took most ti […]
Show full quote

SteveC wrote on 2021-07-07, 08:26:

No it doesn't I'm afraid. […]
Show full quote

Mumak wrote on 2021-07-07, 07:36:

Thanks, checking now how to fix.. GETBIOS didn't produce a VBIOS file (C000.ROM) ? That would be quite important.

No it doesn't I'm afraid.

However I have noticed a couple things:

1 - if I load normal config.sys so emm386.exe loads (and hwinfo moans) then the screen doesn't go scrolly corruptness, it just goes blank. Not sure if that means anything?

2 - Also if I continue to press a key after the screen corrupts then on the 3rd press the image comes back (saying Checking: Cyrix) then press it again - Checking: Hualon, then press it again and it corrupts and then the PC is fully hung - continued pressing of the space bar eventually beeps once the keyboard buffer is full. A temporary corruption is fine, just need to work out what's freezing the machine.

Thanks! I think I might have a workaround for this issue and I also added a progress bar to the CPU screen where it took most time to scan the chipset.
Please try this build and let me know the result:
HWINF614.ZIP

Yes that progress bar and the video test works fine now! Attached are the report and debug files if you still want them 😀

Cheers,
Steve

Thanks, happy to hear that! 😀

SteveC wrote on 2021-07-06, 14:52:

Mumak wrote on 2021-07-06, 14:40:

SteveC wrote on 2021-07-06, 14:31:

Just ran this on my PS/2 Model 70 and looking good. Can I make one suggestion though - give a little message bottom right when it's working out what to display (like you do when finding machine brand or at the bottom of the screen when looking for dongles in parallel port). This little 386 takes ages to draw some screens 😀 - see here https://photos.app.goo.gl/4Usw6WWfWvowk3G59

Thanks for the feedback, indeed it might need some indication on such machines. Could you please provide the HWiNFO Report + Debug Files for my reference? Don't have many with MCA 😀

I tried but the Video Info page crashes the machine. The CRT does this - https://photos.app.goo.gl/9sYTPLDfk8t3mHyp6, and an LCD panel just says no signal. Attached are the LOG and DBG files.

Sorry to bother again, but I just realized there's one more thing I'd like to improve - identify the PS/2 model. Could you please run the following build with -d switch and attach the DBG file produced? That will give me some more data for this purpose:

Mumak wrote on 2021-07-07, 11:47:

SteveC wrote on 2021-07-06, 14:52:

Mumak wrote on 2021-07-06, 14:40:

Thanks for the feedback, indeed it might need some indication on such machines. Could you please provide the HWiNFO Report + Debug Files for my reference? Don't have many with MCA 😀

I tried but the Video Info page crashes the machine. The CRT does this - https://photos.app.goo.gl/9sYTPLDfk8t3mHyp6, and an LCD panel just says no signal. Attached are the LOG and DBG files.

Sorry to bother again, but I just realized there's one more thing I'd like to improve - identify the PS/2 model. Could you please run the following build with -d switch and attach the DBG file produced? That will give me some more data for this purpose:
HWINF614.ZIP

This one crashes on VGA again? The files are dates 15th June 2021?

OK anyway attached is a debug from the model 70 and model P70 PS/2.

Also on the P70 first run of hwinfo I get a black screen, escape out, run it again it comes up but then crashes hard (needs a power off/on) on system info:

Cheers,
Steve

Oh sorry, I indeed attached old files! Edited the previous post with new package.
On the P70 you'll probably need to disable Reset method 1 and 3.

Mumak wrote on 2021-07-07, 12:31:

Oh sorry, I indeed attached old files! Edited the previous post with new package.
On the P70 you'll probably need to disable Reset method 1 and 3.

Attached from the model 70.

That worked on the P70 I can now get to the info page (and it correctly identifies the P70). I can't do a -r report though as it doesn't remember the disable reset methods.

SteveC wrote on 2021-07-07, 12:46:

Mumak wrote on 2021-07-07, 12:31:

Oh sorry, I indeed attached old files! Edited the previous post with new package.
On the P70 you'll probably need to disable Reset method 1 and 3.

Attached from the model 70.

That worked on the P70 I can now get to the info page (and it correctly identifies the P70). I can't do a -r report though as it doesn't remember the disable reset methods.

Perfect, got the data I needed. Will add this model too 😀 Thanks!