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

    #46
    CBMXfer

    Anders/Steve,
    I am getting nowhere with transfers to/from the 2040 disk drive (connected to a PET) and the PC using cbmlink via pc64 cable. The PET 8032 hangs up with no disk activity or lights. I am thinking of trying CBMXfer in case I am using the wrong syntax somehow with cbmlink and let it talk to cbmlink.

    As a backup I have ordered a XM1541 cable from a company in Europe and, in a month or so when it arrives, hope to communicate with a 1541 drive (of unknown operational status) and the PC.

    Then I could sneaker-net (walk) diskettes to the 2040 drive. And since 1541 drives are supposed to be read compatible with 2040/4040 PET drives, I should be able to load programs into the PET. And finally write the files back on 2040 formatted diskettes. What a process that will be as I had better remember to initalize the diskettes properly when I switch diskettes for writing or the diskette can become corrupted.

    One problem may be how to format diskettes on the 1541 from the PC (I do not have a C64). Does any transfer software help with this issue? I do have a few old C64 diskettes but I would like to use new diskettes.
    -Dave

    Comment


      #47
      Yes, OpenCBM (cbm4win, cbm4linux) includes formatting commands. Actually the 1541 is an intelligent device so you just send the command "go format yourself" and off the drive goes to format itself.

      I will try to remember to conduct some more tests, but I fear either your PET is partly broken (bad VIA?) or your PC64 cable is not correctly made. Well, it could be your PC has a non-compatible parallel port too, something you will find out sooner or later after receiving the XM1541 cable. However your PC should be of a quite odd model in order for it to fail. Perhaps you can look it up or even better try another PC if you have one to make sure the problem does not lie on that side?
      Anders Carlsson

      Comment


        #48
        Anders,
        OK good things to check. However my parallel port in on my WIN98 Toshiba laptop (Pentium II type) so while the port should be compatible, I don't think I can use OpenCBM to format as it works on XP class machines.

        If you saw my pc64 cable, you would worry about shorts, but it does work for load and save commands (transfers to/from the PC to the PET RAM). But I'd better check the wiring. I may yet have to switch to the XU1541 USB cable so I can use OpenCBM with my WIN-XP machine.
        Thanks, Dave

        Comment


          #49
          The XM1541 cable will work with Star Commander in pure MS-DOS. As far as I remember there is no software that runs natively in Windows 98, with the exception to running Star Commander in a command window and cross your fingers it will work.
          Anders Carlsson

          Comment


            #50
            Originally posted by carlsson View Post
            The XM1541 cable will work with Star Commander in pure MS-DOS.
            That's good to know. That should be easy for me to try.

            Originally posted by carlsson View Post
            As far as I remember there is no software that runs natively in Windows 98, with the exception to running Star Commander in a command window and cross your fingers it will work.
            I will double check, but I think the cbmlink documentation says their windows version will work on Windows 98.

            Comment


              #51
              I'm unsure to what extent cbmlink supports the X-series cables, but in any case I would expect it to connect to a computer in the other end rather than a floppy drive. However I'll admit I never investigated what it can do. Perhaps you are familiar with the 64HDD software, which lets you connect a MS-DOS PC to a Commodore computer and use the PC like a virtual floppy/hard drive. That is far from your intended use, but it goes to show the IEC bus just as well lets you connect two computers together as one computer and one storage/printing device.
              Anders Carlsson

              Comment


                #52
                Success with Star Commander

                Originally posted by carlsson View Post
                The XM1541 cable will work with Star Commander in pure MS-DOS.
                Anders,
                I purchased an XM1541 cable from Europe and hooked it up to a DOS PC and a CBM 1541 Disk Drive. With Star Commander, it works like a champ. I am able to transfer files to and from the floppies and the PC. The user interface seems a bit odd, but it works.

                Then I am able to LOAD the file into my 8032 PET via the Model 2040 IEEE drive which is “read compatible” with the 1541. I then place a 2040 formatted floppy into the drive, initialize the drive to make sure the BAM is updated, and finally SAVE the file to the 2040 diskette.

                It is a bit cumbersome, but for me, it seems more reliable than the cmblink/pc64 cable method which has a habit of hanging-up too often.
                -Dave

                Comment


                  #53
                  Can someone show me where these cheap plentiful Datasettes are? I can't find any here for less than $40, and most of them go for $70 or so - quite expensive if you ask me, and my Datasette is dead.

                  Disregard this post - I didn't see that there are many pages and the comments about plentiful Datasettes are from 2009.
                  More commonly known as "Yushatak" - www.yushatak.com
                  Focused on 486 and Pentium Machines
                  I collect All-In-One PCs and Keyboard PCs, especially Compaq.

                  Comment


                    #54
                    Raven, if you like I can try to dig up a C2N and send to you for shipping costs. However since I'm overseas, it probably will get quite expensive. I can't believe they should be that expensive on the US market, but perhaps the early shift to floppy drives means less Datassettes were sold and remain than the situation is over here in Europe. Many of us European collectors are flooded in tape recorders, like for every new computer we obtain, we get two more Datassettes.

                    On regard of the C2N232, I had a long bout tonight but failed most operation. I can load simple files, but the cbmlink communication is intermittent. I don't know what is wrong, but it is quite frustrating.
                    Anders Carlsson

                    Comment


                      #55
                      Originally posted by Raven View Post
                      Can someone show me where these cheap plentiful Datasettes are? I can't find any here for less than $40, and most of them go for $70 or so - quite expensive if you ask me, and my Datasette is dead.

                      Disregard this post - I didn't see that there are many pages and the comments about plentiful Datasettes are from 2009.
                      I have a Datasette sitting in my attic that I'm not likely to use, and the shipping probably would be pretty small. It however may be a week or two before I can get up there to get it out.

                      Comment


                        #56
                        Originally posted by carlsson View Post
                        C2N232 .. I can load simple files, but the cbmlink communication is intermittent.
                        Update: After switching from CBM 8032 and VIC-20 to using a CBM 710 (or a CBM 610 for that matter), it works much better. Those CBM-II computers have a cassette port but no ROM support to use it. I wonder if it means less routines may interfer with the cbmlink process. I gotta try a bit later, but for now the CBM-II are my 8250 gateways.
                        Anders Carlsson

                        Comment


                          #57
                          Originally posted by carlsson View Post
                          Update: After switching from CBM 8032 and VIC-20 to using a CBM 710 (or a CBM 610 for that matter), it works much better. Those CBM-II computers have a cassette port but no ROM support to use it. I wonder if it means less routines may interfer with the cbmlink process. I gotta try a bit later, but for now the CBM-II are my 8250 gateways.
                          Anders,
                          As best as I can guess, when the CBM utility (plain.prg) is launched (it loads in high memory), it operates as a daemon (background process) by wedging itself into the system timer interrupt chain which allows it to 'come alive' on a periodic basis and monitor for cbmlink commands from the PC. When it 'springs into action' based on commands from the PC, perhaps infrequently it can interfere with the CBM operations based on random or asynchronous activity, who knows. The code is good but not bullet proof although the concept seems sound to me.
                          -Dave

                          Comment


                            #58
                            No idea. I've exchanged messages with my friend and the program's author Marko. He mentioned something about 16550 serial ports could cause problems, but I don't know if that is the case. However I wonder if the automated bootstrap method using c2nload is the optimum one. Perhaps it would work better if I save the server part to floppy disk or cartridge and load/run it locally instead of bootstrapping it.
                            Anders Carlsson

                            Comment

                            Working...
                            X