VOGONS


First post, by Nunoalex

User metadata
Rank Newbie
Rank
Newbie

Hi gain everyone !

I recently bought and old 486 DX2-66 computer that brought a 170mb IBM hard drive (IBM wda-l160)
I suspect the hard disk came form an older system that was upgraded since 170mb was already too low for a 486
I will later put pictures of the machine later on the "system specs" section of this forum

Anyway I plugged the drive on another machine since the mobo that came with the system is heavily corroded by the varta plague taking care to configure the jumper to slave drive (I looked up the drive model online)
The drives boots and makes happy old hard drive noises, no sign of a mechanical malfunction
I could access D: (actually D: and E: since it was partitioned in 2) and "DIR" gives me the list of files I could make MD directories (not folders, DIRECTORIES dammit) and I could copy files over to my other C: drive
But then the problems started, when "chekdisking" there were a lot of truncated files, lost chains etc etc FAT was corrupt etc etc
But trying the checkit /f hangs the machine after a few files are processed

I tried NDD and again errors upon errors, sometimes it seemed it could fix the FAT issue but then it would tell me "drive not present" while fixing the directory structure
I did manage to bring NDD to run to the end and it seem to do a surface scan that showed no errors and the drive light was lit and it seemed to be processing the disk surface
There was a clear map of the drive with used and unused sectors shown... no bad sectors whatsoever)

So I decided to just go nuclear and bring back good old FDISK (My gosh I think it was the first time I used FDISK in 25 years)
FDISK erased the old partitions and made a new 170mb one, I set it to active and then next logical step was good old "Format D:"
First Format said it didn't have space to save a recovery file and then proceeded with he format.. when it reached 100% it stopped a bit and then it said "Cannot write FAT, Format terminated"
So now the drive is not accessible most of the time, but sometimes I CAN access it and DIR command shows no files - empty
I plugged the drive to another computer with windows 7 and windows recognized and installed "drivers" for it and it was present as drive D: but could not access it or format it

So I come here for help if anyone can have an idea of what I can do
I doesnt seem to be a mechanical problem, the drive behaves normally, powers up, does the self test and obeys commands that are sent to it
It seems a logical problem
Could the magnetic material in the platters be demagnetized after all this years and the logical information of the drive geometry that was recorded at fabrication be weak or erased and the drive needs a new low level format?
Or can a capacitor on the control board be bad and data read/write is not reliable? But the errors seem very specific, for example I did manage to dir/s and xcopy files etc... no strange errors there
Or am I just doing something wrong? My DOS era hardware memory is already a bit vague

Well thank you everyone

Nuno

Reply 1 of 17, by weedeewee

User metadata
Rank l33t
Rank
l33t

Try this

remove the partition
then create an extended partition
now create two logical drives, each about half the hard drive
try to format both.

I'm guessing your hard drive has some bad sectors in a lousy location.

Right to repair is fundamental. You own it, you're allowed to fix it.
How To Ask Questions The Smart Way
Do not ask Why !
https://www.vogonswiki.com/index.php/Serial_port

Reply 2 of 17, by Jo22

User metadata
Rank l33t++
Rank
l33t++

I think the same. 🙂👍

You can try running S0KILL to safely erase all data, too.
Re: IDE to Compact Flash as MS-DOS boot drive.

Then proceed creating all partitions from new.

Bad sectors.. I'm speaking under correction, but I think something is off if that error message appears.

Not because of DOS, but rather because HDDs that "modern" do usually silently use spare replacement sectores (reserved sectors).

That means that either some serious defect exists or that the HDD ran out of spare sectors.
Which isn't good, either.

On MFM/RLL era HDDs, bad sectors were normal and excluded during low-level format.
A sticker/label with a table was stuck on the HDD that provided information.
Also, DOS itself did exclude bad sectors during soft format (aka high-level format).. Not sure how reliable that was, though.🤷‍♂️

Edit: Please don't throw out that HDD, though.
Some HDDs (especially Conner models) that old or young do have a debug port on the PCB.
It's a serial connection, like with modern DSL router.
By using a terminal program, you can see what the HDD firmware is reporting.
PS: The voltages might be +-5v, not +-12v as used by RS-232 ports on PC.

"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel

//My video channel//

Reply 3 of 17, by Nunoalex

User metadata
Rank Newbie
Rank
Newbie
weedeewee wrote on 2023-03-21, 16:28:
Try this […]
Show full quote

Try this

remove the partition
then create an extended partition
now create two logical drives, each about half the hard drive
try to format both.

I'm guessing your hard drive has some bad sectors in a lousy location.

Ok I will try but I never heard any read retry noises associated with bad sectors
everytime the drive did something like the NDD surface scan you could hear the heads normally running along its course

Reply 5 of 17, by ediflorianUS

User metadata
Rank Member
Rank
Member

