C64 Bounty Bob Strikes Back Question

All questions about how to use KryoFlux go here.
User avatar
IFW
Posts: 3080
Joined: Mon Nov 08, 2010 2:42 pm

Re: C64 Bounty Bob Strikes Back Question

Post by IFW »

sncboom2k wrote:Edsel007 - I used your commands as stated above, here they are:

dtc -p -b-8 -fdumpdir\Raw_Dumps\%1\%1_ -i -i2 -y -g2 -i23 -t10 -l8

dtc -p -m1 -fdumpdir\Raw_Dumps\%1\%1_ -i0 -fdumpdir\G64_New\%1.g64 -y -g2 -i22 -l8

It produced a G64 that would attach to VICE, but it fails to pass the copy protection check at the very 1st step.
That's as far as I got using my original batch file, so we must be missing something somewhere.

Not sure it matter, but my BBSB is v1.2

Thanks,
Sncboom2k
The additional protection: the disk must be write protected, otherwise junk is being transferred to the c64 :)
You must write protect the g64 produced. Set the read-only file attribute, then Vice tells the emulated system that the disk is write protected.
sncboom2k
Posts: 147
Joined: Sat Jul 21, 2012 5:33 am

Re: C64 Bounty Bob Strikes Back Question

Post by sncboom2k »

Ah see? lol - had to be something so simple. That worked and now the G64 works just fine.

Thanks IFW

Sncboom2k
Post Reply