CRONEJP@UREGINA1.BITNET (Jonathan Crone) (03/06/89)
I've been trying to get a friends A2000 to work prorperly with aread, awrite and jlink. Specifically PCDISK doesn't seem to work. The situation: an A2000 with 1 meg of memory, a Bridgeboard, a 30 meg hard drive with controller on the PCside, (IE: DJMOUNTed from the amiga side for the amiga partition.) the config.sys on the pc side has the device=jdisk.sys statement. Bringing the machine up from power off boots the amiga and PC sides, after opening the bridgeboard window ffrom workbench, and clicking on PCDISK, still yields a failure of the Aread or Awrite to do anything, and Jlink fails to find the amiga side of the connection. rebooting only the bridgeboard side (CTRL ALT DEL) causes the AMIGA side CLI's etc. etc. to generate nothing but garbage on any keypresses but the PCside can now do an aread or awrite, or Jlink sucessfully. all the proper software is in its correct drawers... janus.library is in the Expansion directory and the devs: directory has the janus.device stuff in it... I'm at a loss.... any and all possible explainations would be GREATLY appreciated... thanks JpC -------------------------------------------------------------------- Jonathan P. Crone CRONEJP@UREGINA1.BITNET cronejp@mcl.UUCP Heisenberg might have been here...
bill@cbmvax.UUCP (Bill Koester CATS) (03/07/89)
In article <8903060008.AA03781@jade.berkeley.edu> CRONEJP@UREGINA1.BITNET (Jonathan Crone) writes: >I've been trying to get a friends A2000 to work prorperly with >aread, awrite and jlink. Specifically PCDISK doesn't seem to work. > >The situation: >an A2000 with 1 meg of memory, a Bridgeboard, a 30 meg hard drive >with controller on the PCside, (IE: DJMOUNTed from the amiga side >for the amiga partition.) > >the config.sys on the pc side has the device=jdisk.sys statement. > >Bringing the machine up from power off boots the amiga and PC sides, > >after opening the bridgeboard window ffrom workbench, and clicking on >PCDISK, >still yields a failure of the Aread or Awrite to do anything, and >Jlink fails to find the amiga side of the connection. >rebooting only the bridgeboard side (CTRL ALT DEL) causes the >AMIGA side CLI's etc. etc. to generate nothing but garbage on any >keypresses but the PCside can now do an aread or awrite, or Jlink >sucessfully. > >all the proper software is in its correct drawers... >janus.library is in the Expansion directory >and the devs: directory has the janus.device stuff in it... > If you reboot the PC with ctrl-alt-del and watch the screen you should see one of two messages. With the original software the messge will be Janus Handler found at segment E000 The new V2.0 software has the message Janus Handler x.xx Janus Library x.xx If you do not see one of these messages it means that the custom janus software in PC.boot is not being found or that the memory window is not set properly. First make sure the following files are present. for the original V1.0 software SYS:Expansion/Janus.Library SYS:Expansion/Janus.Library.info SYS:sidecar/pc.boot SYS:sidecar/2500prefs for the V2.0 software SYS:Expansion/Janus.Library SYS:Expansion/Janus.Library.info SYS:PC/System/pc.boot SYS:PC/System/2500prefs Then use pcprefs to set the memory window to E000 for an XT or sidecar or D000 for an AT. You must see the message mentioned above before things will work prepperly. BK