Zoom Floppy w/ Mac Os X
c/g_gfx
mac and start transfering to my c64 floppy with no software? Or will I
need to create or find a program that will work with this device?
Nate Lawson
Mac OS X is supported but you need to install OpenCBM via a portfile. So
you need to install Mac Ports, then libusb-legacy, then opencbm. It's
not a point and click install but perhaps someone will build a .pkg for you.
--
Nate
c/g_gfx
this? Thanks.
Nate Lawson
"xum1541" is the name for the firmware in the ZoomFloppy and related
devices. You should follow these instructions to install OpenCBM.
The ZoomFloppy has a manual also that everyone should read. It is being
reviewed and will be released soon.
Dragos
it just doesn't work. Not sure if its a version issue (I run the
latest Snow Leopard) or what, but no love. Someone should definitely
put together and installer.
Nate Lawson
> I have the xu1541 and I followed the directions on lallafas blog and
> it just doesn't work. Not sure if its a version issue (I run the
> latest Snow Leopard) or what, but no love. Someone should definitely
> put together and installer.
>
> On Jan 15, 11:31 am, Nate Lawson <n...@root.org> wrote:
>> http://lallafa.de/blog/opencbm-on-mac/
You'll have to give more info. We have at least two users on 10.6 and it
works for both of us.
Did you see the manual?
http://www.root.org/%7Enate/c64/ZoomFloppy-Manual-1.0a.pdf
Do you get a compile error or something?
--
Nate
Pete Rittwage
Did you mean xum, or are you trying to use the older usb adapter?
On Jan 27, 2011 9:42 AM, "Dragos" <mgla...@gmail.com> wrote:
I have the xu1541 and I followed the directions on lallafas blog and
it just doesn't work. Not sure if its a version issue (I run the
latest Snow Leopard) or what, but no love. Someone should definitely
put together and installer.
On Jan 15, 11:31 am, Nate Lawson <n...@root.org> wrote:
> http://lallafa.de/blog/opencbm-on-mac/
>
...
Dragos
no point in getting the xum (yet)
On Jan 27, 10:58 am, Pete Rittwage <rittw...@gmail.com> wrote:
> Did you mean xum, or are you trying to use the older usb adapter?
>
Nate Lawson
support nibbling, etc. I really recommend you get a ZoomFloppy
(xum1541-based) device as it is *more* likely to work for you.
-Nate
Dragos
why get the new one?
Nate Lawson
different between xu1541 and xum1541. Testing one has no bearing on
whether the other will work.
It's like saying plugging in a USB mouse proves that your USB flash
drive will work. About the only thing it proves is that the physical
port is active -- nothing about the software support.
If you want xu1541 support, try the OpenCBM list. I think Christian
Vogelsgang, the author of that blog, has an xu1541.
https://lists.sourceforge.net/lists/listinfo/opencbm-user
Thanks,
Nate
Alexander Oberhuber
Just got my Zoomfloppy and downloaded OpenCBM from Spiro Trikaliotis'
homepage as described.
It DOES NOT HAVE a "windrv" directory with the USB-drivers.
Where to properly get the USB-drivers from please?
Yours
ATT
Alexander Oberhuber
Okay I fixed this issue myself, obviously all files should be downloaded from
http://www.root.org/~nate/c64/xum1541/ -> correct it in the manual!@#!!
I installed it.
I got an error "DLL could not be loaded".
I checked windows/system32 and replaced manually "opencbm.dll" ->
20.480 bytes now instead of 19.xxx bytes earlier.
Then I was running runtest.bat:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\WINPROG\opencbm-ZoomFloppy-1.0a>runtest.bat
Found the following drives:
error: no xum1541 device found
error: no xum1541 device found
libusb/xum1541:: Das System kann die angegebene Datei nicht
finden. ("System cannot find file")
You should see your drive detected above. If not, please see the
ZoomFloppy manual for troubleshooting tips.
Grrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr....
What now?
Nate Lawson
> Okay I fixed this issue myself, obviously all files should be downloaded
> from
> http://www.root.org/~nate/c64/xum1541/ -> correct it in the
> manual!@#!!
I have updated the manual to 1.0b to say in multiple places not to use
the 0.4.x series and removed any links in the install section to OpenCBM.
> I installed it.
> I got an error "DLL could not be loaded".
> I checked windows/system32 and replaced manually "opencbm.dll" -> 20.480
> bytes now instead of 19.xxx bytes earlier.
First, make sure to run "instcbm --remove" to remove your old 0.4.x
install you first did. Then, follow all the steps in the manual,
including installing the USB drivers.
> Then I was running runtest.bat:
>
> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
>
> C:\WINPROG\opencbm-ZoomFloppy-1.0a>runtest.bat
> Found the following drives:
> error: no xum1541 device found
> error: no xum1541 device found
> libusb/xum1541:: Das System kann die angegebene Datei nicht finden.
> ("System cannot find file")
>
> You should see your drive detected above. If not, please see the
> ZoomFloppy manual for troubleshooting tips.
>
> Grrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr....
> What now?
That means your ZoomFloppy can't be found. It is not connected or the
USB drivers weren't installed from the windrv dir. Please see the
troubleshooting section of the manual, which will direct you to go
through the installation steps from the beginning.
--
Nate
Alexander Oberhuber
>That means your ZoomFloppy can't be found. It is not connected or the
>USB drivers weren't installed from the windrv dir.
Nope, Sir. It *was* connected and the drivers *were* proper.
That's the bad news.
The good news is: I tried several other drives and a naked 1571 ran,
atlast, fine.
The bad news is: The Zoomfloppy hardware does not detect every drive.
It seems to have problems with some old 1541 drives which work *fine*
on my c-64.
Anyway: Just where is the fabled super-speed of the heretofore
never-been-used burstmode of the 1571?
I figured several command lines for d64copy myself (--help, yeah) and
couldn't get burst-speed...
Oh, and BTW: How to update, if ever necessary, the HEX file for the Zoomfloppy?
Alex
Nate Lawson
>> That means your ZoomFloppy can't be found. It is not connected or the
>> USB drivers weren't installed from the windrv dir.
>
> Nope, Sir. It *was* connected and the drivers *were* proper.
The message you gave (no xum1541 found) is only reported if the adapter
itself can't be detected. If a drive is not attached by the adapter is,
it does not print an error message.
See if you can reproduce it.
> That's the bad news.
> The good news is: I tried several other drives and a naked 1571 ran,
> atlast, fine.
> The bad news is: The Zoomfloppy hardware does not detect every drive. It
> seems to have problems with some old 1541 drives which work *fine* on my
> c-64.
Are there any unpowered devices on the IEC bus? All drives in the chain
must be powered. How many drives on the chain? Total cable length?
If there is only one drive connected at a time, please report ROM
version and drive types that can't be detected.
> Anyway: Just where is the fabled super-speed of the heretofore
> never-been-used burstmode of the 1571?
> I figured several command lines for d64copy myself (--help, yeah) and
> couldn't get burst-speed...
SRQ burst nibbling mode is not implemented in the firmware yet. You can
use parallel cables for fast transfers. I doubt we'll ever implement
regular 128 burst mode since it's so slow (3.5 KB/s reads, 400 byte/s
writes).
> Oh, and BTW: How to update, if ever necessary, the HEX file for the
> Zoomfloppy?
When the first firmware update comes out, we'll document the process and
include an easy-to-use utility. Right now it is too difficult a process
and if users get it wrong, they have to short wires together on the
expansion header to recover.
--
Nate
Jim Brain
>
> I have updated the manual to 1.0b to say in multiple places not to use
> the 0.4.x series and removed any links in the install section to OpenCBM.
file that does not have the version and revision in it. That way, we
can distribute the link to the document without it getting stale all the
time. Obviously, it requires updating the alias.... Or, maybe sending
folks to a page that does not change, with the document link that does?
Jim