it may be a hardware issue , like ram... pull the drive run a full test externally on modern pc , if all is fine the drive is ok. (check for corrosion on PCB , if corrosion , clean with contact cleaner , remount pcb). Fdisk is no good , try other tools, (from hirens) or something else. better yet format partition and load win files from modern pc, then plug in old. Properly set-up hdd CHS specs in bios.

I usually use QuickTech Pro - PC Hardware Diagnostic tools , it has a good good hdd tester and formatter. (if the hdd is seen by pc)

My 80486-S i66 Project

Reply 6 of 17, by douglar

User metadata
Rank Oldbie
Rank
Oldbie
ediflorianUS wrote on 2023-03-22, 10:18:

it may be a hardware issue , like ram... pull the drive run a full test externally on modern pc

Might be a challenge to make the drive work in a new PC.

Hard drives built before 1995 rarely have working LBA addressing and require CHS addressing to function. (Cylinders/Heads/Sectors)
Most USB adapters and PCIexpress controllers built after 2005 insist on using LBA addressing.

So if you attach that old drive to your new computer and it starts clacking like a rattle and seems unable to do anything, that's just the result of trying to use LBA addressing on a CHS only drive.

Reply 7 of 17, by Horun

User metadata
Rank l33t++
Rank
l33t++

I agree douglar ! Needs a 486, Pentium, P.Pro or Slot 1 board running DOS to really fdisk and format that old of a drive IMHO and make sure to manually enter the CHS values of the "translated" of the CHS
good chance the 486 does have an issue...

Hate posting a reply and then have to edit it because it made no sense 😁 First computer was an IBM 3270 workstation with CGA monitor. Stuff: https://archive.org/details/@horun

Reply 8 of 17, by Jo22

User metadata
Rank l33t++
Rank
l33t++

I was able to use a classic ~80 MB drive on an AMD Athlon 64 X2 PC in 2008 or so.
The BIOS auto-detected the HDD with the right values if attached to the on-board IDE connector..

But that's really hit and miss. Depends on the drive's firmware, the PC's BIOS etc.
Real CHS (P-CHS, physical CHS) isn't being used since the 1980s, anymore. It's rather L-CHS (Logical CHS).
Some vintage HDDs also support LARGE model (E-CHS), the predecessor to LBA.

Yeah, it's really hard to predict how compatibility turns out in practice. 😅
HDDs since 1990s or so do cheat with the CHS values, anyway, to please both IDE and PC BIOS specs.
If it wasn't for DOS/BIOS, the very same ancient HDD controller electronics could handles gigabytes of storage just fine.

Edit: IMHO, the CHS or LBA translation matrices used are slightly similar to how x86 assembly worked in real mode: segment+offset.
I.e., it's possible that two different drive geometries *may* work in accessing the drive's data.
This possibility might also be the cause for confusion between PC-HDD, however.

The changes that were made with ATA-2 specification also harm compatibility.
Certain register meanings have changed, or registers react in a different way.

"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel

//My video channel//

Reply 9 of 17, by ediflorianUS

User metadata
Rank Member
Rank
Member
douglar wrote on 2023-03-22, 19:29:
Might be a challenge to make the drive work in a new PC. […]
Show full quote
ediflorianUS wrote on 2023-03-22, 10:18:

it may be a hardware issue , like ram... pull the drive run a full test externally on modern pc

Might be a challenge to make the drive work in a new PC.

Hard drives built before 1995 rarely have working LBA addressing and require CHS addressing to function. (Cylinders/Heads/Sectors)
Most USB adapters and PCIexpress controllers built after 2005 insist on using LBA addressing.

So if you attach that old drive to your new computer and it starts clacking like a rattle and seems unable to do anything, that's just the result of trying to use LBA addressing on a CHS only drive.

My connor drive ide 20 mb from Toshiba worked fine with external enclosure to backup everything .

My 80486-S i66 Project

Reply 11 of 17, by ediflorianUS

User metadata
Rank Member
Rank
Member
douglar wrote on 2023-03-24, 09:59:
ediflorianUS wrote on 2023-03-24, 08:45:

My connor drive ide 20 mb from Toshiba worked fine with external enclosure to backup everything .

Whats the make and model of enclosure are you using?

a Q-Tec 750H USB2 HDD CASE 3.5" item no.13290 rated 200-240VAC/VDC,2.0A/12V

(used the same enclosure to load/install win98 on my 486 WD43 hdd).

Attachments

  • WP_20230324_001.jpg
    Filename
    WP_20230324_001.jpg
    File size
    777.01 KiB
    Views
    1057 views
    File license
    Fair use/fair dealing exception
  • WP_20230324_002.jpg
    Filename
    WP_20230324_002.jpg
    File size
    896.24 KiB
    Views
    1057 views
    File license
    Fair use/fair dealing exception
  • WP_20230324_006.jpg
    Filename
    WP_20230324_006.jpg
    File size
    761.03 KiB
    Views
    1057 views
    File license
    Fair use/fair dealing exception

