| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | help! |
RS> You havent said if thats the old or the new system, motherboard etc. RS> Tho you do appear to be saying that this is all after the change. Yeah, all happened after the change. PE> Anyway, I have serious suspicions about this LBA. RS> You should have tried just disabling that on the first hint of a problem RS> with E once you installed the new motherboard, if thats what you did. Well actually I replaced the disk with my old IDE, and it still wouldn't boot off my C drive, with OS/2 3.0. I did write down all the OS/2 abend information. PE> The fact that it doesn't show up in boot manager is worrying. RS> It is indeed, thats what I said before, that enabling it may make RS> the data invisible. In this case that applys to the partition table. The data on the D drive (500 meg HPFS on new drive) was ALWAYS visible. The data on the E drive, I think was visible. The thing is, I only ever got to see it if I booted OS/2 off floppies, because I couldn't boot OS/2 off any of my drives. I don't think I would have attempted to install on a drive that I couldn't even see. In fact, the install onto my E drive (2 gig HPFS on new drive), DID succeed, up to the point where it had read in 7 disks off floppy, and was rebooting the machine. The thing is, when the machine was rebooted, instead of continuing the installation, the motherboard came up and told me "no operating system installed". It was at THAT point, that I didn't see my E drive's data again. I got to see ACLLIST once, and then the next time, even that file had disappeared. Considering I had installed 7 OS/2 disks onto the drive successfully, I didn't think it was such a bad thing to do a chkdsk. chkdsk just said it couldn't find the root directory, attempting to repair, and that was it. RS> Its not clear what you actually did. If you installed the new RS> motherboard, and auto identified the 2.5GB drive, hopefully you RS> did get the same numbers as you used with the old motherboard. Yes, I made sure of that. Initially I didn't get the right answer for the old D drive (540 meg, FAT), so I changed them myself. Not that I think that made any difference, I think the data would have been visible either way. I couldn't find a way of getting my motherboard to force LBA for the 540 meg drive. It chooses "LARGE". However, despite the fact that it always chooses "large", like I said, it was disappearing from my C drive's boot manager if I enabled LBA support on the disk. Since then I have repartitioned the old 540 meg drive, and everything is fine, with LBA support (but still "large") and it appears on boot manager. RS> That should have then allowed both the D and E drives to be as RS> visible as they were on the old system. Maybe needing to disable LBA. Ok, I can't remember if I actually did this. However, I didn't really care if the drive data was visible, what I cared about was booting OS/2 3.0 off the C drive. If that had worked, and I had found the drive not visible, I would have done further investigation into that. PE> But if anyone has a tool to recover data from an HPFS partition PE> that is in god-knows what state, please send it to me. RS> Sounds like what you have done with it since has creamed it. The raw data will still be stored on the disk in sectors, which I can still access, aren't they? Or does HPFS get rid of sectors? BFN. Paul. @EOT: ---* Origin: Ten Minute Limit (3:711/934) SEEN-BY: 640/305 711/934 @PATH: 711/934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.