Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

Everything posted by NoNameNeeded

  1. Since there are thousands of different versions out there, I don't know which is which but I found out that this one... http://o.rths.cf/basilisk/basilisk55-win32-git-20190824-978d4a7da-xpmod.7z ...works better than this one... https://o.rths.cf/basilisk/basilisk52-g4.4.win32-git-20190907-6db06749e-xpmod.7z ...even though the latter one is the newer version (or seems to be the newer version, according to the date) In the version from sept 2019 zooming in or out in google maps using the mouse wheel doesn't work (like in a much older version I found) but it does work in the version from August 2019.
  2. I certainly wouldn't install it, at least not on a real computer. Windows 95 is rather finicky when it comes to updates. Updates might render some applications or games useless or might slow down your computer significantly or just cause other seemingly inexplicable problems. Just install the updates you really need and don't go for the most recent files just because they're newer. Even if you don't run into any incompatibility problems newer system files might slow down your computer (as mentioned above). Recently I updated the Common Controls Library with an update called 50comupd.exe (it seems to be a well known update). It is needed to run some newer applications but on a 486 you just don't want to install it because it slows the explorer down like you wouldn't believe. Before the update it was snappy, after the update the explorer slows down to a crawl. Since I knew which file had been updated, I was able to replace the newer file with the older one but of course you wouldn't know that if you installed all the updates at once.
  3. I'm sorry but I really don't know an answer to that. I think a lot can be achieved (just think about KernelEx) but I know way too little about that stuff.
  4. It doesn't work. I've just tried it on Windows 95B. Throws an error about a missing function "IsDebuggerPresent" which I could "fix" but it still won't start.
  5. I've just downloaded this browser and as far as I can tell it seems to be working fine (on Windows 95B from '96). It's a nice idea to have a basic browser for Windows 95 but I think it would even make more sense to use something like KMeleon because as far as I know it uses Windows stuff as a GUI and not the XUL stuff that all these Firefox derivates come with. What this means for the end-user is that it uses less memory and launches faster and that really is quite an important thing on an older computer. Just saying...
  6. I wish I could find a link but there is someone somewhere who allegedly got (a browser based on) Firefox 53 to work on XP. It's not a normal version, it uses some linux-like stuff and you can't just install it like a normal Windows application and therefore I couldn't get it to run. But anyway, has anyone heard anything about that?
  7. I don't use Windows 98 but Windows 95. Of course, I don't use it on my main computer (even though I have a few virtual machines that run Win95), but 1 or 2 years ago, I bought an old laptop, just for fun. And then I thought, why not putting it to use as it was meant to be? So, now I really use it as a computer that I can take anywhere to work on Word document or to view PDF files. And except for the battery life I think I'm not really worse off than other people who also use Word and pdfs, so it doesn't really make that much of a difference (but I don't have to struggle with ribbons in Word, which is a good thing) From time to time a get strange looks and some people have asked me if my laptop is some kind of new retro-looking device and OS. It's not, it's as old as it looks.
  8. Why is it a recommended update? It seems to be the version from ME. Does it do anything better than older versions?
  9. I've changed these settings to new values now. I don't know what they do, all I noticed was that if I set them to high the app won't start because it doesn't have enough RAM, but now it works and doesn't use more RAM then before. I can't say it's perfect because I've encountered a BSOD again but only once even though I opened and closed the app at least 20 times in a row. So I don't know what these settings do but they seem to mitigate the problem.
  10. Oh and one more thing. In CFF Explorer I found something that's called "Native Win9x driver" I just applied this setting to my application and even though the BSOD did show up once, I was still able to get back to a (somewhat screwed) Windows and restart the computer which is already a bit better than having to reset the machine.
  11. Sometimes, when a BSOD occurs and I hit enter several times I get to see an interesting picture. This time, it looks like a giant M..:) To me, it seems like this has something to do with either gdi or the graphics card (or both). I've already updated the driver but what's interesting is that these BSOD occur both on a virtual machine running Win95 and also on a Pentium 1 laptop so even though the graphics card and its driver differ a lot, the BSOD is still the same.
  12. Yes, but even with the redirections you suggested, these random BSODs still occur. So, that can't be the solution. I'm afraid there just is no solution. It's just that this application wasn't made for Win95, that's the bottom line. But it was worth a try. P.S: I also opened the file in CFF explorer and kicked out msimg32.dll After all, Win95 doesn't come with msimg32.dll (which is related to gdi.exe) and the application uses only two functions so I just removed it to see if the BSODs vanish. They didn't. But again, it was worth a try.
  13. Ok, in Dependency Walker the addresses are shown in a different format so I couldn't find anything. But I did find something with another program, it's not exactly the same address but it's at least similar (BFF9A352) The function is in kernel32.dll and it's called IsBadStringPtrW
  14. Update 3: Ok, now I tried it with an original unmodified file. The last problem I mentioned in Update 2 is sorted out now (it was probably due to my additional modifications) Now I need to open and close it for a while and see if the BSOD returns. Update 4: I got an error about low system resources and after that the ominous BSOD returned.
  15. How do you know how I modified it? But you're right that I did not redirect GetLongPathnameA to GetShortPathNameA. I've done that now and then I renamed the function to LocalCompact in a Hex Editor. I couldn't rename TrackMouseEvent to PaintDesktop because there is no such function in Win95, so I left it as it is, I think originally I renamed it to GetKeyboardType or something, I don't really remember. The way I modified it before was that I renamed the function GetLongPathNameA to GetFullPathNameA. Could that cause problems? Update; Just tried the new application, the exact BSOD appeared when I closed it, so that doesn't seem to fix the problem. It think it seems to be related to gdi.exe Update 2: Now I am no longer able to open a pdf file. It only throws an empty error message when i try to open a pdf file from within Foxit Reader or an error message referring to the application's name when I double click on a pdf file. Maybe it's because I've renamed the GetLongFilePathA function to LocalCompact?
  16. So is there a more effective way?
  17. Which number should I be looking at? I can see "ordinal" and "entry point" numbers, none of which come even close to the number of the BSOD.
  18. I'm getting this BSOD quite frequently when I try to either open or close Foxit Reader 2.1 on Windows 95. It's a modified version of Foxit Reader, normally it wouldn't run on Win95. Now, of course it's no big surprise that an application that wasn't even meant to run on an operating system might cause one or the other problem but nevertheless I thought it can't hurt to ask if anyone happens to know what could cause this specific BSOD error. I couldn't find anything really useful, it just seems to be a very general error with no real solution. At times, I also get other errors referring to gdi.exe but I can't say if the bsod is in any way related to the gdi problems.
  19. Is it the same dll you sent yesterday or a new one? I think I clicked on rebuild, but can you add stuff without rebuilding it? I'll try it again. Edit: Ok, it's not the same and it seems to work now. It saves and retrieves the toolbar settings. Amazing! Thx a lot for your help! Ok, next project: Office 2016 on Windows 3.1 Should be easy....;)
  20. Update: Even though it will no longer open, the application writes a new binary setting to the registry, so this seems to work....
  21. Ok, there is at least a search function. That makes it a bit easier. Thx for the hint. Nevertheless, I still don't like that program too much. @ABCDEFG Ok, I was now able to find the settings and redirect them to your dll file. Unfortunately the application will no longer start. It throws an error (or two, depending if there is a DockState_Pro key in the registry or not) complaining about an invalid page in the exe. But I was able to narrow the problem a bit down, so at first I only redirected the Regquery part to your dll and the app still opened, albeit with a messed up toolbar, but as soon as I redirect also the Regset part to your dll, the application will no longer open.
  22. I'm sure it's in there but I just can't seem to find the DockStatePro entry in ollydbg. Is there maybe another program which is not as ridiculously bad as ollydbg? It shows whatever it wants to. Open a file three times and you get to see 3 different results. Open an exe file and you get to see the content of kernel32.dll...?! And there isn't even a search function. Even the most basic, crappy word editor has a search function and lets you search for just about anything...But not in ollydbg I know it's for free so you can't expect much but it's extremely annoying. Maybe I'll find the right strings one day, maybe not.
  23. To my knowledge, at the time when Win98 was around USB soundcards didn't really exist. What makes it even more problematic is that you're looking for a usb soundcard with 64bit drivers.It is even less likely to find one that is new enough to come with 64bit drivers and old enough to come with Win98 drivers. If I'm wrong, I'm sure someone will correct me.
  24. Update: As soon as I change the address of only one setting to the new dll and save the application file, the application will not open, throwing an error about a problem with kernel32.dll
  • Create New...