#Bridgeboard Help!
10 messages in this thread
This is to anyone who has experience with the Amiga Bridgeboard. I have a
friend, actually a professor, who has the XT BB. He has lost the use of his
virtual C drive (in this case naed fake_c). He lost it using Prodigy
software. Because the info on the drive is vital, he despa ly needs to get
the drive back. It is a 10 meg partition. Double-clicking on the PC MONO
icon yields a message that reads BOOT DISK FAILURE, TRY ANY KEY TO RETRY.
How can I reaccess this drive? Booting the program from floppy works but he
can't access the drive. If the PC Boot portion is on the fake_c partition,
is he screwed? Please be spcific in your answer so I can relay it properly.
Many Thanks!!!
That "drive" is a simple AmigaDOS file on the Amiga side. He
should look in his sys:pc/system directory for a file called aboot.ctl
(or some such) which contains the full path information for this
file. Not that finding the file will necessairly do you much good
since it's laid out as if it were a whole MS-DOS filesystem rather
than a series of MS-DOS files.
If I were to reformat and completely reinstall the software, would I
be able to reaccess the "drive", if I back up the file and reinstall it.
Lap,
If the file is trashed, then you'd be backing up a trashed file so
no…you wouldn't be able to access it.
If the file isn't trashed, then perhaps the aboot.ctl file somehow
or other got changed/trashed so the system can no longer find the file.
Can you do anything with the "drive" from the MS-DOS side? Perhaps
something like chkdsk on it?
Don
Don,
Do you recall that using the /F parameter with chkdsk will trash the
drive?
Sincerely,
(Mr.) Gayle Lee Fairless
'Perfessor Fearless'
– via Whap!
lap wah lee,
If you can use chkdsk, don't use the /F key. I read a message from
someone that Chkdsk /F will trash your hard drive.
Sincerely,
(Mr.) Gayle Lee Fairless
'Perfessor Fearless'
– via Whap!
Gayle,
The /f flag is the only why to get chkdsk to actually do any
repairs.
You run it first without the /f flag so you can see what's going
on, then if you find problems, you use the /f (perhaps after a
backup…depends on the problems) to do the fixup.
Don
Thanks, I sort of knew that already.
Just to clarify some more. We did look at the aboot.ctrl file and it
showed something like DH1:fake_c which I guess was pointing to the "drive"
file. I'm sure it was pointing to the correct one but still the message of
boot failure occured. There was only one line in the aboot.ctrl. My thining
is that if the PC bootup is not in that pseudo drive, I should be able to
reinstall everything and reinstall that one file and have it work. I would
try this except that I would like some opinion before I do anything.
Lap,
Sure, you could use MAKEAB to remake dh0:fake_c if you wanted, but
that would insure that you lost any and all data that fake_c may currently
contain.
Look on your dh0:, see what's there. Your problem may be something
as simple as the drive that shows up as DH0: may have a loose connection or
some such.
Don