Read-only archive of the Armageddon Games Forums Archive (2000–2026) · About this archive

Zelda Classic 2.10

335 replies · 213,384 views · Started 01 January 2005

mjctraider wrote:I have all the support files and I tried this:

(Go to Start -> Run -> Browse; select the file you want to run -> add "-windowed [-gdi]" without the quotes -> OK)

My computer didn't like that. So I have no idea what to do. I am lost as to what to do.

Well, I'm out of ideas. Did you try getting the latest version of DirectX off the Microsoft homepage like DN suggested? If so, what's the last line in the "allegro.log" file say?

Dark Nation wrote:As for the alternate music, thing, do you have a better suggestion for what to call it? It was originally called Tracker Music, but once MP# and OGG support was added, it needed a different name.

"Normal" and "Alternate"? Or "Preferred" and "Backup"? I dunno, like I said it just felt kinda backwards to me.

They gonna update the Zelda Classic site soon with this info? It'd be nice to know all the new features that have been implemented, not the bugs fixed necessarily, just the new features. 😊

mjctraider wrote:I have all the support files and I tried this:

(Go to Start -> Run -> Browse; select the file you want to run -> add "-windowed [-gdi]" without the quotes -> OK)

My computer didn't like that. So I have no idea what to do. I am lost as to what to do.

Remove the brackets around -gdi

Man, I haven't used Zelda Classic in ages. I'd really like to try it out now when the Linux version is released.

All right, so, anyone who happened to read the original words of this post shoudl ignore them, as I have belatedly realize that downloading the proper support files for a given program usually fixes most problems. Again, thanks for the hard work, DN.

</edit>

Ok I install Microsoft C++ seeing how I am a programmer and all and decided to deguq the program instead of selecting the button to not send the report to Microsoft. The problem that pops up in C++'s debugger is the following:

Unhandled exception in zelda-w.exe(ALLEG41.DLL):0XC000005: Access Violation.

Stepping into the code it seems to be a call to a pointer perhaps to that memory location if I remember my programming correctly. Maybe this will shed some light on my problem and maybe someone will come up with a solution. till then I am going to continue to figure it out myself in case no one has any solutions for me.

Edit:

Ok finally the allegro.log updated instead of being blank evertime I tired to run zelda-w.exe and I would assume this confirms a problem with alleg41.dll, but I could be wrong, still a beginner programmer.

Zelda Classic v2.10 (Build 0)
Checking Files... OK
Allocating quest path buffer (280b/280b)...OK
Allocating map buffer (185.94k/186.21k)... OK
Allocating string buffer (6.75M/6.93M)... OK
Allocating door combo buffer (159.50k/7.09M)... OK
Allocating dmap buffer (51.00k/7.14M)... OK
Allocating combo buffer (1.49M/8.63M)... OK
Allocating color data buffer (158.11k/8.79M)... OK
Allocating tile buffer (8.00M/16.78M)... OK
Allocating trash buffer (97.66k/16.88M)... OK
Allocating item buffer (6.00k/16.89M)... OK
Allocating weapon buffer (2.00k/16.89M)... OK
Allocating guy buffer (14.00k/16.90M)... OK
Initializing Allegro... OK
Allocating bitmap buffers... OK
Loading data files:
Zelda.Dat...OK
Fonts.Dat...OK
SFX.Dat...OK
Loading saved games... Save file not found. Creating new save file.OK
Initializing sound driver... OK
Setting video mode...

You should download the alleg41.dll that DN links to in his post. It's newer than the versions in the older ZC betas, so that might help. I know it's gotten me a step closer to fixing my issues.

mjctraider.
When you first download everything into your folder, you should open zquest-w.exe and play the lost woods midi.
The program then will write you several files, ag.cfg, allegro.log etc.
THEN open zelda-w.exe and it should work.

If all else fails, read the instructions 😊

so let me clarify, have their been any recent uploadings of ZC 2.10 with bug fixes after the initial release on New Year's DN?

DFW, any "bug fixes" would be released as something like ZC 2.11 or something. As far as I've seen 2.10 is the latest released.

This is much better than b183 was, but I don't like a few things. Here's a list of them:

  • Static in the little map in the bottom right corner of the screen. Same for the tile editor when there's no tile copied. This is slowing things down, and it makes it hard to see the little 3x3 pixel screen selector box in the map, especially when the static seems to be a light gray, and the box is white. I would rather have it just be black again. Maybe an option to turn it off?
  • Again, in the tile editor, I don't like only having the gray grid now. The gray grid is making it very difficult for me to make tiles. Making the spacebar change between gray and the dark blue again might be good.
  • Yet another tile editor thing. This time, it deals with selecting tiles. Can we have a key combination such as Ctrl-Shift-Home, that would select tiles from the currently selected tile to the beginning of the row of tiles. Also, that would require Ctrl-Shift-End to go to the end. It's kind of annoying when you have to use the arrow keys just to do it, since the home and end keys go to the beginning and end of the current tile page now.
  • The light gray in the palette editor is making it hard to select the right colors. A very dark gray ( 4,4,4 ) , is looking like pure black with the gray backgrounds.
Overall, it's a very good job, execpt for those slight annoyances. I also have a couple questions about some things:

1) How do you go about using the Full Link Tile Modifier rule? I've tried a couple things, and haven't had any luck.
2) Will there ever be an option to not only change the Before Map and After Map minimaps for DMaps, but also the other areas in the subscreen that use the borders, like the border around the items?

Also, I found one slight bug. Not too serious, but still annoying. In the Map Colors window, when you click the 3 tab, sometimes you can't edit those 5 values. Going out of the Map Colors window, and coming back in usually fixes it though.

To move to the beginning or end of the current tile line, do a ctrl-left or ctrl-right. To select the same, hold shift down while moving.

At some point, I hope to make the subscreen almost completely customizable, maybe even to the extent of being DMap- (or level-) oriented (like the map tiles).

Questwizard88 wrote:1) How do you go about using the Full Link Tile Modifier rule? I've tried a couple things, and haven't had any luck.

The rule just makes the variable modifier of an item affect most of link's tiles I believe. With it off, the variable mod for items only affect a few of link's tiles.

Freedom wrote:mjctraider.
When you first download everything into your folder, you should open zquest-w.exe and play the lost woods midi.
The program then will write you several files, ag.cfg, allegro.log etc.
THEN open zelda-w.exe and it should work.

If all else fails, read the instructions 😊

I did that on several occasions and still get the access violation. Maybe it just doesn't like me. Well just for laughs I thought I'd try it again for the 20th time and reinstalled everything and ran zquest first and surprise surpirse it gave me the access violation again and here's what is in the allegro.log file:

ZQuest v2.10 (Build 0)
Allocating MIDI buffer (9.84k/9.84k)... OK
Allocating map buffer (185.94k/195.78k)... OK
Allocating string buffer (6.75M/6.94M)... OK
Allocating door combo buffer (159.50k/7.10M)... OK
Allocating dmap buffer (51.00k/7.15M)... OK
Allocating combo buffer (1.49M/8.64M)... OK
Allocating color data buffer (158.11k/8.80M)... OK
Allocating tile buffer (8.00M/16.79M)... OK
Allocating trash buffer (97.66k/16.89M)... OK
Allocating item buffer (6.00k/16.89M)... OK
Allocating weapon buffer (2.00k/16.90M)... OK
Allocating guy buffer (14.00k/16.91M)... OK
Allocating combo undo buffer (1.49M/18.40M)... OK
Allocating tile undo buffer (8.00M/26.40M)... OK
Allocating file path buffers (1.25k/26.40M)... OK
Initializing Allegro... OK
Loading data files:
ZQuest.Dat...OK
ZGP.Dat...OK
Fonts.Dat...OK
OK
Initializing sound driver... OK

I click on zquest it flashes three times and appears to be in windowed format and then the message box appears on the window. I give up and I'm waving the white flag.

Here's mine
This may have been ask, but I really don't want to go back over all of these posts to see.
What are you running, XP?
What version of direct X?
IF XP are you Adminisrator?
If XP, do you have window blinds turned off?
.

ZQuest v2.10 (Build 0)
Allocating MIDI buffer (9.84k/9.84k)... OK
Allocating map buffer (185.94k/195.78k)... OK
Allocating string buffer (6.75M/6.94M)... OK
Allocating door combo buffer (159.50k/7.10M)... OK
Allocating dmap buffer (51.00k/7.15M)... OK
Allocating combo buffer (1.49M/8.64M)... OK
Allocating color data buffer (158.11k/8.80M)... OK
Allocating tile buffer (8.00M/16.79M)... OK
Allocating trash buffer (97.66k/16.89M)... OK
Allocating item buffer (6.00k/16.89M)... OK
Allocating weapon buffer (2.00k/16.90M)... OK
Allocating guy buffer (14.00k/16.91M)... OK
Allocating combo undo buffer (1.49M/18.40M)... OK
Allocating tile undo buffer (8.00M/26.40M)... OK
Allocating file path buffers (1.25k/26.40M)... OK
Initializing Allegro... OK
Loading data files:
ZQuest.Dat...OK
ZGP.Dat...OK
Fonts.Dat...OK
OK
Initializing sound driver... OK
Loading Quest...

Decrypting...okay.
Opening...okay.
Reading Header...okay.
Reading Rules...okay.
Reading Strings...okay.
Reading Doors...okay.
Reading DMaps...okay.
Reading Misc. Data...okay.
Reading Items...okay.
Reading Weapons...okay.
Reading Maps...okay.
Reading Combos...okay.
Reading Color Data...okay.
Reading Tiles...okay.
Reading MIDIs...okay.
Reading Cheat Codes...okay.
Reading Init. Data...okay.
Reading Enemy Data...okay.
Done.
Loading Quest...

Decrypting...okay.
Opening...okay.
Reading Header...okay.
Reading Rules...okay.
Reading Strings...okay.
Reading Doors...okay.
Reading DMaps...okay.
Reading Misc. Data...okay.
Reading Items...okay.
Reading Weapons...okay.
Reading Maps...okay.
Reading Combos...okay.
Reading Color Data...okay.
Reading Tiles...okay.
Reading MIDIs...okay.
Reading Cheat Codes...okay.
Reading Init. Data...okay.
Reading Enemy Data...okay.
Done.
Saving Quest...

Writing Header...okay.
Writing Rules...okay.
Writing Strings...okay.
Writing Doors...okay.
Writing DMaps...okay.
Writing Misc. Data...okay.
Writing Items...okay.
Writing Weapons...okay.
Writing Maps...okay.
Writing Combos...okay.
Writing Color Data...okay.
Writing Tiles...okay.
Writing MIDIs...okay.
Writing Cheat Codes...okay.
Writing Init. Data...okay.
Writing Enemy Data...okay.
Encrypting...okay.

mjctraider wrote:I click on zquest it flashes three times and appears to be in windowed format and then the message box appears on the window. I give up and I'm waving the white flag.

Have you tried using some of the different video options to see if that fixes your problem? Try adding either of these (but not both at once) to the command line for Zelda or ZQuest:

-fullscreen -directx -safe
-fullscreen -directx -soft
-windowed -gdi

You had added some of these before, but improperly I think. Also, are both the player *and* the quest editor crashing in this manner? If any of these options work for the player, please report to me what "Help->Video Mode" (or something similar) says. You wouldn't be using a laptop by any chance would you?

Freedom wrote:Here's mine
This may have been ask, but I really don't want to go back over all of these posts to see.
What are you running, XP?
What version of direct X?
IF XP are you Adminisrator?
If XP, do you have window blinds turned off?
.

Yes I am running XP, the very very latest version of DirectX is on my computer I am the adniistrator and I have no idea what window blinds are, first time using XP for me. And to answer another persons question both the player and quest maker crash in the same manner and no I am not using a labtop. I'm getting a headache from trying to get it to work and I apologize for giving anyone else a headache for trying to help me out here.

It's a good thing it isn't 2.0 cause I heard that version was nothing but a virus.

I am hoping I can make a good sequel to my 1.90 quest "Realm of Shamanock"

I've not been in for a long long long long long time and most of you may not even know me. But Great job on the new zelda classic!
I'm downloading it now(stupid dial-up -.-) I can't wait to try it out :3

MJC, what do you mean, it flashes three times? Do you mean it flashes like it's being minimized and restored, or like it's going from fullscreen to windowed and back? If that's the case, then I've had your problem before. And the solution is deceptively simple...

My good sir, you must click. Click like a mad man, like a spastic telegraph operator. You must be John Henry in the race against the steam powered clicking machine. You must click as if your very life, and lo, the very fate of the universe depended on it! For God's sake man, for all that is well and good in this world, YOU MUST CLICK!!

Well, dramatics aside, if you are indeed suffering from the same problem as me, rapid clicking ought to solve the process whenever this sort of thing occurs. You see, I'm not a coding genius or anything, but I have a theory. My theory is that ZC has a disagreement with Windows XP about resolutions, and I'm not talking about their respective goals for 2005. ZC runs at a very low resolution in full screen, something like 320x400 or something low like that. I think. And Windows does not like this. No, not at all! So being the bigger program that it is, it simply gives ZC a big old slap upside the head in the form of an access violation. ZC tries in vain on it's own, struggling to convice XP to let it run in a low res full screen, but alas, it has no luck.

But the clicking solution does work, for as the movie TRON taught us, Users have 1337 powers. If you click fast enough, you're liable to get a click onto ZC itself, and NOT the desktop. This is important, because for whatever reason, if you do it right, ZC wins the screen resizing battle and opens. I've had this issue with other programs, and not just ZC, so I don't think it's an issue exclusive to ZC. It's just a resolution thing.

Hopefully this will help. Good luck!

I still would had loved to see that NSF feature implemented in the future version of Zelda Classic, since it seems like a wonderful idea to begin with.. Especially the feature to use Tracker MOD/XM/S3M and IT files to boot with that for the happiness. =)

Oh yes, anyone whom is specialized in programming the NSF area for the future ZC software, you might want to have a gander at this:

http://www.slack.net/~ant/nes-emu/libs.html#Game_Music_Emu

It's hard to say what it is doing it flashes so fast that all I really see is the top part of the window for zquest or the player and then the display box appears about sending the error report. It doesn't look like it is being minimized and then restored. I tried clicking like a mad man and once there was a box that appeared about a problem with the sound and then twice while clicking like a mad man the screen went completely blue and to the middle left side of the screen in white letters was zquest-w. I have no idea what that means.

Edit: I doubt this would change anything, but would the fact that I am using XP Professional make it more difficult for me to get both the quest editor and the player to work?

Dark Nation wrote:10. Added a new bp option to the tile grabber. Pressing the 'N' key will switch the grab style to NES. This allows tiles to be lifted more easily from NES games.

11. Added a new option to the grabber. Pressing the 'B' key will cycle through the different bit plane settings (1, 2, NES, 4, and 8).

Ok, what exactly do these do? I've been pushing them when in the grabber, but it seems as though nothing happens.

They only seem to work if you have a file other than one of the following opened:

  • Exported Graphics Pack
  • Exported Tiles
  • Images

Yes I did tried and a message box appeared saying something along the lines of cannot find file or invalid path or something like that. Even saw an example I believe was in this link which showed the properties window of a shortcut for zelda-w.exe and tried that and still my computer didn't like it. I'll keep on trying till I've finally had it and I'll just give up and forget about it.

Did you download the first three files DN listed at the beginning of this post? ZC for windows, the Alleg41.dll, and the third support archive (many files)?

Also, do yourself a favor and turn error reporting off. Microsoft doesn't give a crap about most of the errors you get anyway.

mjctraider,
Do other versions work in your computer?

I run windows 98, BUT My brother runs XP PRO, and I took him a copy of the 184 over, slapped it all on his puter' and it ran like a top.
I didn't have to do any tweaking.
I haven't taken over the 2.10 for him yet, but I bet it would be the same.

I had some similar problems as you a while back, when I decided to start using the windows versions instead of the DOS, I discovered that the alleg41.dll's I had were all mixed up, how this happened I have no clue, since when I D/L a new version everything goes in a new folder.
I just kept swapping out what I had until they would run, and then tweaked them from there.
It did the same thing you describe about, the window just flashed then closed.