Announcement

Collapse

Forum Rules and Etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.


Rule 1: Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.


Rule 2: Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.



Rule 3: Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.


Rule 4: "PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.


Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Rule 5: Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.


Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.


New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.


Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

C2n232

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #31
    cbmlink and the Commodore 2040 disk drive

    I am the new owner of a Model 2040 dual floppy IEEE 488 drive for my Model 8032 PET. The disk has been updated with DOS 2 ROMs. It seems to work fine although I only have the performance test program meant for a 1541 single drive and so can only thoroughly test drive zero, but both drives seem OK. I can “New” the floppies (format) and read and write files.

    Here is my problem. I tried to transfer disk file data from the 2040 to a PC via the cbmlink software and it does not seem to work. I also tried to copy a complete image in d64 format with no success. In fact cbmlink seems to do nothing except ‘hang’ the PET when this is attempted. Cbmlink has commands for disk transfer but they don’t seem to work on the PET. Are the disk commands for the Commodore 64 and the 1541 type drives only?

    Has anyone successfully transferred data to/from a 2040 or 4040 drive using cbmlink?
    I tried using no track numbers (default) and using 1 to 35 tracks for images to no avail. I think I may be missing something.
    -Dave

    Comment


      #32
      I've written images to a PET's 8050 using cmblink, but I can't for the life of me remember how. Maybe if you run us through the steps you took it'll bring something back. Does your procedure for transferring individual files still work and how does a disk transfer differ?

      BTW: Is d64 the right format for 2040 images? I remember there was some messing about involved trying to generate d80 images for the 8050.
      Steve Maddison
      Digital, Sinclair, Commodore, homebrew Z80 and other stuff...

      Comment


        #33
        Originally posted by cosam View Post
        I've written images to a PET's 8050 using cmblink, but I can't for the life of me remember how. Maybe if you run us through the steps you took it'll bring something back. Does your procedure for transferring individual files still work and how does a disk transfer differ?
        Hi Steve,
        When I first used cbmlink, I did not have a disk so I only needed it to transfer program code from the PC to PET memory as vice versa. That works fine with the -l (load) and -s (save).
        But now I tried the File Read command (-fr switch) which I thought would transfer a disk file from the 2040 (connected to the PET) through to the PC.

        Originally posted by cosam View Post
        BTW: Is d64 the right format for 2040 images? I remember there was some messing about involved trying to generate d80 images for the 8050.
        Here I was attempting to copy the whole diskette image to the PC as a .d64 file. The only examples in the instructions were for a .d64 file or as a binary file. This is done with a 'disk read' command -dr. The full command line I used was:
        cbmlink -c pc64 0x378 -dr0, 3,1,35 FILE.D64
        I specified disk unit zero, interleave of 3, track 1 to track 35. When this did not work, I used all defaults:

        cbmlink -c pc64 0x378 -dr FILE.D64
        This did not work either. The PET just hung up. When I reset the PET, the prompt on the PC came back. I was thinking that the PET diskette format is compatible with the 1541 disk drive? I need to do some more research on formats. I am glad to read that you had some success transferring data to an 8050 drive. That gives me some hope. Thanks, Dave

        Comment


          #34
          For what it is worth, in January I successfully read two floppy disks from a 8250LP drive. I used cbmlink with the C2N232I interface connected to a CBM 610 and a custom cartridge with code to enable the cassette port. As for your second question, 4040 floppy disks should be read compatible with a 1541 so you shouldn't have to take the detour around the PET to read those.
          Anders Carlsson

          Comment


            #35
            Originally posted by carlsson View Post
            For what it is worth, in January I successfully read two floppy disks from a 8250LP drive.
            Anders, if you were reading the full diskette image, do you remember if you specified the starting and stopping track numbers in the command line or did you leave them out?
            Thanks, Dave

            Comment


              #36
              Actually I used Bill Degnan's CBMXfer, but I'm quite sure that program leaves the track numbers out. After all, the D80 format (in my case) should already have the tracks defined.

              While I don't own a working 2040, 3040 or 4040, if you like I could take the trouble of attaching a 2031 to a PET and see if I can transfer files that way. Note however I would be using the C2N232I interface rather than PC64 like you seem to use.
              Anders Carlsson

              Comment


                #37
                Originally posted by carlsson View Post
                While I don't own a working 2040, 3040 or 4040, if you like I could take the trouble of attaching a 2031 to a PET and see if I can transfer files that way. Note however I would be using the C2N232I interface rather than PC64 like you seem to use.
                Anders,
                Yes when you get a chance, please see if you can transfer a file from the disk drive to the PC and then perhaps a whole diskette image.

                I'm still looking for a C2N232 cable as it seems more universally used.

                Have you looked into the XU 1541 adapter that hooks up the 1541 drive to the USB of a more modern PC running WIN XP and OpenCBM software? I have a 1541 and am tempted to try this setup. If it worked, I think my PET 2040 drive could then read the diskette for transfer data to the PET that way.

                Comment


                  #38
                  No, I haven't considered the XU1541 since I have enough transfer cables and devices as it is, and almost all my PC's have onboard parallel ports anyway. Of course I have a classic XM1541 cable that goes to a 1541-II. I have previously used that setup to write 35 track floppy disks read on the 2031 (connected to a CBM 710).
                  Anders Carlsson

                  Comment


                    #39
                    Originally posted by cosam View Post
                    I've written images to a PET's 8050 using cmblink, but I can't for the life of me remember how. Maybe if you run us through the steps you took it'll bring something back. Does your procedure for transferring individual files still work and how does a disk transfer differ?

                    BTW: Is d64 the right format for 2040 images? I remember there was some messing about involved trying to generate d80 images for the 8050.
                    I'd love to know how to do this !!

                    I got an XE1541 cable and 1541 drive before I found out that images written on a 1541 are not compatible with the 8050

                    I've got loads of pet software as .d64 files and can't get any onto the PET, I have only managed one program (Cosmic Cosmiads) by recording to tapoe and then loading, but cause it's machine code I can't then save back to disk !!!

                    Comment


                      #40
                      You need a different kind of cable. The recommended one is a PC64 cable which connects the PC to the PET and will turn the PET into a slave. But as mentioned above, Dave had some problems using this kind of setup.
                      Anders Carlsson

                      Comment


                        #41
                        Originally posted by Panther View Post
                        I've got loads of pet software as .d64 files and can't get any onto the PET, I have only managed one program (Cosmic Cosmiads) by recording to tapoe and then loading, but cause it's machine code I can't then save back to disk !!!
                        There are various tools for manipulating at least d64 images, maybe even d80s, but I had the most success using VICE. The d64 can be attached as one drive and you can simply copy .PRGs over to a virtual 8x50 drive with a blank d80 attached. As far as I can remember the transfer of the d80 to a real disk was just a matter of following the cbmlink documentation.

                        And yes, you need the PC64 cable: DB25 at one end and PET user port edge connector at the other. Not hard to make (the pinout is in the cbmlink docs) but I did have a job finding a suitable edge connector.
                        Steve Maddison
                        Digital, Sinclair, Commodore, homebrew Z80 and other stuff...

                        Comment


                          #42
                          Originally posted by Panther View Post
                          I got an XE1541 cable and 1541 drive before I found out that images written on a 1541 are not compatible with the 8050
                          I am a little luckier I think because the 2040 is read compatible with the 1541 drive so I have more options.

                          Originally posted by Panther View Post
                          I have only managed one program (Cosmic Cosmiads) by recording to tape and then loading, but cause it's machine code I can't then
                          save back to disk !!!
                          You should be able to do this if you are at all familiar with the machine language monitor that is built into ROM. From a fresh load from tape, go into the machine language monitor with a sys 1024. Using the memory display command (.m), check from 0401H in blocks of around 0800H untill you find some code (non hex AA pattern). That is the start of the program. Record that address. Then keep going until the code ends (hex AA pattern starts again). Record the end address. At this point you have the information the save the program to disk. Use the SAVE command (.s) with the following syntax:

                          .s "0:name_of_program",08,start address in hex,end address in hex

                          Use exit command (.x) to get back to BASIC.
                          If you are not familiar with the monitor program, go to this link:

                          http://generalthomas.com/PET/BATPRO_Ref.pdf

                          and check p.60 for info on the memory display command, and p.62 for info on the save command. Some of the other commands listed need a Batpro EPROM but these are OK without it.

                          Right at the moment I am having a hard time with the pc64 cable trying to transfer files to/from my PET 2040 disk using cbmlink but I hope it is just cockpit errors. You may have better luck with the 8050.
                          -Dave
                          Last edited by dave_m; March 13, 2010, 07:47 AM.

                          Comment


                            #43
                            dave_m,

                            Many thanks for the tips, I'll give it a go as soon as I get chance, I've also enquired with a friend who's alot better than me with a soldering iron to see if he can construct a PC64 cable !!

                            Stu.

                            Comment


                              #44
                              Originally posted by carlsson View Post
                              Actually I used Bill Degnan's CBMXfer, but I'm quite sure that program leaves the track numbers out. After all, the D80 format (in my case) should already have the tracks defined.
                              Anders, I'm hurt... you don't remember who wrote CBMXfer LOL

                              Actually, as far as I can tell cbmlink continues until it gets an error on sector 0 of the current track. It increments the sectors until there is an error then moves to the next track, and when it gets an error on sector 0 it assumes it's done. I recently tried transferring a disk and it just gave up after a couple tracks with no error. Of course the banging noise told me there was an error, and the file size of the D80 was way too small.

                              Currently CBMXfer doesn't check the result but it's something I plan on implementing at some point.

                              Steve
                              WANTED: CBM-II hardware or software, PET software

                              Comment


                                #45
                                Haha. Can you spell brainfart? Sorry, of course it should say Steve Gray's CBMXfer.
                                Anders Carlsson

                                Comment

                                Working...
                                X