Re: PC as 1541

On 4/27/2011 9:14 AM, Gábor Lénárt wrote:
> On Wed, Apr 27, 2011 at 07:38:12AM -0500, Jim Brain wrote:
>
> Ahaam, well, I thought ZoomFloppy is "only" for connecting 1541 (or similar
> IEC drive) to your PC, and not what I need, but then it seems I am wrong.
Glad I could help add some color to the discussion.
>>
>> I think the best solution is an IEC-based device that utilizes
>> Ethernet.  Such a device could attach to local or remote storage, as
>> well as remote repositories.
> Maybe yes, but I don't want to most complex sultion ever first ;) Anyway,
> with cross-development I mean about various sources, needs "make" and
> Makefile to build. Then it's easy to - let's say - write "make final" (or
> whatever) which would mean to transfer the generated disk image (from
> current build) to the "virtual 1541" which is connected - let's say - via
> USB with PC, but via IEC bus with C64. But you're right, maybe it does not
> make too much difference to have the connection between "virtual 1541" and
> PC as an USB cable or an ethernet link (especially if the uC which aimed to
> emulated 1541 can support both - at least some PICs can do it), and ethernet
> is much more versatile from this point of view, as you noted. First, I
> thought there is an easy "DIY" solution which can be built from spare parts
> (PC parallel port cable) but I think I have to admit that for my "ultimate"
> goal it's not so easy (especially because I would like to use modern OS -
> Linux - on the development PC, which makes it hard to run an 1541 emulation
> software on the PC, if it's not even impossible: using an MSDOS machine just
> too complex again, then I can be fine even with SD2IEC or so, just I have to
> move memory card all the time between the device and PC, which is not so
> nice).
I don't see the issue as overly complex.  Things like C2N232 and an 
IEC->USB or IEC->Ethernet solution can simply run a small app on the 
machine that checks for a file or something on the PC side.  If the file 
shows up, dload it and run.  Or, the file could be a marker file, which 
includes a start address and the name of a file to load and sys.  There 
are a number of variations on the theme, and I think most cross dev 
solutions employ something like that.

I will say, along Marko's comment, LPT and COM ports are gone from most 
machines.  I doubt you'll find much contemporary development tooling 
that uses those older methods.  However, if you do have an older 
machine, 64HDD should fit your goals.  Run 64HDD on an old PC with LAN 
network drivers.  Set up 64HDD to use a LAN share, and Cross dev to that 
share from another, Windows/Linux machine.

Jim

Jim

       Message was sent through the cbm-hackers mailing list