All Activity

hmm i had a feeling about it looking at IP's before possibly, because of it loading this "geo" ddc it shows in the URL for a split second. :|

I managed strip services and drivers to bare minimum MS services only and some disabled. To do it i used services and drivers disable tool, but some them you hit inaccesibility boot device errors or security error. To bypass them you have check which service is based on which, disable them piece by piece, its really working in only in virtual machines, with snapshops and quick rewind, or you have to do registry backup and keep notes about all changes and return them, when you hit to booting spate. Inaccessible boot device error you mostly are caused by Upperfilters in WIndows registry where is list of *.sys files filename without sys suffix.. so you have to search for it and remove filters before you disable the drivers and these drivers most have classId for DIsk device or most often Volume, some filters are part of WIndows.. Especially a lot of filters have EaseUS tools, a bit less Acronis, Minitool and Paragon - for example their HFS and AFS are based on filters too. My machine is still not booting the same error, so problem is not some driver or 3rd party app service, but something else in the system. I also fixed all errors related to last Event log, i disabled all remated services and disabled their drivers. What is left, there are some Panther logs from day where it stopped botting, i did make upgrade, but some updates using upgrade like procedure / system. In Panther logs, i see that there is some errors about recovery envriroment, i they really make much sense, i have dedicate recovery partition, but there is also C:\Recovery where is multiple sub directories with some Ids and one OEM, what is interesting that *.win files have only like 150 MB, my standard recovery wim on dedicated partition have 400 MB+, so its possible that because on enough space on the system it somehow failed, and it could happen even before this update and this update expected not broken *.wim. Its just theory, question is really if broken recovery could cause boot error 0x000021a, so far my boot always start normally, autorecovery after multiple boot fails is disabled.. which i dont mind, when i start it manually and start automatic repair it fails with message related to recovery too. I did it before and fixed disk structure, partition flags and recovery entry in bcds, but i will try once more fiddle with recovery settings there is some xml beside of BCD, too find out if its related to this error, otherwise its some broken system file - but sfc and dism should fixed them, there are fine. Or its related to registry, i removed all broken registry keys, but its still the same.. i know removing is not fixing, but there wasnt something import broken, just trash after some failed uninstalls and portable programs.

Weirdly enough, it seems it's not necessary to have a valid Windows key to enroll into the ESU program. So one way or another you should be fine as long as you get the ESU activation screen to show up.

Hi, I got a problem... before right switch on the taskbar and you had a menu where could create a new quick lunch bar... now it doesn't work... is it possible restore it?

@awkduck Well, in theory it is possible if we had a team of expert software engineers and system programmers who know 9x in depth, who would dedicate their time to this problem. It is not a simple problem and would require modifying some vxds and dlls and adding new functionality. At first glance it may not look like that, and it may seem simple, but just look at kernel32.dll it is only 460kB, but its assembly code when disassembled is about 5.5MB. Also VMM.VXD is about 450kB but when disassembled it is about 2.5MB of assembly code. Similar applies to VWIN32.VXD and others. There would also be a problem with the shell, User32.dll and GDI32.dll and others which are not fully 32-bit but most of their most important functionality is actually 16-bit because 9x systems are hybrid. And many other important files that would have to be modified. And not just a small modification but a complete reengineering is required. That is a MASSIVE task and therefore it is not realistic to expect such a thing to happen in practice. But we can still use multiprocessors/multicores for, some calculations and such things...

This was only relevant for certain locations. I'm from Switzerland, here we are being taught only British English. And The Queen used to love our mountains. Not relevant, Slovakia contributes for 0.00000000001 of EU population, joined very recently, probably had some form of the obsolete American dialect in the schools, taught under the soviet boot. Now you all learn only British English.

How do you know what I not fully understand? D.Draker was clairvoyant, you, no. No matter the intent, on such old version, many sites will not open, simple.

You do not fully understand the intent behind such things as ESR (and LTSB/LTSC). That said, many home-based consumers that use corporate-based products for non-corporate use may very likely also not fully understand the underlying intent. Personally, to me, in my opinion, yadda yadda yadda, ANY product that is EXTENDED is GREAT NEWS for the CONSUMER.

Update: After using the methods posted on the web (on various sites) to force the Consumer ESU activation prompt in System Update I successfully included this PC in my family of 5 computers still running Windows 10. This computer is my main PC (dual-boot Win10/Win11) and I really need it to continue getting Win10 security updates. I might just ignore the licensing mystery as signing this PC up for the ESU program was my main objective. FYI I'm a photographer who still uses old Adobe CS6 apps which Adobe (intentionally?) disables when installing Creative Suite 2025. My workaround is to use Win11 with the recent CC apps and use Win10 for CS6 apps which I still need access to for editing older files and to use features that no longer exist in CC2025. R

