|
Re: AppleWin 1.29 supports .WOZ now [message #384837 is a reply to message #384830] |
Wed, 10 July 2019 08:36 |
TomCh
Messages: 242 Registered: November 2012
Karma: 0
|
Senior Member |
|
|
On Wednesday, 10 July 2019 00:30:07 UTC+1, Steve Nickolas wrote:
> My face when.
>
> It'll certainly help with filecracks to have AppleWin's debugger instead
> of MAME's.
>
> -uso.
Hi Steve,
You beat me to it... although I'm a little hesitant as at least one game's copy protection check is failing (Wizardry III). But AppleWin is successfully able to run all of Applesauce/John Morris's test v1.3 .woz images.
Current limitations are:
.. images are read-only
.. only support for 5.25" image types
Here's the link for those that are interested in trying it:
https://github.com/AppleWin/AppleWin/releases/tag/v1.29.0.0
btw. I extended the (undocumented) debugger's 'disk info' command so that the precise track (to 0.25) and phase (to 0.50) are shown.
Tom
|
|
|
Re: AppleWin 1.29 supports .WOZ now [message #384840 is a reply to message #384837] |
Wed, 10 July 2019 09:40 |
Steve Nickolas
Messages: 2036 Registered: October 2012
Karma: 0
|
Senior Member |
|
|
On Wed, 10 Jul 2019, TomCh wrote:
> On Wednesday, 10 July 2019 00:30:07 UTC+1, Steve Nickolas wrote:
>> My face when.
>>
>> It'll certainly help with filecracks to have AppleWin's debugger instead
>> of MAME's.
>>
>> -uso.
>
> Hi Steve,
>
> You beat me to it... although I'm a little hesitant as at least one
> game's copy protection check is failing (Wizardry III). But AppleWin is
> successfully able to run all of Applesauce/John Morris's test v1.3 .woz
> images.
>
> Current limitations are:
> . images are read-only
> . only support for 5.25" image types
>
> Here's the link for those that are interested in trying it:
> https://github.com/AppleWin/AppleWin/releases/tag/v1.29.0.0
>
> btw. I extended the (undocumented) debugger's 'disk info' command so
> that the precise track (to 0.25) and phase (to 0.50) are shown.
>
> Tom
>
I'm sure it required some major hacking to get THIS far.
I only checked it with the one I had on hand, which was Impossible
Mission. (Tried to filecrack it. I had trouble even with the Two Knives
Tan crack, so not surprised I had trouble doing so here.)
-uso.
|
|
|
Re: AppleWin 1.29 supports .WOZ now [message #384851 is a reply to message #384837] |
Wed, 10 July 2019 19:19 |
TommyGoog
Messages: 112 Registered: January 2013
Karma: 0
|
Senior Member |
|
|
On Wednesday, July 10, 2019 at 7:36:21 AM UTC-5, TomCh wrote:
> Hi Steve,
>
> You beat me to it... although I'm a little hesitant as at least one game's copy protection check is failing (Wizardry III).
>
> Tom
Hi Tom,
Hmmm, Wizardry III? I remember that. Do you need to see the Wizardry III copy protection source code with my old comments explaining what I think the code is trying to read on track $22?
Tommy
|
|
|
Re: AppleWin 1.29 supports .WOZ now [message #384871 is a reply to message #384851] |
Thu, 11 July 2019 14:01 |
TomCh
Messages: 242 Registered: November 2012
Karma: 0
|
Senior Member |
|
|
On Thursday, 11 July 2019 00:19:42 UTC+1, googleeyes wrote:
> On Wednesday, July 10, 2019 at 7:36:21 AM UTC-5, TomCh wrote:
>> Hi Steve,
>>
>> You beat me to it... although I'm a little hesitant as at least one game's copy protection check is failing (Wizardry III).
>>
>> Tom
>
> Hi Tom,
>
> Hmmm, Wizardry III? I remember that. Do you need to see the Wizardry III copy protection source code with my old comments explaining what I think the code is trying to read on track $22?
>
> Tommy
Hi Tommy,
I think I have the Wizardry III copy protection documented. See here: https://github.com/AppleWin/AppleWin/issues/662
But if you think I've missed something then please chip in.
Thanks.
|
|
|
|
|
|
|
|
|
|
Re: AppleWin 1.29 supports .WOZ now [message #386880 is a reply to message #386867] |
Tue, 10 September 2019 15:55 |
Steve Nickolas
Messages: 2036 Registered: October 2012
Karma: 0
|
Senior Member |
|
|
On Tue, 10 Sep 2019, Michael AppleWin Debugger Dev wrote:
> Kids these days -- spoilt with debuggers. Back in my day we used NMI and
> saved the entire contents of RAM or boot-traced it through the stack and
> text pages.
I'm basically doing the exact same thing with the debugger, though. XD
-uso.
|
|
|