The following warnings occurred:
Warning [2] Undefined property: MyLanguage::$archive_pages - Line: 2 - File: printthread.php(287) : eval()'d code PHP 8.1.28 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/printthread.php(287) : eval()'d code 2 errorHandler->error_callback
/printthread.php 287 eval
/printthread.php 117 printthread_multipage



CBMSTUFF FORUM
Problem with 360k drives - Printable Version

+- CBMSTUFF FORUM (https://www.cbmstuff.com/forum)
+-- Forum: CBMSTUFF PRODUCTS (https://www.cbmstuff.com/forum/forumdisplay.php?fid=1)
+--- Forum: SuperCard Pro (https://www.cbmstuff.com/forum/forumdisplay.php?fid=3)
+---- Forum: Atari 400/800 disks (https://www.cbmstuff.com/forum/forumdisplay.php?fid=9)
+---- Thread: Problem with 360k drives (/showthread.php?tid=307)

Pages: 1 2


Problem with 360k drives - bani - 05-21-2016

SuperCard Pro Disk Archiver v1.91 - Hardware 1.1 - Firmware 1.2

SuperCard Pro Disk Archiver v1.91 seems to have a bug with 360k 48tpi drives.

Disk Type: Atari 400/800
DriveType: 48 tpi

Make Image -> archiver reads to track 22, then starts bashing the head into the stop.

It seems the DriveType is ignored and archiver tries to always double step the head. You can see it seeking much too far per track on the 360k drive.

On 96tpi drives it works fine.

a8rawconv seems to do the right thing, stepping properly on 48tpi and 96tpi drives.


RE: Problem with 360k drives - admin - 05-22-2016

Did you change the drive type to 48TPI in the pull-down menu? The pull-down menu option is not ignored, but I can certainly check that again.


RE: Problem with 360k drives - bani - 05-22-2016

yes, it is changed to 48tpi in the pull down menu. both 96tpi and 48tpi have the same effect -- it bashes into the endstop at around track 22.


RE: Problem with 360k drives - admin - 05-23-2016

OK, I will look into it. It should single step in the 48TPI setting.


RE: Problem with 360k drives - admin - 05-23-2016

The Atari 400/800 mode is broken. This is a special case because the Atari 400/800 disks are typically single sided. I made a change to correct something else with this format and it broke the 48TPI mode. To fix this it would require a re-write of quite a bit of code. Instead of doing that I am going to release an all new version of the disk copier/imager that is track/head based instead of disk type based. This way you could imagine or copy just a single side of a disk (top or bottom). It's still compatible with the image file format though.

Until this has been released you can use the C64 mode to copy/image disks successfully with 48TPI drives. The disk format really just determines the max tracks, number of heads, etc... and nothing to do with the actual copying. Flux is flux, no matter what disk is there.


RE: Problem with 360k drives - bani - 10-08-2016

any idea when the new version will be available?


RE: Problem with 360k drives - admin - 10-08-2016

I thought I had already fixed this. I will check.


RE: Problem with 360k drives - bani - 02-16-2017

(10-08-2016, 09:14 PM)admin Wrote: I thought I had already fixed this. I will check.

any news?


RE: Problem with 360k drives - admin - 02-16-2017

I had no problem making images with a 48TPI drive. You can also use the program a8rawConv to make images, including those for Atari emulators.


RE: Problem with 360k drives - Pmetzen - 02-18-2023

[quote pid="1845" dateline="1464052262"]
adminThe Atari 400/800 mode is broken.  This is a special case because the Atari 400/800 disks are typically single sided.  I made a change to correct something else with this format and it broke the 48TPI mode.  To fix this it would require a re-write of quite a bit of code.  Instead of doing that I am going to release an all new version of the disk copier/imager that is track/head based instead of disk type based.  This way you could imagine or copy just a single side of a disk (top or bottom).  It's still compatible with the image file format though.

Until this has been released you can use the C64 mode to copy/image disks successfully with 48TPI drives.  The disk format really just determines the max tracks, number of heads, etc... and nothing to do with the actual copying.  Flux is flux, no matter what disk is there.
[/quote]

So that's complete nonsense. Because of river is river. This is not true at all. And I'll tell you why. The C64 does not use track 0. It starts with Track1 and therefore no disc can work. The Atari requires gauge 0 to boot. The C64 does not need it, because in the drive is the boot sequence needed to boot the floppy disks. Therefore, track 0 is not available on floppy disk. It always starts with track1. I can set to 40 tracks in C64 mode, but if you think you have 40 tracks as is the case with the Atari, you were wrong. There are actually 41 tracks for the Atari, since track 1 of the C64 is not seen as track 0 by the Atari. It's all moved back from track 1 to 40. With the missing track 0 there are 41. Only the track 0 is not present. So much of river is river.