----------Snoopy to the Rescue--------- A 4am crack 2015-10-04 --------------------------------------- Name: Snoopy to the Rescue Genre: educational Year: 1984 Publisher: Random House, Inc. Media: double-sided 5.25-inch floppy Previous cracks: Apple Mafia Identical cracks: #441 Garfield Double Dares #188 Garfield, Eat Your Words Both sides are bootable. I'll start with side A. ~ Chapter 0 In Which Various Automated Tools Fail In Interesting Ways COPYA immediate disk read error Locksmith Fast Disk Backup unable to read any track EDD 4 bit copy (no sync, no count) copy works Copy ][+ nibble editor all tracks use standard prologues (address: D5 AA 96, data: D5 AA AD) but modified address epilogue (AA DE EB instead of DE AA EB) Disk Fixer ["O" -> "Input/Output Control"] set Address Epilogue to "AA DE EB" Success! All tracks readable! T00 -> looks like a DOS 3.3 RWTS T11 -> DOS 3.3 disk catalog T01,S09 -> startup program is "STEX" Why didn't COPYA work? modified epilogue bytes (every track) Why didn't Locksmith FDB work? modified epilogue bytes (every track) EDD worked. What does that tell us? probably just structural protection (modified epilogue), no nibble check Next steps: 1. capture RWTS with AUTOTRACE 2. convert disk to standard format with Advanced Demuffin 3. patch RWTS to read standard format ~ Chapter 1 In Which We Attempt To Use The Original Disk As A Weapon Against Itself [S6,D1=original disk] [S6,D2=blank disk] [S5,D1=my work disk] ]PR#5 CAPTURING BOOT0 ...reboots slot 6... ...reboots slot 5... SAVING BOOT0 CAPTURING BOOT1 ...reboots slot 6... ...reboots slot 5... SAVING BOOT1 SAVING RWTS ]BRUN ADVANCED DEMUFFIN 1.5 ["5" to switch to slot 5] ["R" to load a new RWTS module] --> At $B8, load "RWTS" from drive 1 ["6" to switch to slot 6] ["C" to convert disk] --v-- ADVANCED DEMUFFIN 1.5 (C) 1983, 2014 ORIGINAL BY THE STACK UPDATES BY 4AM =======PRESS ANY KEY TO CONTINUE======= TRK:................................... +.5: 0123456789ABCDEF0123456789ABCDEF012 SC0:................................... SC1:................................... SC2:................................... SC3:................................... SC4:................................... SC5:................................... SC6:................................... SC7:................................... SC8:................................... SC9:................................... SCA:................................... SCB:................................... SCC:................................... SCD:................................... SCE:................................... SCF:................................... ======================================= 16SC $00,$00-$22,$0F BY1.0 S6,D1->S6,D2 --^-- ]PR#5 ]CATALOG,S6,D2 C1983 DSR^C#254 174 FREE A 002 HELLO B 002 FIELD1 B 002 FIELD2 B 002 FIELD3 B 002 FIELD4 B 002 FIELD5 B 002 FIELD6 B 012 LVL1 B 013 LVL2 B 014 LVL3 B 011 LVL4 B 011 LVL5 B 011 LVL6 B 021 BUFDAT1 B 021 BUFDAT2 B 021 BUFDAT3 B 021 BUFDAT4 B 003 HISCOR B 012 STEX B 002 RB B 012 BPLATE.CPRS B 021 PDATA B 002 MSCDAT B 008 CP.CPRS B 042 FRONT B 032 BACK B 018 GRIVER ]BRUN STEX ...crashes... [S5,D1=DOS 3.3 master disk] ]PR#5 ]BRUN STEX,S6,D2 ...program loads and runs... So it doesn't like Diversi-DOS 64K (the DOS on my work disk). It's probably accessing DOS functions directly or assuming the RWTS parameter table is at specific address, instead of using the vectors on page 3. But it works when I boot an unmodified DOS 3.3 first, so it isn't checking for its original DOS at runtime. [S6,D1=demuffin'd copy] ]PR#6 ...grinds then crashes... The demuffin'd disk can't read itself. This is not unusual. ~ Chapter 2 In Which We Remove All Traces Of Copy Protection Using An Automated Tool That I Wrote For Just Such An Occasion [S6,D1=demuffin'd copy] [S5,D1=my work disk] ]PR#5 ]BRUN PDP ; fix epilogue byte checking in RWTS T00,S03,$91 change AA to DE T00,S03,$9B change DE to AA T00,S06,$AE change AA to DE T00,S06,$B3 change DE to AA Side B has identical protection. Quod erat liberandum. ~ Epilogue On first boot, the game asks for your name and displays it on a "this disk belongs to" screen on each subsequent boot. This information is stored in T02,S09, along with a count of how many times you've booted the disk. Zeroing out the entire sector causes the disk to ask for your name again on the next boot. I've left both sides in this pristine state. --------------------------------------- A 4am crack No. 467 ------------------EOF------------------