My 80486-S i66 Project

Reply 13 of 17, by weedeewee

User metadata
Rank l33t
Rank
l33t
douglar wrote on 2023-03-24, 14:35:

Nice adapter. Looks like it is old enough (~2005) to still support CHS addressing. That’s a keeper!

~2001 https://datasheet.datasheetarchive.com/origin … DSA00381869.pdf

Right to repair is fundamental. You own it, you're allowed to fix it.
How To Ask Questions The Smart Way
Do not ask Why !
https://www.vogonswiki.com/index.php/Serial_port

Reply 14 of 17, by rasz_pl

User metadata
Rank l33t
Rank
l33t

Re: IDE to USB adapter (again) Afaik Cypress EZ-USB FX2 USB 2.0 Chip reference IDE-to-USB design supports CHS and PIO modes
CY4611B – FX2LP USB to ATA/CF Reference Design https://media.digikey.com/pdf/Data%20Sheets/C … DFs/CY4611B.pdf
can be build using $5 "CY7C68013A-56 Develope Board Eeprom FX2LP Module Logic Analyzer Usb 2.0"
https://www-user.tu-chemnitz.de/~heha/basteln … x2/index.en.htm

looking at ide.c source code:
[code]extern char NumCylindersMSB; // global #Cyl MSB
extern char NumCylindersLSB; // global #Cyl LSB
extern char NumHeads; // global #Heads
extern char NumSectPerTrack; // global #SectorsPerTrack[/code]

but now that I started reading the firmware itself all I can see is LBA addressing 🙁

Open Source AT&T Globalyst/NCR/FIC 486-GAC-2 proprietary Cache Module reproduction

Reply 16 of 17, by Nunoalex

User metadata
Rank Newbie
Rank
Newbie

ok a little update on the 170 mb IBM hard disk
To be honest the hard disk is 160mb ... because back in the good old days 1 MB = 1024 KB

Anyway... I managed to find some old MS-DOS disks that I had not put into a disk drive in 35 years ! And run the setup
the setup started and it told me the hard disk was not formatted and if I wanted to format... I formatted it and it just went and installed ms-dos 5.0

so now the HDD is running fines, I copied some files and folders and programs run from it...

So as a note to people... dont assume anything when dealing with old hardware... it is a REAL possibility you dont have enough information/knowledge when presented with an issue
I could very well have assumed the disk was toast and throw it or open it or just completely destroy it in my ignorance

but the HDD was not doing any unpleasant sounds and was responding to commands so I had a big feeling it was just some logical/compatibility/software issue

thanx to everyone that responded

here are a few pictures of the ancient bugger

2TnLC2H.jpeg

UlHwPFk.jpeg

S0PZcyR.jpeg

Reply 17 of 17, by ediflorianUS

User metadata
Rank Member
Rank
Member

I managed to fix load's of thoast drives (at least to the point you can MS-DOS-use them.) I even hate trowing away the one's I could not fix , I just set-tem asside. I even start Ram selection and would only trow the one's I cannot fix , use or won't boot to MS-DOS (1mb required).

I learned the hard way that if you use SSD, and they fail , data is lost , you are lucky if you can fix the ssd.... (so I hate them). yes they are fast , but have internal firmware(os) much worse than HDD's

and I leanerd single and dual platter drives are most robust , and sometimes even with 1 bad sector they can last as much as you need them .

I do like upgrading old pc's but , as I have files and check for backup before upgrade , I had no issues , and was limited to about 4 gb on vintage (pre P1 systems) Never managed to fill them. (you can use up to 120gb in fat32 in dos) with not much issue ,
but what's the point?

Ocasionally I do came across on drives that spin , but you can only format them if you wish to use , or worse , format in uncomon format's (like a seagate 500gb I never managed to do anything except reset-format then partition with exFat , no fat 32 or ntfs would ever run on it ) but drive run fine , useing as backup for music as secondary drive , copy-ing with cmd copy-x command... under xp64bit

Most of the times PCB is faulty , dirty or corroded , quick clean fixes many issues otherwhyse the system would spew-out as errrors.
Once I had to resolder 1 pin on IDE drive that gave multiple errors, ide conector was savered (1pin) ... never had issues after fix.
Or my Toshiba T3100e , had a missaligned by 2 pin IDE cable , and gave error , fix that , worked fine , than put asside the connor drive and upgraded to Seagate 4.3 , (the WD4.3 would not be verry compatible , could not partition it on the T.... , worked fine on the 486 project - my original 486 drive is K.i.a.... need to fix that , 320mb....).

My 80486-S i66 Project