HIMEM and SETVER should load fine on a fresh install, so there is still something wrong here. CHKDSK errors may be caused by incompatibility of you CF card with the XT-IDE: do you have other CF cards of different make or capacity that you can use? Also, you can add a /V switch after HIMEM.SYS in you config.sys, and see if you can get some messages on what himem is doing before the system hangs
- VCF South West - June 14 - 16, Davidson-Gundy Alumni Center at University of Texas at Dallas
- VCF West - Aug 2 - 3, Computer History Museum, Mountain View, CA
- VCF Midwest - Sept 7 - 8 2024, Schaumburg, IL
- VCF SoCal - Mid February 2025, Location TBD, Southern CA
- VCF East - April 2025, Infoage Museum, Wall NJ
-
Please review our updated Terms and Rules here
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
IBM 5170 Hangs on Boot, any line in Config.sys that is "Device="
- Thread starter mdp_mason
- Start date
mdp_mason
Member
I am using the CF card that came with the XT-IDE, I was hoping it would be compatible if it came from the company that assembled the card and installed the initial DOS 6.22. It is a CISCO systems 128 MB card. It does look a little weathered and dirty. I will pass by Micro center today, they have 64 mb and 128 mb SanDisk CF cards in stock. I would prefer more capacity but if the size is an issue I can go for the 64 mb. Perhaps I will just grab both.HIMEM and SETVER should load fine on a fresh install, so there is still something wrong here. CHKDSK errors may be caused by incompatibility of you CF card with the XT-IDE: do you have other CF cards of different make or capacity that you can use? Also, you can add a /V switch after HIMEM.SYS in you config.sys, and see if you can get some messages on what himem is doing before the system hangs
I have added /V to himem but I don't even get any output from it. Its like as soon as the system attempts to call up the file it locks up. I also tried specifying my computer type, the A20, etc and still no dice.
--EDIT
So I will pick up the new compact flash cards soon. I pulled mine earlier to look at the brand name etc. When I put it back in and ran CHKDSK a ton of errors came back, every directory trashed. Not sure why removing it and putting it back in caused such corruption but I am strongly suspecting the card now. STI Flash 7.4.1. I ran CHKDSK /f and the total bad sectors did not change at the end but all my data is toast. Tried to launch SIMCITY after for instance and it aborted due to the graphics file being corrupted. Will update when I can try the new cards out tonight.
Last edited:
mdp_mason
Member
Hi all! Thank you all for your help. The new SanDisk CF card worked like a dream. Everything loads at startup as it should after a fresh install of PC DOS. I misread the cards I got as 128 mb and 64 mb but it was gigs haha. I figure that will stave off degradation from write cycles anyhow. I opened the 128 gig first before I realized so that's what I put in. Partitioned myself 3 2 gig partitions across C: D: and E: so I can utilize more of the space. I figure it would be a challenge to try and fill up 6 gigabytes on a 286 platform though haha.
Hi all! Thank you all for your help. The new SanDisk CF card worked like a dream. Everything loads at startup as it should after a fresh install of PC DOS. I misread the cards I got as 128 mb and 64 mb but it was gigs haha. I figure that will stave off degradation from write cycles anyhow. I opened the 128 gig first before I realized so that's what I put in. Partitioned myself 3 2 gig partitions across C: D: and E: so I can utilize more of the space. I figure it would be a challenge to try and fill up 6 gigabytes on a 286 platform though haha.
I'm glad you had everything working finally. It had started to look like the probelm was with the "hard drive" and not the 5170. You never know, but I'm glad we all focused in that direction first.
I am running a 286 clone with an AMI BIOS, and I noticed some severe data corruption with multiple CF cards. Using the XTIDE BIOS for disk access instead of the system BIOS completely fixed this issue for me.
Silent data corruption is very hard to debug, but your symptoms smell similar. You may be lucky with your current CF card, but the corruption might also just be less likely. Keep your eye open for further corruption if you want to keep using your BIOS drivers.
Silent data corruption is very hard to debug, but your symptoms smell similar. You may be lucky with your current CF card, but the corruption might also just be less likely. Keep your eye open for further corruption if you want to keep using your BIOS drivers.
mdp_mason
Member
Been installing additional programs, cards, and ram since then. So far so good! I haven't noticed any more apparent CF corruption, obvious or otherwise so fingers crossed it holds up!I am running a 286 clone with an AMI BIOS, and I noticed some severe data corruption with multiple CF cards. Using the XTIDE BIOS for disk access instead of the system BIOS completely fixed this issue for me.
Silent data corruption is very hard to debug, but your symptoms smell similar. You may be lucky with your current CF card, but the corruption might also just be less likely. Keep your eye open for further corruption if you want to keep using your BIOS drivers.