Welcome, Guest. Please login or register.

Author Topic: A lost art? Star Commander!  (Read 2373 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline LocalH

  • Newbie
  • *
  • Join Date: Nov 2002
  • Posts: 39
    • Show all replies
Re: A lost art? Star Commander!
« on: August 20, 2004, 01:12:37 AM »
Hm, it's been a while myself, but I seem to remember a timing setting (and I think there was an auto-calibration in at least one version of SC that I used), that had to be set depending on your CPU speed. When I was transferring disks, I was using a regular X1541 cable, and the only problem I had, was that occasionally after dumping a whole disk, I'd get a 74 error - but the contents of the dump were 100% correct.
 

Offline LocalH

  • Newbie
  • *
  • Join Date: Nov 2002
  • Posts: 39
    • Show all replies
Re: A lost art? Star Commander!
« Reply #1 on: August 20, 2004, 02:16:21 AM »
If you're running in a single-tasking environment such as DOS, it's best to turn async off, as SC will have realtime control over the parallel port and thus should be able to handle a faster synchronous transfer. However, if you ever want to use SC from within the Win9x GUI (I did this occasionally for C64 development), you'll have to turn async on. If you plan to use SC in both DOS mode and the GUI, I found it best to make two copies of the config file, one with async on, one with it off. Then, I merely set up two batch files - one for async and one for synchronous. Each batch file echo'd a bit of information regarding the circumstances that are best for each setting, then copied the respective config file to the name SC expected, then launched SC.

However, if you can't get SC to work at all with async off, it's worth trying it with async on. It'll probably only really work in Normal mode, but an async normal mode is better than none at all.