Netscape 4.08 doesn't fully start #1152
Comments
|
Works for me. Try the latest build from https://ci.appveyor.com/project/otya128/winevdm/builds/43431835/job/3jxor4jpuf50wub0/artifacts and if that doesn't work make a trace. |
|
Could you send your build of Netscape? I'm getting the exact same error. |
|
Never mind, it doesn't work, I'll make a trace now. |
|
Here's the trace |
|
The crash isn't in the trace. On my computer it gets too 0x150c before ending so you'll probably just have to wait longer. |
|
For whatever reason, when I tried it earlier it just hung. This is the regular result I've been getting. https://drive.google.com/file/d/1xPTVc8IsRGQ8er4wY3xAwAgwQQmpnVSq/view?usp=sharing |
|
It looks like the c runtime heap is getting corrupted as it crashes in fmalloc. It happens after the hkey_classes_root registry key is enumerated and a lot of memory allocation occurs. Snide I can't repo it I can't tell whether it's a bug in winevdm or if Netscape, which was written when the registry would have been much smaller, bugs out with so many entries. |
|
I was looking at this again and noticed you have this different plugin which is accessed close to the problem. Does removing it prevent the crash? |
|
Yes but the entire reason I'm running it is for that plugin, which is made for 16-bit (I think) and doesn't work properly on 32-bit Netscape |
|
I found a copy at http://ftp.sunet.se/mirror/archive/ftp.sunet.se/pub/pc/windows/winsock-indstate/WWW-Browsers/Plug-In/ and it doesn't crash but is a different version than yours. Do you have a link to it? |
|
You're right, it doesn't crash with that version, but it exhibits the same behaviour that I've seen in Basilisk, but this isn't an otvdm issue, rather a plugin issue. Thanks for the help! |
|
I suppose you are working on https://bluemaxima.org/flashpoint/datahub/Technologies_to_Add#EMBLAZE . If you are getting a crash when using the wayback file, if you save it then remove the archive.org javascript from the top then it won't crash. If you are getting the mci errors, place the BLZ_WAV dir with the wave files in the plugins dir then add into your netscape.ini file. BTW, I am still interested in the other crash so if you have a link to the crashing plugin... |
|
Haha, yes I am working on that, and thanks for your help. That fix does mostly work, however it does sometimes error when I close the window. It also puts this (ignore the Log Watcher). I think I may have been using a 32 bit one for the one that was crashing, the file name ended in 32 but when I looked in the metadata it said "Original filename NPBLZ16.DLL" so ¯\_(ツ)_/¯ |
|
Okay using otvdmw I was able to fix all but this one (which is actually when it opens); does it need registry? |
I can get the message to appear by going to http://web.archive.org/web/19961105063140oe_/http://www.geo.inter.net/ebz/dmo/embeded/dmoblz08.blz with otvdm.exe. It is harmless but are you saying that when you run it otvdmw.exe a console window appears and shows that message because that doesn't happen for me.
Yes, using the 32bit version would definitely cause heap corruption when verqueryvaluea is called due to the unicode to ascii conversion. |
|
Well when I start it in cmd it says that in the console, it doesn't make a new window for it. Is there a way to silence it? If not, it should be fine as it's only 2 lines. |
|
If you can set an environment variable the "WINEDEBUG=-all" should work. |
|
Thanks, also this is really just a peeve of mine (not really an inconvenience) but is there a way to remove the "version: 2300"? Edit: I got it by adding |
|
Although depending on when I stop it, this sometimes happens. Again, this isn't really an issue that's terribly major. |
|
Is there a procedure to reproduce that? A trace would be helpful too. |
|
Ah, alright, I'll just make a note about this then. The plugin seems very haphazardly made anyway, considering the other issues. Thanks for all your help! |
Describe the bug
When trying to run Netscape 4.08, I get this long error
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: