Andy <arie...@gmail.com>: May 18 04:48AM -0700
Unfortunately not skilled enough with a C64 and haven't used it in years. I
do not remember how to format a disk on the actual C64, though i suppose I
could look into it. I did not mean to convince anyone I had done this!
On Wednesday, May 17, 2023 at 8:27:02 AM UTC-4 Spiro Trikaliotis wrote:
|
RETRO Innovations <go4r...@go4retro.com>: May 18 09:26AM -0500
On 5/18/2023 4:31 AM, Andy wrote:
> I did that, the format continued on for 5 minutes. I don't see how
> it's the zoomfloppy if it's connecting and accepting commands buth GUI
> and CLI.
Yeah, I stand corrected. I am surprised that a 64 format completes
quickly, but a ZF one would run longer and never finish.
Which CBM machine did you try the format with?
Jim
|
RETRO Innovations <go4r...@go4retro.com>: May 18 09:27AM -0500
On 5/18/2023 6:48 AM, Andy wrote:
> years. I do not remember how to format a disk on the actual C64,
> though i suppose I could look into it. I did not mean to convince
> anyone I had done this!
Oh, I mis understood then.
To format a disk on a 64, it's open 15,9,15,"no:jim,ji":close15
Jim
|
Andy Riecker <arie...@gmail.com>: May 18 10:31AM -0400
I am swapping back and forth between CBMTransfer 2 Beta and trying the CLI
with cbmctrl.
I tried
cbmctrl open 15,9,15,"no:jim,ji":close15
it aborted saying Not Enough Parameters
On Thu, May 18, 2023 at 10:27 AM RETRO Innovations <go4r...@go4retro.com>
wrote:
|
Spiro Trikaliotis <an-zoomfl...@spiro.trikaliotis.net>: May 18 11:24PM +0200
* On Thu, May 18, 2023 at 10:31:09AM -0400 Andy Riecker wrote:
> cbmctrl.
> I tried
> cbmctrl open 15,9,15,"no:jim,ji":close15
The command-line
OPEN 15,9,15,"NO:JIM,JI":CLOSE15
that JIM mentioned is for formatting the disk from a C64!
As your format does not finish with the ZF attached, I am absolutely
sure that you do not have an OpenCBM or ZF problem, but your drive is
faulty.
So, it would be best if you could either fix it, or try with a known
good drive.
Regards,
Spiro
--
Spiro R. Trikaliotis
https://spiro.trikaliotis.net/
|
RETRO Innovations <go4r...@go4retro.com>: May 18 04:32PM -0500
On 5/18/2023 9:31 AM, Andy Riecker wrote:
> I tried
> cbmctrl open 15,9,15,"no:jim,ji":close15
> it aborted saying Not Enough Parameters
As Spiro says, my comment was in relation to your statement about doing
this from a c64. It will only work from there. And, it does look like
I have a typo. It should be
open15,9,15,"n0:jim,ji":close15
Where n0 is n zero, not n shiftO.
letters should be typed in as written from the startup screen. On the
64, the chars will all be uppercase, which is fine.
Jim
|
Andy Riecker <arie...@gmail.com>: May 18 05:56PM -0400
I assume this is addressing a drive at 9, while my actual C64 drive
attached to my 64 is at 8. Regardless, when I enter the command with a
blank disk inserted in my 1541, the red light flashes and makes no noise.
Even if I was to get the disk to format correctly, I'd have no way of
getting my homebrew d64 file to the disk. I was able to format the disk
successfully by using the ZoomFloppy and the CLI. "cbmformat 9 GAMES,4" was
the example given in the docs, and once I submitted the command I pulled
the power to the ZF. I was able to get a directory through CBMTransfer
multiple times in a row. I know at least the ZF works for reading disks
properly. What I can't do now is transfer the d64 to the disk as every
attempt results in the error I reported in my 2nd or so post the "Warning:
read error". I'm more lost than ever ;)
On Thu, May 18, 2023 at 5:32 PM RETRO Innovations <go4r...@go4retro.com>
wrote:
|
RETRO Innovations <go4r...@go4retro.com>: May 18 07:48PM -0500
I think this might be better solved via a Zoom Call. Do you have any
availability Friday afternoon/evening to get on a quick
Discord/Zoom/Hangout/Slack call so we can debug that way? I think I am
confused about your setup(s), so I am giving bad information on how to
diagnose.
Let me know and let me know which technology is preferred, as I think I
can use all of the above.
Jim
|
Stephen Chrzanowski <pont...@gmail.com>: May 18 09:09PM -0400
Andy;
The thing about the 1541/1571/1581 is that they have their own DOS built
in. So if you get the Zoom to start TALKING to initiate the command to do
the work, the Zoom has done its job. When you close the channel, the Zoom
is waiting for the drive to finish its business. The drive itself does the
formatting via it's own ROM, not by will of the PC or by the will of any
code on the Zoom.
All the Zoom is doing is sending a few bytes of data to the drive (In this
case) to send a command over the IEC. The command is received and the
drive itself does the work. All of it. The Zoom is just a bridge, it
doesn't DO anything.
I had a lot of fights with the Zoom and my PC and I gave up on it for a
couple of years. I couldn't even get the USB drivers to work at all. It
threw a good chunk of errors and such. I came back to it probably 6 months
ago, and I somehow managed to knock some sense into it, and have it working
with Win8 and Win10. I was able to get D64s copied, and get some disk
images ripped that weren't copy protected to G64. Now, I'm using a 1571,
not a 1541 to do disk imaging, but even for a 1541-II, a simple format
should work.
For example, if you send the OPEN command, and leave the CLOSE command
until later, you'll note that the OPEN statement returns immediately. Once
you send the CLOSE command, the prompt waits until the drive is done.
On Thu, May 18, 2023 at 5:24 PM Spiro Trikaliotis <
|