Image Map Image Map
Page 1 of 2 12 LastLast
Results 1 to 10 of 18

Thread: ZoomFloppy / OpenCBM/ 2031LP and 8050

  1. #1

    Default ZoomFloppy / OpenCBM/ 2031LP and 8050

    Hey there!

    As I continue working my way through my PET gear, I've turned my attention to the 2031LP and the 8050 drives. There's definitely something up in my PET and I'm awaiting 3446 chips. In the meantime, I hooked an edge connector up to my ZoomFloppy to give it a GPIB interface.

    Does anyone have any experience using a ZoomFloppy to talk to a 2031 or an 8050? I've got the ZoomFloppy talking to cbmctrl... I've updated the firmware to the latest (v8 ). Neither drive seems to respond to a status or detect query, though both of them react to a reset... I was thinking I wired my interface backwards except that the reset works.

    Any thoughts?
    Last edited by dhoelzer; November 12th, 2019 at 10:50 AM.

  2. #2

    Default

    What OS are you using? And do you own a 1541 drive? I had the weird experience that under Windows 7 I was able to read and write floppies with the 1541 but things didn't work for my 8250LP. Never found out the reason.
    With kind regards / met vriendelijke groet, Ruud Baltissen

    www.baltissen.org

  3. #3
    Join Date
    Feb 2009
    Location
    Southern California, USA
    Posts
    2,705

    Default

    Quote Originally Posted by dhoelzer View Post

    Does anyone have any experience using a ZoomFloppy to talk to a 2031 or an 8050?
    I thought they got the 8050 interface working. However I have a 4040 drive and ZoomFloppy does not work with it. It seems they put very little effort into the software debug of ZoomFloppy with the IEEE-488 drives.

  4. #4

    Default

    Quote Originally Posted by Ruud View Post
    What OS are you using? And do you own a 1541 drive? I had the weird experience that under Windows 7 I was able to read and write floppies with the 1541 but things didn't work for my 8250LP. Never found out the reason.
    Not currently, but it works fine with my internal 1571 on the 128DCR. Obviously, that's serial GPIB rather than parallel GPIB.

    I was originally working from Windows, but had to switch over to MacOS in order to compile OpenCBM from source to support the v8 zoomfloppy firmware.

  5. #5

    Default

    Quote Originally Posted by dave_m View Post
    I thought they got the 8050 interface working. However I have a 4040 drive and ZoomFloppy does not work with it. It seems they put very little effort into the software debug of ZoomFloppy with the IEEE-488 drives.
    Yes, I saw that. Actually, that's why I updated to the v8 firmware over v7, which required recompiling; none of the released opencbm installs include support for it.

  6. #6
    Join Date
    Jan 2012
    Location
    Connecticut, USA
    Posts
    2,302

    Default

    Hi I am jumping in this midpoint. Are you saying the zoomfloppy does NOT read/write to the 8050 floppy drive unit? I have not tried to connect my 8050 to the zoomfloppy unit yet. I did try it with my SFD-1001 which is also a commodore ieee488 floppy and could not get it to actually write a disk.

  7. #7
    Join Date
    Feb 2009
    Location
    Chattanooga, TN - USA
    Posts
    858
    Blog Entries
    1

    Default

    A long time ago I did use my zoomfloppy with my 8050 drive.
    It worked fine.

    Later,
    dabone

  8. #8

    Default

    Quote Originally Posted by VERAULT View Post
    Hi I am jumping in this midpoint. Are you saying the zoomfloppy does NOT read/write to the 8050 floppy drive unit? I have not tried to connect my 8050 to the zoomfloppy unit yet. I did try it with my SFD-1001 which is also a commodore ieee488 floppy and could not get it to actually write a disk.
    I am saying that... and I'm trying to figure out if it's the drive, my wiring, or something else. . It doesn't write to my 2031LP either, but both are supported.

    Again, cbmctrl reset will trigger either drive if it's connected, but nothing else works *at all*

  9. #9

    Default

    I have a 2031 (not the LP version) and didn't have much luck using ZoomFloppy with it, but to be fair I didn't spend a lot of time on it.
    Since I have a good 1541, I just use that. The 2031 is fully read/write compatible with the 1541 so the disks are interchangeable.

  10. #10

    Default

    Quote Originally Posted by dhoelzer View Post
    It doesn't write to my 2031LP either, but both are supported.
    IMHO if it is able to communicate with one IEEE drive, it should work for all IEEE drives. I have a small project, CBM-PC, where a PC emulates more or less a CBM. It is meant to create disk images by asking the drive to send the content of every sector of the inserted disk. I need to know what type of drive is attached because the number of tracks and sectors/track can differ. But I am using the same protocol for all the drives.

    So I think you ran into the same problem I had: not being able to communicate with any IEEE drive. So far nobody found the reason or came with a solution.
    With kind regards / met vriendelijke groet, Ruud Baltissen

    www.baltissen.org

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •