Re: AppleTalk

["Michael Pender" <mpender@hotmail.com>]

Bill Garber <willy46pa@comcast.net> wrote in message
NlSdnUA_1O9bVoeiU-KYvw@comcast.com">news:NlSdnUA_1O9bVoeiU-KYvw@comcast.com...
> > That's what I had in mind:
> > - select a disk image from the server (networked computer)
> > - transfer the disk image file via AppleTalk
> > - expand the disk image onto the slot 5 RAM disk
> > - run from the slot 5 RAM disk as if it were the floppy from which the
DSK
> > image was made
> > - when done, update the disk image on the server.
>
> Dude, that'll take way longer than booting it up from the
> floppy. If you run GS/OS, I believe 4 and up, you can boot
> from floppy and snag and manioulate all your files from the
> Mac. If your 3.5" disk is taking a long time to boot, you more
> than likely have too much on it. Much more than you actually
> need to operate.

That's not quite what I have in mind.  What I'm planning will be *much*
faster than a floppy.

> > Unfortunately, it sounds like this could only work with a Mac as a
> > fileserver if it were running Appleshare 3.0 and System 7.  There
remains
> > the possibility of doing this for a PC as a fileserver though.  Also, it
> > probably wouldn't work with DOS 3.3 titles without faking a Disk II
device
> > signature and replacing the RWTS interface code.
>
> PC-MacLan does work, after you're booted up and AppleShare is
> running on the GS. I can share my entire PC with the GS, but I am
> not sure there is room on a 3.5" disk for everything and that.

I have a lot of DSK files on my PC and I would like to be able to select a
disk image from the IIgs, transfer the DSK image from the PC via the
network, write the image to the RAM card, and then use the disk image on the
RAM card like a floppy.  The PC would be acting as a disk image server, not
a file server, which improves the transport speed considerably.  Once the
disk image is local, the RAM card would act like a *very* fast disk drive.

Can anyone recommend a good source for Apple II bus prototyping boards?

- Mike

(surprisingly, that question is not in the hardware hacking FAQ ;-)