Thank you for your help :-) I entered the serial number using "slmgr /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX" (XXXXX = the good Win10-Pro key) and I got: Error: 0xC004F050 The Software Licensing Service reported that the product key is invalid. But I know that it IS valid and came from previous 2 retired systems. The first was a upgrade from Windows 7 Pro in 2016 and the second was 6 months ago. Meanwhile the system claims to be activated without any error messages after entering it in "Change product key". Strange .... R

Are you sure it is not something else? Retrozilla (default settings) is still working for me with Google on Windows 95 OSR2. BTW tab with Google: only title is showed.

https://www.vogons.org/viewtopic.php?p=974480#p974480

This won't make the several years old browser engine new. So what of it?

Changing BIOS settings is not the same as "reflashing" the BIOS, which shouldn't be needed after changing the battery. Or does it now? Do most drives require AHCI? I've only found this with one drive that was extremely slow in compatibility mode (5 MB/s) because it didn't fully implement Ultra DMA.

I am using DLP 2025-08-20. SABR has gone away again for now and downloads work. It is not great that I need to wait some 10-20 seconds to see if download would start, but what can you do. I haven't seen very poor video quality again recently.

See here All you need is the files in the exe folder. If using Win95 you may try the newer test ini (see previous discussion above in this regard).

Link is dead, does anyone have a copy of the patch? Thanks

I did just discover that the paypal slide mouse screen in my older version of Serpent is DEPENDENT UPON the ISP that I use. I canceled my previous ISP but it remains active until the end of my billing cycle (I only have two more days) - I get no slide mouse screen in Serpent when connected via my previous ISP (cable). I *DO* get the slide mouse in Serpent (unsolvable - checkbox turns green but page does NOT advance) in Serpent when connected via my new ISP (fiber optic).

Use slmgr with /ipk and put your product key in that way. If it gives you an error, post that message.

Reserved

@reboot12 Well, Win95 does lack API and features compared to 98(SE) or ME so it's understandable. Besides, in case of [very] new motherboards or add-on cards that need further patches it is possible that some code pieces may interfere with each-other. Most everything in this area of matching old OS versions with new hardware has always been more or less experimental. Personally I've never been happy with Win95 even back in its time, upgrading from Win3.1. Only 98SE - with further unofficial upgrades as time went by - could satisfy me to a substantial degree. But it's all about the software running on top of the OS. I'm not familiar with your MIDI application, or MIDI generally - the most I came close to it was a virtual keyboard emulator written [also] in AHK by someone else, which I modded a little (not in the DropBox pack, and it's Unicode only). Hope you find some good working configuration eventually.

@Drugwash Thanks for the quick answer but I have already given up using the 6200 card after I edited the file manually according to what I wrote LoneCrusader but it did nothing and the system still does not start https://msfn.org/board/topic/174096-nvidia-video-driver-shutdown-fix/page/6/#findComment-1104546 Probably in my case there is another problem with the 6200 card. After a few days of trial and errors I have enough Unfortunately, I failed to use the PCIe ATI X300 or Nvidia 6200 in Win95 - I tried on 4 different computers. The best configuration in which I managed to start Win95 and the system works stable - I use for MIDI production/editing in MAGIX music studio 3.0 deLuxe: Asus B85M-E Haswell 4 Gen CPU - need FIX95CPU by LoneCrusader 2 GB RAM + PATCHMEM.EXE by Loew (alternative 8 GB RAM but need also HIMEMX.EXE /max=2G) Intel iGPU + VBEMP 9x driver Sound Blaster Live! PCI Realtek 1Gb 8168 on NDIS2 DOS driver

Unfortunately only one version of Win95 has been tested back then. It's been ten years since, I moved to Linux, Mr Loew regretfully passed - may he rest in peace - and apparently there has not been much interest in this patch since. I attached an experimental version of the ini file, but please be aware it has not been tested at all; code was just added blindly from other sections, and it may or may not work at all, or could even lead to boot errors. Please read the documentation carefully to learn how to recover from such errors by unpatching or restoring the backup file. File was compressed under Linux, hopefully it can be unpacked in Win95 - otherwise please try to do it in a later OS. Also please make sure you're using the latest available version (1.5.2.2) of the patcher as earlier versions may use a different, uncompatible ini format. It can be found at first link in my signature if other links don't work. Please note it is a large archive file (~125MB)., look in the ShutdownPatch subfolder. Hopefully this helps. Unfortunately I have lost touch with Windows generally for a few years already so it's doubtful I could be of more help in this matter. ShutdownPatcher.ini_1.5.2.3_test.zip

F..k - Why does this topic have in the title 9x if nothing works in Windows 95 !!! The topic should have the name: WPA2 for Windows 98/Me! or better Wifi for Windows 98/Me!

Do this patch works on Win95? The program detects the system version but does not patch because in the .ini file there are no entries for Win95 - entries (8x) are only for Win98SE: https://www.vogons.org/viewtopic.php?p=1377051#p1377051