CompuServe Thread

#Janus 2.0

3 messages in this thread
#106870From: Don Curtis/SYSOPMay 29, 1990 1:39 AM
John, Yes…by using AREAD or AWRITE to/from a Shared Hard Drive (JLinked, MakeAB, or JANUS device)…you're trying to pass the data thru the Amiga- MS-DOS interface (JANUS) both directions at once. That is a tough job for MS-DOS to handle…thus the i/o errors. Look at it this way…read from the MS-DOS side and pass it to the Amiga side … Amiga side sees it goes to JH0: and immediately passes it back to the MS-DOS side…thus MS-DOS is trying to do read/writes at the same time and gets confused. If you can use an intermediate device, such as first writting it to an Amiga side floppy and when that's done, passing it back to JH0: via COPY…the problems will go away. Of cousre, if you try to pass it back (the copy to JH0:) while you're trying to do something else on the MS-DOS side…the problems will reappear…and probably more severely. Don
#106898From: John G. AtaMay 29, 1990 10:32 AM
I understand. However, isn't it strange that I can aread/awrite a file from the PC hard disk to jh0: with no problem? Now, I would have thought that would have been a problem, not the floppy!! John
#107030From: Don Curtis/SYSOPMay 29, 1990 11:55 PM
John, No…it's not strange…the read/writes go to the same physical device, and it too can only do one at a time…so it reports itself busy momentairly. While from the floppy, it's a separate physical device so just as the MS-DOS side is getting to do another read/write to the floppy…it gets this other message to do a hard disk read/write and gets confused. At least that's the way I understand it. Don