Posted By
Ian Coog
on 2011-01-14
15:12:12
|  Yape 1.0 (32bit) problems
Hi, I wanted to know if anyone else noticed a problem using Yape 1.0 (32bit), I use it on Win98se.
Under the File menu almost nothing works anymore, even if i use the menu (autostart, load prg, save prg/attach d64) or press the f7/f8/shift f8/alt-d it only acts as if Enter was pressed and nothing happens. Same goes for tape/attach tape.
The pic snapshot work, but all the other menus that are supposed to pop up a dialog do not work
Forgot to link the resources in the exe or it's simply because it uses some "wide char" only APIs? for example
0 FreeEnvironmentStringsW ¦KERNEL32.DLL
0 GetEnvironmentStringsW ¦KERNEL32.DLL
it's not actually correct to use unicode functions on
Then examining further the exe imports I can see it probably uses some missing imports
8 <n/a> ¦COMCTL32.dll <- ??
1 <n/a> ¦ DSOUND.dll <- ??
2 <n/a> ¦ MSVFW32.dll ¦ <- ??
Also I noticed that the exe resource version is unchanged from 0.86
I hope it can be fixed. If there is no one able to fully test under win98 I can do it with pleasure =)
|
|
Posted By
Gaia
on 2011-01-15
08:20:10
| Re: Yape 1.0 (32bit) problems
Hmm... sounds as if the Win98 version might have been compiled from a non-clean state (with remnants of the XP/Vista/7 build). Sorry, it may have escaped my attention. Anyway, I will upload a new test build for ya soon and post the link here. Thanks for the report and stay tuned.
[UPDATE]
OK, here it is: http://yape.homeserver.hu/download/Yape101Win9x.zip
|
|
Posted By
Csabo
on 2011-01-15
15:25:32
| Re: Yape 1.0 (32bit) problems
Cool! Can anyone else help test this? (I don't have access to any Win98 machines.)
|
|
Posted By
Ian Coog
on 2011-01-16
02:55:07
| Re: Yape 1.0 (32bit) problems
Tested it and still doesn't work. At least now it doesn't store an Enter in the keyboard buffer, still no dialog ever popups, only the msgbox in the file association telling that i need xp/vista (wtf?  D)
|
|
Posted By
Gaia
on 2011-01-16
14:26:16
| Re: Yape 1.0 (32bit) problems
OK, the resource version is irrelevant. The Win9x eclusion in the file associations was intentional (back in the day). Apparently, it was not due to a corrupted rebuild... likewise it is linked against the ASCII WinAPI calls. How long are you experiencing this issue? Appeared in 1.0 only?
EDIT: ok I guess I found it. Win98 apparently does not like the OPENFILENAME Structure's lpstrFile member to be pointed to a function heap static variable. Please redownload the package.
|
|
Posted By
Ian Coog
on 2011-01-17
15:35:14
| Re: Yape 1.0 (32bit) problems
yeah the structure sizes problem is a common error when writing win9x compatible progams using winxp dev tools (visual C later than 2003), I already stumbled on it a dozen of times and so happened to other Commodore crosstools developers in the past years =)
I'd like to know which package to download now.
http://yape.homeserver.hu/download/Yape101Win9x.zip is dated 16/1/2001 and still is not working, the full yape pack on the site
http://yape.homeserver.hu/download/yape1.0.zip
is not changed. None of both open the dialogues here. :/
EDIT: you're still passing the wrong value
.0041274F: C705F025C30058000000 mov d,[00C325F0],000000058 ;' X'
it should be 0x4c on win98, not 0x58
I hacked the exe in all occurrences of GetSaveFileNameA and GetOpenFileNameA calls and now it works =)
|
|
Posted By
Gaia
on 2011-01-17
15:52:19
| Re: Yape 1.0 (32bit) problems
So you mean that the size of OPENFILENAME is wrong? Unfortunately, that's compile time constant but I am doing this:
// Fill in the OPENFILENAME structure
ZeroMemory(&sf, sizeof(sf));
sf.lStructSize = sizeof(sf);
... which ought to be OK.
I might have updated the headers or somesuch but will figure out thanks for the hint 
|
|
Posted By
Ian Coog
on 2011-01-17
15:57:24
| Re: Yape 1.0 (32bit) problems
yeah, latest win sdk uses winxp constants, you better make a function that check os major version, if 4 set the 1st member to 0x4c, if 5 or more use sizeof(OPENFILENAME)
|
|
