##29110 Bnd Crash
2 messages in this thread
Don,
Your assumptions are correct and I think I read you right. Booting from
the floppy also tells me that there's nothing wrong with the software on the
floppy. Yes, I have recopied the software on the harddrive, more than once.
I've completely erased the harddrive and copied all the files from the floppy,
that I know booted ok, onto the harddrive, although I don't have a file compare
program. But if the problem is bad PC files on the harddrive, I should still
be able to jlink to a harddrive partition, if I boot from the floppy, no? This
grows curiouser and curiouser.
Dennis
Dennis,
You can't JLINK until the Bridge side boots…and you said you get the
GURU right after you issued the BindDrivers command. At that point, the bridge
hasn't booted yet…it's just starting.
As I said before, the Binddrivers command is issued and the Bridge goes
thru an initial check of it's configuration…that's the first access of the
drives and then Binddrivers returns.
However, at that point, the Bridge isn't booted, it's just starting
it's boot process. For the next 15 or 20 seoncds or so…it's checking it's
RAM and looking for the serial and parallel ports. Once it's done that, it
then once again…accesses the floppy looking for a boot disk. If found, it
boots. If not found, it then looks for a bootable harddrive. If that's not
found either…it puts up a prompt asking for a system disk.
If it finds either a bootable floppy or HD, it then reads in the file
'config.sys' and configures drivers as needed, and finaly it looks for the file
'autoexec.bat' and executes it if found. If no autoexec.bat file exists…it
posts a date prompt so you can enter the system date.
So as you can see, until the bridge gets to the config.sys file, it
can't even load the MS-DOS side drive (jdisk.sys) and until it gets to
autoexec.bat…it can't execute the JLINK.EXE command.
So…JLINK is also out as a problem…the problem is running
binddrivers from your Amiga side HD vs running it from your Amiga side floppy.
Try this for 'fun'….place a line that simply says 'ASSIGN' in your HD
startup-sequence just before the binddrivers command. That'll tell you where
things are assigned at that point. Let me know what it says.
Don