color whack & wiping the save file

Try build 1194 and see if it's any better...I don't know. dup; http://armageddongames.net/showthread.php?45204-crashes-in-player

1194?
most recent offered is 1190 and I have it
and the color thing is bad, even have to reboot to get it to stop sometimes

For Windows Vista/7

If your talking about the purple/pink frame in the ZC Player around the gameplay area and similar graphical corruption in the Quest Editor, try closing all instances of Explorer.exe before launching the game.

If your using Windows XP, it is likey a virus scanner, messenger program or something with a "always on top" feature that causes it.

The other sure fire way to get rid of it under both XP and Vista/7 is to just run them in a Window, preferably 640x480 or bigger as 320x240 is tiny these days :P .

I believe it's that same issue franpa but it's gotten a lot worse in the betas since 1099
it also now effects the player as well and never did before for me.
it seems to also be worse in the colors that it effects, in zquest color set 0 tiles on the screen are changed, this never happened before.
sometimes exiting and re-entering doesn't fix it, it always did before, now I have to reboot.

It actually deleted my save file for the player exiting to try to reset the colors.

Are you running in fullscreen mode when this happens?

yes yes yes one yes to answer you and the other two because this stupid ass forum requires 10 digits to post.

and it doesn't occur in Windowed mode? try my solution of using Task Manager to close all instances of Explorer.exe via the Processes Tab then use Task Manager to run Zelda Classic, If it works I can make a BAT file that automates this and reloads Explorer.exe after you're done. You won't have access to the Start Menu or Windows Explorer while running the Zelda Classic Player or ZQuest, though you wouldn't have access anyways if you run these programs in Fullscreen unless you alt-tab.

In Task Manager you can click "File, New Task (Run... )" to run Zelda Classic and see if the colour corruption vanishes without any Explorer.exe process present.

no thanks.
Zelda classic needs to conform to my computer, not the other way around.
1194 is no better

It's a known bug with early direct draw games and Windows Vista/7 as well as various "always on top" or messenger programs which also run under Windows XP.

edit: bleh I remembered wrong oh well, anyways here is a post I used for a reference, the devs can look at it if they want. The thread relates to a module that when used in conjunction with Wormkit, helps solve the palette corruption problem. Wormkit is a tool that can modify the game and add new features etc. like a mod http://forum.team17.com//thread/74880/#post695558#post695558

That particular module helps resolve most cases of the problem by suspending all Explorer.exe processes while the game is in focus, when it is not the processes are resumed.

I run xp franpa.

just the fact that this has gotten so much worse in these later builds, and that this report was moved to exterminated bugs because they have no intention of trying to fix it tells me all I need to know.
I'll finish my current quest and move on to different things, I'm done with ZC at that point.
the current versions will never be anywhere near stable, and a rewrite will never happen in my lifetime.
in my opinion about 75% of the crap that L added to get it here is unnecessary crap.

Edited last post to be a little bit more clearer. I meant that the messenger programs and virus scanners and stuff that can cause it, will often also be available for XP and cause the same problems there.

For Vista/7 the problem is there from the start
For XP the problem is not present but may appear after installing some 3rd party or even 1st party applications.

oh, I hear you.
I'm not going to concern myself with it.
Just going to finish this quest up and move on.
It's only one of many problems with zelda classic nowadays
there just doesn't seem to be any real focus on having a real usable stable program here.
I guess it's nobody's fault really, just the way it is.

Well it's a known issue, there's already threads about it in limbo, and everything else you mentioned is in the the active bug list.. I don't know where else to put it. :shrug:

On my laptop this issue is non-existent since there is no anti-virus and it's set up to run as fast as possible with the least amount of processes possible. Win XP SP2. I suppose that helps confirm what franpa said about direct draw/256 colors/ pocesses etc.. It just magically works. With my desktop I always run it in windows so I don't get this problem either. However I remember back using 2.10 on my old desktop this used to happen to me a lot.

..I don't know if it's even work-around-able in ZQuest. The best I could think of is pressing SHIFT-F11 or something and having ZC reload and reset everything palette related.. (Actually this can be tested already (I think) Freedom. -Next time it happens try one of these: -Go to the palette menu and dick around with any combination loading and veiwing crap (there's too many combinations to mention) or try to grab a palette [will reset it] ) I wouldn't bet on this not working though... Or option #2: Does exiting fullscreen and going back into it fix the problem 100% of the time? If so I could add an option right next to that in the menu that will release the device context and create a new one without altering fullscreen settings or anything else.

That's really the best I could do.

I'm more concerned with the fact that it happened in the player and then deleted my sav file when I exited to get the colors back right.
that never happened before

Yes, the save game corruption/missing should be looked into.

http://blog.macuyiko.com/2009/07/solving-color-problem-red-grass-purple.html

Yeah the bat files the best method. But again, Freedom has reported in this thread about a save game corruption issue, perhaps split it from the thread and put it in it's own separate one?

[edit] I see there's some weird Delphi code there. Maybe Sean want's to add a new feature to zcLauncher? ...(I think that's written in Delphi)..

[edit2] Well I suppose this might work:

	HWND hParent			= NULL;
	HINSTANCE hInstance		= NULL;
	HWND hWnd                      = win_get_window();
	WNDPROC AllegroProc	= (WNDPROC) GetWindowLong( hWnd, GWL_WNDPROC );
	hInstance			= (HINSTANCE) GetWindowLong( hWnd, GWL_HINSTANCE );
	hParent				= (HWND) GetWindowLong( hWnd, GWL_HWNDPARENT );
	SetWindowLong( hWnd, GWL_WNDPROC, (LONG)(WNDPROC)ColorFixProc );

If the colors whack out in zquest you can switch from fullscreen to windowed and then back and it fixes it.
not a big problem.
It happening in zelda.exe and deleting the save file though.... maybe that's another issue.
Others have talked about their sav files being deleted, they weren't happy

Question: how do you know it deleted the save file? Did you look in the game directory and confirm that it was gone, or did the game tell you the file was absent when you restarted it?

Maybe you know already, but if you quit the game and restart it right away, it can get confused and think the file is missing when it's not. I just want to be sure that's not what happened here. (Granted, that shouldn't be an issue. I'll see if I can't fix that.)

Well if you exit ZC then start ZC, knowing that it takes a while to fully close. It's users fault >.> as the file won't be free for the new session until the first session of ZC finishes with it, the scenario can cause the dialog box to appear in the new session.

how do you figure it's the users fault franpa?
if you close it and open it again, it should look to the sav file you have.
"knowing that it takes a while to close".... you never sent me that memo, perhaps the program should wait until it is available, like firefox does if you try to reopen it too quick?

saffith,
that could have happened, but now it was too long ago and I really don't remember.
I know of three people who have lost their sav files, Joe, Elise, and myself, so either way it is an issue that should be addressed.

I'm not too sure about this, but let's give it a shot. Here's an alternate alleg42.dll that might fix the color issue.
http://www.mediafire.com/?zb42zdhzmmy