Page 2 of 2

Re: Sega system 24 disks

Posted: Tue Nov 17, 2015 11:57 am
by ordyne
Is it possible that kryoflux could make a 1:1 copy of system 24 disks? It doesn't seem to work for Hotrod which AFAIK has a different disc structure to every other system 24 game and is most troublesome to backup.

Re: Sega system 24 disks

Posted: Wed Nov 18, 2015 9:10 pm
by mr.vince
If it's index aligned, it should work already... but... can you post more info on the format? Links with specs etc.? Saves time finding out on our end.

Re: Sega system 24 disks

Posted: Thu Nov 19, 2015 11:10 am
by ordyne
Apparently its the sector sizes which differ in Hotrod.

Bonanza bro etc
// Sector Size
// 1 2048
// 2 2048
// 3 2048
// 4 2048
// 5 2048
// 6 1024
// 7 256

track_size = 0x2d00;



Hotrod
// Sector Size
// 1 8192
// 2 1024
// 3 1024
// 4 1024
// 5 512
// 6 256

track_size = 0x2f00;

Does this help?

Re: Sega system 24 disks

Posted: Thu Nov 19, 2015 11:14 am
by ordyne
Here is the extract from the mame driver.


DRIVER_INIT_MEMBER(segas24_state,hotrod)
{
io_r = &segas24_state::hotrod_io_r;
io_w = &segas24_state::hotrod_io_w;
mlatch_table = 0;

// Sector Size
// 1 8192
// 2 1024
// 3 1024
// 4 1024
// 5 512
// 6 256

track_size = 0x2f00;
}

DRIVER_INIT_MEMBER(segas24_state,bnzabros)
{
io_r = &segas24_state::hotrod_io_r;
io_w = &segas24_state::hotrod_io_w;
mlatch_table = segas24_state::bnzabros_mlt;

// Sector Size
// 1 2048
// 2 2048
// 3 2048
// 4 2048
// 5 2048
// 6 1024
// 7 256

track_size = 0x2d00;
}

DRIVER_INIT_MEMBER(segas24_state,sspirits)
{
io_r = &segas24_state::hotrod_io_r;
io_w = &segas24_state::hotrod_io_w;
mlatch_table = 0;
track_size = 0x2d00;
}

DRIVER_INIT_MEMBER(segas24_state,sspiritj)
{
io_r = &segas24_state::hotrod_io_r;
io_w = &segas24_state::hotrod_io_w;
mlatch_table = 0;
track_size = 0x2f00;
}

DRIVER_INIT_MEMBER(segas24_state,dcclubfd)
{
io_r = &segas24_state::dcclub_io_r;
io_w = &segas24_state::hotrod_io_w;
mlatch_table = segas24_state::dcclub_mlt;
track_size = 0x2d00;
}


DRIVER_INIT_MEMBER(segas24_state,sgmast)
{
io_r = &segas24_state::hotrod_io_r;
io_w = &segas24_state::hotrod_io_w;
mlatch_table = 0;
track_size = 0x2d00;
}

DRIVER_INIT_MEMBER(segas24_state,qsww)
{
io_r = &segas24_state::hotrod_io_r;
io_w = &segas24_state::hotrod_io_w;
mlatch_table = 0;
track_size = 0x2d00;
}

DRIVER_INIT_MEMBER(segas24_state,gground)
{
io_r = &segas24_state::hotrod_io_r;
io_w = &segas24_state::hotrod_io_w;
mlatch_table = 0;
track_size = 0x2d00;
}

DRIVER_INIT_MEMBER(segas24_state,crkdown)
{
io_r = &segas24_state::hotrod_io_r;
io_w = &segas24_state::hotrod_io_w;
mlatch_table = 0;
track_size = 0x2d00;
}

DRIVER_INIT_MEMBER(segas24_state,roughrac)
{
io_r = &segas24_state::hotrod_io_r;
io_w = &segas24_state::hotrod_io_w;
mlatch_table = 0;
track_size = 0x2d00;
}

Re: Sega system 24 disks

Posted: Fri Nov 20, 2015 12:36 pm
by IFW
The content does not matter as long as the tracks are index synced - with the current DTC version.
Just do a 1:1 copy (read/write stream); if the data read out was good, the copy will be good as well.
A future DTC version will also remove the index sync only limitation from the stream copy mode.

Re: Sega system 24 disks

Posted: Fri Nov 20, 2015 3:42 pm
by ordyne
I'm away for a week but will try it when I get back but I'm sure that's what I already tried without success.

Re: Sega system 24 disks

Posted: Wed Feb 03, 2016 10:45 am
by anormal
Maybe it can be copied by a miriad of old pc copiers, Teledisk, Anadisk, Copy2PC, Copywrite, the newest and i think and maybe the most powerful is Copymaster by Serge Pachkovsky, last version is 0.44a

Yo could try them, but you'll need an old PC.
From Copymaster doc:
CM is a bit-copying utility specifically designed to utilize most
abilities of AT floppy disk controller (FDC). CM can work with 360K, 1.2M,
720K or 1.44M floppy drives using any recording density. With 300 RPM 5ะป-inch
drive and most FDCs, it can copy FM (single density) floppies. It can even
copy disks, which have different recording density on the SAME track -
feature which no one software or hardware bit-copier have.
CM works with FDC in polling mode, which requires CPU services each 16
mks for high density drive. Therefore, CM requires relatively fast CPU - 6
MHz / 0 WS 80286 is an absolute minimum. Because CM operations are tightly
related with computer hardware, it will not work on computers even with minor
incompatibilities. IBM's own PS/2 model 50 (and probably some other MCA
machines) is an example.