Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Dream Machine ( Build your own PC ) -- Ignore unavailable to you. Want to Upgrade?

To: Clarence Dodge who wrote (7258)	4/25/1999 4:28:00 PM
From: Zeuspaul	Read Replies (1) \| Respond to of 14778

The errors that are present in the lost partitions will still be there after a restore, correct? Yes. My best guess is the errors are not in the partitions but in the partition tables in the Master Boot Record. If you do not have a backup of the MBR..and do not ask me how you are supposed to do that, I do not think you can or 'easily can' restore the MBR. I can't help but wonder if there was a problem on that disk before I opened PM. Like I said, its amazing to me that just opening PM could cause such havoc. Running a PM procedure would be more understandable Well she booted so the MBR was OK before PM did whatever it did to the MBR. Naturally a reformat of that disk is needed after I get the data off, or as Wily has indicated maybe before. What else can I do to repair whats broken? After yes. I would hesitated on the before unless you are confident you can find some "real" free space. Since PM thinks the entire drive is free space I do not know how you can find "real" free space. Was there free space at the end of the drive per your memory? Did you make a clone of the KOT at the end of the primary NT drive? If so you could use that as a restore AFTER you recover your files. Yes I think I have enough free space on C: or E: (ScsiTa). ROMO too, of course. ROMO doesn't have a bootable OS. Would that be a problem? Bootable OS is not a problem. Size may be a problem. Where does the free space start? You may have to use an extended FAT32 partition to be compatible with L&F. Anything beyond the 2 gig barrier pretty much rules out FAT unless you make it a primary partition. Is the ROMO the least risky drive to play with? If so I would try a FAT 32 partition on a ROMO. One option might be to move the partition on the ROMO towards the 8 gig barrier..risky if you try to move it beyond the 8 gig barrier, then put a primary 2 gig FAT partition at the front of the ROMO. Just thinking out loud here..do not make any rash moves until we think the ideas through. Zeuspaul

To: Clarence Dodge who wrote (7258)	4/27/1999 7:42:00 PM
From: Sean W. Smith	Read Replies (1) \| Respond to of 14778

Clarence, <iI can't help but wonder if there was a problem on that disk before I opened PM. Like I said, its amazing to me that just opening PM could cause such havoc. Running a PM procedure would be more understandable If all you were doing was starting PM then PM being the cause of the problem is nearly impossible. PM doesn't write your disk upon loading and waits till you tell it to do something and then apply changes. I would be far more suspect of the insertion and removal of this disk. Either way it definetly sucks but Can't see how just loading a software package is gonna destroy your disk. Sean