|
Post by Dr. Video / ADDiXiON BBS on Apr 11, 2005 12:47:37 GMT -5
For some reason, I could not write a D64 file to my 1571 this morning with Leif's shell program. Worked fine using the command line interface.
In the GUI Shell, I could read the directory, get status, etc. At first, it would not format, then it did format. But when I tried to transfer d64 to 1571, the drive blinked, then control went back to the GUI. It's like it aborted or something. Drive status reported no errors.
Has anyone had that kind of behavior before?
|
|
|
Post by Dr. Video / ADDiXiON BBS on Apr 11, 2005 13:26:39 GMT -5
Well it turns out the D64 file was EMPTY! GUICbm4Win aborts and doesnt waste my time, where as the command line interface copies a blank disk!
So everything appears to work as it should I guess...
|
|
|
Post by Leif Bloomquist on Apr 11, 2005 13:32:35 GMT -5
I usually don't check this subforum, lucky I spotted this That does sound strange, as the GUI doesn't do anything except call the command line tool. Can you check the "Preview cbm4win commands" option, and tell me what the command line is?
|
|
|
Post by Dr. Video / ADDiXiON BBS on Apr 11, 2005 14:23:18 GMT -5
I figured it out.... the d64 has a space character in the filename. Apparently this screws up cbm4win.... i just took the space out and it worked!
|
|
|
Post by Leif Bloomquist on May 2, 2005 8:45:57 GMT -5
Just to be sure, does the space screw up cbm4win, or gui4cbm4win?
|
|
|
Post by Dr. Video / ADDiXiON BBS on May 2, 2005 20:10:07 GMT -5
I can't remember now. If you want, just put a space in some file name and see if you can transfer it to a 1541 with the command line interface, then your program.
I suspect cbm4win is the issue if all your prg does is passthrough commands to it. It might be necessary to include quotes on the command line to make it work, and if so, your program would need to do the same possibly.
|
|