aduncan@rhea.trl.oz (Allan Duncan) (08/13/89)
side with Amiga partition. At times when I start up, the Amiga side
functions normally, and I then start up the PC side (from CLI), and you
get to see the results of autoexec.bat on the screen, ending with a CLI
prompt. Now is the time for the big test - enter a single return and
you may well be greeted with "Bad command or file name" and a PC lockup.
I haven't got the statistics yet on the occurrence, but a 50-50 on cold
boot with virtually nil on C-A-A seem about right.
I have a wait in the startup-sequnece of 75 sec after binddrivers to
make sure that there is no PC activity before I issue the djmount (oh
yeah, the disk is FFS), and the script does NO writing to disk - there
is a ASDG-rrd with a t directory with T: assigned to it.
I even tried getting rid of the ^Z that edlin puts at the end of the
.bat file. All I can suggest is there is some problem with the task that
takes the Amiga keystrokes over to the PC. Clues any body ?
There are a few other problems that I have with the board, such as
read/write errors on cold booting, which, when too frequent, can be sent
away by flexing the bridgeboard, or if severe, levering of the IC's in
their TIN(?) sockets. (Haven't Commodore heard that tin oxide is not very
conducting, and forms very easily between two contacts that carry little
current). Not what I would call robust.
Allan Duncan ACSnet aduncan@rhea.trl.oz
ARPA aduncan%rhea.trl.oz@uunet.uu.net
UUCP {uunet,hplabs,ukc}!munnari!rhea.trl.oz!aduncan
Telecom Research Labs, PO Box 249, Clayton, Victoria, 3168, Australia.aduncan@rhea.trl.oz (Allan Duncan) (08/14/89)
The front end of the previous post got munged somewhere locally, so here
goes again.....
I have a B2000, PC bridgeboard, 2.63 software, with hard disk on the PC
side with Amiga partition. At times when I start up, the Amiga side
functions normally, and I then start up the PC side (from CLI), and you
get to see the results of autoexec.bat on the screen, ending with a CLI
prompt. Now is the time for the big test - enter a single return and
you may well be greeted with "Bad command or file name" and a PC lockup.
I haven't got the statistics yet on the occurrence, but a 50-50 on cold
boot with virtually nil on C-A-A seem about right.
I have a wait in the startup-sequnece of 75 sec after binddrivers to
make sure that there is no PC activity before I issue the djmount (oh
yeah, the disk is FFS), and the script does NO writing to disk - there
is a ASDG-rrd with a t directory with T: assigned to it.
I even tried getting rid of the ^Z that edlin puts at the end of the
.bat file. All I can suggest is there is some problem with the task that
takes the Amiga keystrokes over to the PC. Clues any body ?
There are a few other problems that I have with the board, such as
read/write errors on cold booting, which, when too frequent, can be sent
away by flexing the bridgeboard, or if severe, levering of the IC's in
their TIN(?) sockets. (Haven't Commodore heard that tin oxide is not very
conducting, and forms very easily between two contacts that carry little
current). Not what I would call robust.
--
Allan Duncan ACSnet aduncan@rhea.trl.oz
ARPA aduncan%rhea.trl.oz@uunet.uu.net
UUCP {uunet,hplabs,ukc}!munnari!rhea.trl.oz!aduncan
Telecom Research Labs, PO Box 249, Clayton, Victoria, 3168, Australia.