Topic: Commodore 64 (Read 568 times)

madmab · « **Reply #30 on:** August 19, 2011, 12:33:00 AM »

Yeah... unfortunately the Vice X-port ported (1.12) seems to have very limited savestate support in regards to using disks. It is really hard for me to verify because it seems finding version 1.12 for windows to verify this is a bit difficult to do.

The savestate code is a bit odd and I suspect it does not work with disks on 1.12.

Anyways what I can tell you is after loading a savestate it gets caught in the emulated cpu code execution loop. Doing who knows what..

I'll have to try one more thing and "force" a remount of the disk in drive 1 after loading a save state and see what it does. I suspect it's attempting to read from a disk that is no longer "mounted" after a save state load.

Retroplay · « **Reply #31 on:** August 19, 2011, 03:08:00 AM »

QUOTE(madmab @ Aug 19 2011, 08:33 AM)

Yeah... unfortunately the Vice X-port ported (1.12) seems to have very limited savestate support in regards to using disks. It is really hard for me to verify because it seems finding version 1.12 for windows to verify this is a bit difficult to do.

http://www.zimmers.n.../old/index.html

madmab · « **Reply #32 on:** August 19, 2011, 04:42:00 AM »

QUOTE(Retroplay @ Aug 19 2011, 05:08 AM)

http://www.zimmers.n.../old/index.html

Thanks but that's just the source code.

fatfonzi · « **Reply #33 on:** August 19, 2011, 08:59:00 AM »

QUOTE(madmab @ Aug 19 2011, 07:33 AM)

I'll have to try one more thing and "force" a remount of the disk in drive 1 after loading a save state and see what it does. I suspect it's attempting to read from a disk that is no longer "mounted" after a save state load.

Would that explain why its freezing when using a single disk game. Remember this happens regardless of which game is played. I have recreated this freezing using both single disk and multi disk games (tried 3 different multi disk games and 2 different single disk games). I've also tried them in zipped and unzipped formats with the same results. The only factor seems to be the length of time played before this bug occurs.

*EDIT*
I no longer have the savestaes for the single disk games that froze but I can recreate it tonight and get it to you if you need it.

fatfonzi · « **Reply #34 on:** August 26, 2011, 09:56:00 PM »

QUOTE(madmab @ Aug 19 2011, 07:33 AM)

Yeah... unfortunately the Vice X-port ported (1.12) seems to have very limited savestate support in regards to using disks. It is really hard for me to verify because it seems finding version 1.12 for windows to verify this is a bit difficult to do.

The savestate code is a bit odd and I suspect it does not work with disks on 1.12.

Anyways what I can tell you is after loading a savestate it gets caught in the emulated cpu code execution loop. Doing who knows what..

I'll have to try one more thing and "force" a remount of the disk in drive 1 after loading a save state and see what it does. I suspect it's attempting to read from a disk that is no longer "mounted" after a save state load.

Hey Madmab,
How's it looking? Is it a lost cause? I understand if you hadnt had the time to investigate it fully yet but just asking if there is any progress?

Thanks

Retroplay · « **Reply #35 on:** August 27, 2011, 09:09:00 AM »

QUOTE(madmab @ Aug 19 2011, 12:42 PM)

Thanks but that's just the source code.

Sorry I thought it was the source you were looking for.

waal · « **Reply #36 on:** August 27, 2011, 09:49:00 AM »

Hey,

What version of Hawkeye do you suggest me ? The tape version seems to be more complete with a title screen ? What about about the disks versions ?

Retroplay · « **Reply #37 on:** August 27, 2011, 11:39:00 AM »

Lurid & Tricycle's crack has title screen, docs and highscore saver.
http://www.gb64.com/...d=3446&d=18&h=0

waal · « **Reply #38 on:** August 27, 2011, 12:35:00 PM »

Thanks !

madmab · « **Reply #39 on:** August 30, 2011, 12:51:00 AM »

QUOTE(fatfonzi @ Aug 26 2011, 11:56 PM)

Hey Madmab,
How's it looking? Is it a lost cause? I understand if you hadnt had the time to investigate it fully yet but just asking if there is any progress?

Thanks

I'm not really sure what I'm gonna do. It's real hard to determine what the emulator is doing after the savestate load. If I could find an executable of version 1.12 for windows it would give me a better idea of what the emulator is supposed to do.

Hopefully a diffcomp of two later versions of Vice64 will hopefully allow me to fix the lockup after playing for a certain period of time issue.

fatfonzi · « **Reply #40 on:** August 30, 2011, 10:00:00 AM »

QUOTE(madmab @ Aug 30 2011, 07:51 AM)

I'm not really sure what I'm gonna do. It's real hard to determine what the emulator is doing after the savestate load. If I could find an executable of version 1.12 for windows it would give me a better idea of what the emulator is supposed to do.

Hopefully a diffcomp of two later versions of Vice64 will hopefully allow me to fix the lockup after playing for a certain period of time issue.

I think this is Vice v1.12.

http://www.multiupload.com/SD7RZ03V1V

madmab · « **Reply #41 on:** August 31, 2011, 02:49:00 AM »

Thanks but oddly enough I think that is the OS/2 version.

Talk about odd....

fatfonzi · « **Reply #42 on:** August 31, 2011, 08:15:00 AM »

How Bout this one...

http://www.multiupload.com/SFOHCVHOXD

madmab · « **Reply #43 on:** September 01, 2011, 12:54:00 AM »

Nope sorry.. that's just the source which I already have... (IMG:style_emoticons/default/smile.gif)

ok I perused over the source differences between 1.17 and 1.18 where the supposed (playing longer than 72 minutes crashes)

There are only two changes that seem like they possibly may be the cause. One I can implement.. the other, however, the structure of the code changed so much that it would be rather difficult. Although I suspect the 2nd one wont make much difference.

So I got another question. If I load a game with a cracktro or something and let it play (without doing anything) will the emulator eventually crash? (Presumably after 72 minutes). If that is the case then it might make it easier for me to determine where it is crashing (assuming it's not getting stuck in some stupid emulated cpu loop). (IMG:style_emoticons/default/ohmy.gif)

Thanks

This post has been edited by madmab: Sep 1 2011, 10:10 AM

fatfonzi · « **Reply #44 on:** September 01, 2011, 08:27:00 AM »

QUOTE(madmab @ Sep 1 2011, 07:54 AM)

So I got another question. If I load a game with a cracktro or something and let it play (without doing anything) will the emulator eventually crash? (Presumably after 72 minutes). If that is the case then it might make it easier for me to determine where it is crashing (assuming it's not getting stuck in some stupid emulated cpu loop).

Thanks

Let's clarify something. I have played many vice64 games longer than 72 minutes without my emu crashing. Actually my vice emu has never crashed "WHILE" playing a game. What actually happens is after playing a game for so long and then saving it will not let me load that game through the savestate again because it just freezes the xbox. So basically I can play my vice emu for any length of time without crashing but I would have to restart any game from the beginning because the savestate feature crashes the emu. But again, it only crashes the emu if I try to load a savestate of a game that I have played for longer than an hour (thats an estimate).
I hope that makes sense
Thanks

Author Topic: Commodore 64 (Read 568 times)