DeadDude

Member
  • Content count

    138
  • Joined

  • Last visited

Community Reputation

0 Neutral

About DeadDude

  1. "all the others" in reference to drive being reported as 10.blah refers to some OLD software I had tried. Old boot CD from 95OSR2.1 Win98 *.*.2222 CD (I really need to just LOOK at it already and give you the actual label #'s- it isn't listed in any listing I can find on W98SE revision charts I can find) floppy boot disk images from bootcd.something that were put onto CD by me. Ancient redhat installer CD (4.?2. Not in front of me right now) only when those things appeared faulty did I try the W2k cd again. When the 80 got here, I first installed W2k (to test his software ona "modern" OS) to remove W2k, I booted 98SE cd and removed the partitions from the installer. If I remember correctly, I had to reboot afterwards, before files were copied.
  2. On my iPod, sorry for lack of quotes and clarity... I do not know if fdisk listed gig or Meg, very possible I misread and assumed it was gig. Reading the suggestion of percentage instead of absolute values sound *very* familiar... Like I forgot that bit from not doing this for such a long time. The HPA may have been immediately reinstated upon first boot and I didn't notice until later.... The first boot didn't show any XPRESS message, but a later boot up (after I partitioned?) had the message. Weird thing tho, as I have since checked the other machines (remember, these machines came from the same batch- all parts sans this 80, were purchased together) do NOT have the HPA. So it sounds like something I did during initial setup all those years ago 'worked around' it. I will post again and answer more questions, just need to 'reply' so I can scroll back and re-readanother post I want to respond to. This site is real hard to use on tiny handheld...!
  3. well, I removed the HPA anyways and started fresh. Interestingly, the HPA came back after a few power cycles... and I noticed the BIOS splash screen starting listing "Booting from XPRESS blah blah" I did some digging, and found the motherboard itself creates an HPA exactly as I had seen on this drive previously. There is no option to deny it happening. I looked at the existing installs today. None of them have the HPA. Very strange, but I simply gave up. I was going to try the image crap again, but decided against it. I am all ears if anyone is aware of software or method to clone this. In the meantime, I have decided to simply add the bits by hand. I was able to recover the specific files off the existing server, and found a previously forgotten TXT file with instructions. I wish I had the time to check the existing server beforehand, as I had already searched all the backup CDs and didn't find these files. (apparently, the IMAGE had the files, but the W98 QIC files did NOT.) I am also now in the process of changing the backup structure for his shop... the old method only worked because of using BOTH the image and the backups (QIC). For unknown reasons he prefers the W98 backup program. Personally I had no issue with that until now. I am thinking of a batch file utilizing RAR command-line to compress, and img burn (name?) to burn to CDR... automated.... multi-pass.... and putting the bits back in through the script... any ideas? Thank you Jaclaz and everyone else for the patience while I freaked out. To be sure, would you agree the problem (for unknown and unimportant reasons right now) is W98SE Installer CDs FDISK? Whether loaded through the install process or booted into DOS and loaded from there? I had only used the W98SE installer disk for those steps (until ya'll pointed me elsewhere). Now I *did* use the W2k CD to fdisk it at some point, but I am now of the impression that is irrelevant in the big picture. Would you agree?
  4. ??? Can you elaborate on that please? The HPA region is removed from the count? Honestly, I have no idea what I am talking about here (never heard of HPA before today). I've read a few articles earlier on it, but don't understand how 'given the HPA region' fits in. (to be clear, I'm just dumb and asking for clarification) Thanks for all your help would you agree then the most likely scenario is FDisk in the 98SE installer is not happy with this drive for some reason? But all other things should be fine so long as 98SE Fdisk don't get near this? I am going to try the image thing tomorrow.
  5. drive goemetry RPM finds gimem sec. EDIT across top of page Hard Disk 1 76,318Mbytes 9,729 cylinders x 255heads x 63 sectors Sector info (I hit F4) # type row filesystemtype startingsector #ofsectors endingsector partsize 0 MBR Master Boot Record 0 1 0 0 1 Pri Unused 1 62 62 31 2 *Pri 1 Windowws FAT-32 LBA 63 40936547 40936609 20468273 3 Pri Unused 40936610 156299374 57681382 4 UNUSED I hope the data requested is listed there, I have to run to the airport right this second. Lots more stuff happening then just this PC... If it still isn't what you are asking for, I apologize again... please tell me where to look in RPM for the data. I do not have Partition Logic. When I get back (about 2hrs) I will look for it. EDIT EDIT We passed in by each other with those last posts... Off to airport, be back in a long bit. thanks
  6. I'm sorry jclaz if I missed something you posted... The sectors reported by RPM matches the amount of sectors minus the HPA area. I've never heard of HPA before. Yes, I am in over my head looking through those things. The BIOS reports the sector values matching the WD official count. HDAT2 reports the drive is missing roughly 1.05 megs at the very beginning of the drive. Looking through that 1.05 megs, I see the FAT 12 listings and over 5,000 FILECHK files broken into chunks of roughly 100 files with 1k-2k of gibberish between them. EDIT EDIT I am installing all the 98 drivers and whatnot at this moment. Afterwards, I will use this 80G and clone it using previous posts to one of my spare older FAT32 drives and see if the result works. I am very curious about imaging now... if an image of a drive does NOT include the HPA, would that be able to cause some of these issues? I've done all these same steps for the last 15+ yrs of my life and never had anything like this occur. I've always been able to simply low level format a drive to undo any partitioning issues I may have caused... and I've never seen data left behind from a low level format.... let alone zero'ing the entire drive...! Am I just spontaneously stupid or something? Maybe I need to step back from this for a while... I swear I'll pull and Office Space on this tower if after this current install it still cannot image properly (and restore). And I apologize if I miss responding to any questions posted here. If you ask again, I will properly answer. My mind is a jumbled mess over this. Thank you for your patience and understanding.
  7. RPM reports the size WITHOUT the HPA area included. Let me see if I got Parition Logic somewhere....
  8. got 98se installed with no drivers so far. but on a whim, I decided to 'check out' the drive... jaclaz said I would try contacting WD support, as what Deaddude bought was a disk with 156,301,488 sectors (of 512 bytes each). every tool/utility I use to check out the sectors reports the drive has a total of 156,299,375 sectors. MHDD v.4.6 HDAT2 v4.5.3 While using HDAT2, I see there IS actually the correct number of sectors... but the 'missing' sectors are in HPA at the very beginning of the drive. Does anyone here know how to read the info HDAT2 displays? I see a lot of data that is nearly meaningless to me... sector 0 000-1F0 33 c0 8e d0 bc 00 7c fb 50 07 50 1f fc be 1b 7c bf 1b 06 50 57 b9 e5 01 f3 a4 cb be be 07 b1 04 I'm not sure what I'm supposed to see looking at the drive in HEX.... BUT... ?!I see CHK files from Scandisk?!?!?! I RAN SCANDISK AFTER THE LOW LEVEL FORMAT! And since then, I have ActiveKilldisk'd this bugger 2-3 times! I see FILE0001CHK through FILE0285CHK I also see a FAT12 table listed afterwards. I am labeleing it FAT 12 because it keeps listing FAT12...NO NAME... gibberish for 5 lines then repeats. Weird things... cuz whenever I have run scandisk on this drive, it has never reported any errors... and the first thing I do is set scandisk to NOT save chains in files. I also check the root of the drive for corruption, and I've never seen these lost chain files there. but a hex view shows them?! Did I get a refurbished drive? That came from a 4k 'home' and transplanted into 512b? yes, I know. I sound totally stupid and crazy. With the tiniest bit of info, my mind is racing through possibilities now that I'm looking through HEX eyes... been years and years, and I never was good without a cheat sheet.. and I ain't got a cheat sheet... so if y'all know this hex stuff... I'm staring at it and will leave it as is for a little bit.... very very odd. 0'd HD has bits that were never placed there...?
  9. alright, I zero'd it out. I ran WD lifeguard Used it to make partitions. Loaded RPM. RPM says Unknown IPL I zero'd it again. Ran RPM Still Unknown IPL ????!! Using it to create primary partition as I type this. After partition created, RPM formatted it. Now, RPM says "Standard IPL" Going to add 2nd partition next... and if that appears fine... I am going to try the install to this drive... NOTE: RPM **IS** user friendly. All options labeled on-screen. Lots of power at fingertips. Seems very simply to use. VERY simple. maybe toooo simple...? great find, wish I knew about it sooner!
  10. found out my cam is useless... LoL here's my attempt at copying all text data for ya to inspect. PATA / 8MB Cache WD800AAJB S/N: WCAV3E898896 MDL: WD800AAJB - 00J3A0 WWN: 50014EE1AF077CA2 DATE: 18 AUG 2011 DCM: DBRCNT2AHN DCX: 9009JES38 5VDC: 0.65A 12VDC: 0.50A R/N: 701596 Circle with arrow splitting it in half D33015 C backwards R U us E101559 KCC - REM - WDT - 1596 Fragile symbol of broken glass trashcan with 'x' over it ecs in tiny print bottom right corner of label bar code next to plug, on bottom of drive: 2061-701596-A00 19R about 5 spaces away from that is: XC 8G17 05NH 9 005060 2065 greenboard on bottom of hard drive has the following printed: TS-M-8V03C SG TOPSEARCH E96016 94V-0 in a box: 18702 in green print at edge: 2060-701596-001 REV A The bottom of the drive, the 'motherboard' appears to be lacking a LOT of components. I realize this doesn't have to mean anything at all... but this is the first drive that appears to be lacking an entire chip that I have seen. Place is labeled "J2"... so it makes me think Jumpers... but whatever... blah blah. Hope I posted the bits you were interested in!
  11. http://community.wdc.com/t5/Desktop/New-WD15EARS-Showing-512-byte-Physical-Sectors/td-p/248170 others have reported the model # doesn't always mean it's the exact same part when it comes to WD drives. I'll see if I can get a pic of the drive to post.... otherwise, I'll try my best to copy it all down here
  12. Oh yeah, one of the FIRST things I did was use the WD life thingy to zero out the first 100 megs and last 500 megs... or reverse that... it was MUCH faster. I ain't taking another step (no 0'ing) until the 4k thing is sorted... Standing by, Capt'n! Thanks!
  13. if you take 4,096 and divide it by 512 you get 8. The drive is 80gigs. FDisk and all other partition manager software pre-2001 report is as a 10gig. After reading how a 4k HD gets mangled by 512 software and partitioning.. I have deduced the drive is in fast a 4k drive. Installing W2k or XP... the drive is properly seen and handled as an 80gig. Installing *anything older* and the drive is seen as an 80gig, but handled as a 10gig. One of the times the drive was mangled, but still booted, I tried to access various files across various partitions. The partitions 'looped' into phantoms. And media files being accessed would on occasion cause VFAT errors. So long as I only accessed the first 500ish megs on the hard drive, it all seemed okay except for cosmetics in My Computer. The first time I accessed D;\ it worked fine, but the 2nd time it said the disk wasn't formatted. In the beginning, I suspected partition damage somehow, so I got into the habit of copying over 2 gigs of mp3s and about half a gig of videos to test it with. Looking at my notes, I can safely conclude the files that 'nerfed' the drive were all beyond the initial 500megs of the drive. Sometimes the copy would 'just work', other times it would only get so far in and BSOD VFAT. another member PM'd me the post link I reposted earlier... and after reading their entire story and the WD white papers... and some basic math... I do believe the drive is using 4k clusters internally, while the OS I am attempting to use is interacting with the drive as if it uses 512b internally. A previous poster shared a link about LBA and BIOS stuff. Thank you very very much, as this was a great primer for the deducing required to reach my conclusions. The page gave me an understanding of how a drive head of 4096 size could mangle a track written in 512 size. Hard to explain that idea properly at this time... but it does explain every single thing I have seen happen, in a nice, tight little package all at once. And for the record, this IS the thing that changed in hard drives in the last 5 years.
  14. I just confirmed the drive is 'Advanced Formatted', and from what I understand that means 4k instead of 512b... does that mean I'm dead in the water? Is RPM 'advanced format' aware? It looks like I messed up the drive majorly from using utilities/partitioners/etc that aren't 4k aware....? Does any of this make sense to someone out there? I thought a low level format would place a 512b format and remove the 4k? Insert profanity here. I'm still going to sero it out with killdisk. pending answers posted, I might take a trip to the shooting range with this sucker.
  15. it took me a second to find xxcopy... at the moment, I couldn't see the forest for the trees... I have since discovered all other utilities are on my UBCD, so I figure I would avoid the extra work of loading the drivers into the 'old' hard drive (only install 98SE, no patches, no updates, no drivers), run xxcopy, swap drives, and load drivers in the 80. Do you see any possible issues with that? In about 10 minutes I'll be zero'ing the drive. got side tracked... located everything and made sure in a VM my UBCD is a good copy.