Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country


Posts posted by assenort

  1. Hi guys,

    I am in an urgent need to find this hotfix:


    however my search on the Internets was futile.

    Please help me out. Thanks much in advance.

    Best :-)

    PS. Never mind this request, I managed to finally find the damn thing; in case it is needed by someone else, here is the link:


  2. Hi guys,

    Recently got meself a second-hand Nokia 7 Plus, which is still a pretty decent gizmo despite being close to 6 years old model. The problem is that I cannot find USB drivers to work under Win10 x32/x64 editions; as well as WinXP x32/x64 editions.

    Please help me out, really need those drivers in order to connect the phone to my laptop and desktop.

    Thanks a big bunch in advance :-)


  3. Hi guys,

    I am annoyed beyond my mind by the idiotic "Quick Scan Due" yellow mark notification that appears over the Windows Security icon in the system tray. Basically Windows Security forces you to run a quick scan, which I do NOT want to be doing every few days apart. No useful help about this issue was found on the Internets, hence my posting here.

    My system: Windows 10 Education 32-bit; Version 22H2; OS Build 19045.3324

    I deleted the entry "Windows Defender Scheduled Scan" in Task Scheduler/Windows/Windows Defender, however this did not solve the issue. Yellow mark still appears.

    Please help me out. Will be greatly appreciated.

    Thanks in advance :-)



  4. Hi again and thanks for the new reply.

    With the XUSBSUPP installed, it did not matter if the USB flash drive was plugged in or not - the shutdown manifested itself every time. Normally, on this particular machine I avoid leaving anything plugged in, be it flash drive or mounted virtual disk in Alcohol 120.

    I have tried different versions of the USB driver stack files - it did not make any difference.

    Perhaps the suggestion that a hardware incompatibility exists is closest to the mark. The machine has Gigabyte mobo with VIA KT133 chipset, which was problematic to begin with (they later came up with VIA KT133A revision to rectify hardware issues).

    The driver pack from PassingBy seems to work better, except for the EjectUSB.exe utility - which breaks the overall functionality. What I mean by this is that once the flash drive is ejected with the help with this utility, it cannot be reconnected unless the computer is restarted. In this regard, could you suggest different version of the utility that I can try?

    Thanks again for your help.


  5. Hi LoneCrusader:

    Thank you for responding to my post and giving a meaningful advice.

    Back in 2016 when I was setting up my Win95 machine, I tried the XUSBSUPP pack. Immediately after its installation, the computer began constantly refusing to shut down, instead displaying and getting stuck at "Please wait while your computer shuts down" message (red letters on blue screen, hope you recall what I am referring to, if not see pic below). This annoyed me to no extent, and I had to uninstall the XUSBSUPP pack even though it had excellent functionality. After the uninstall, the shutdown problem disappeared*.

    After that I installed the half-baked pack created by PassingBy, which did not cause problems with shutting down the machine, and seem to be working fine. Only recently I discovered that the pack has serious deficiency with both functionality and un-installation, hence my first post in this topic.

    *It is not just only the XUSBSUPP pack that causes shutdown problem on my machine, occasionally it was triggered by some other things that I was never able to acknowledge with 100% certainty. For example, from time to time when I try to shut down while leaving a mounted image (using Alcohol 120%), the problem manifest itself again. Another example is when I transfer files to the Win95 machine via the home network, most often from a Win10 machine. These cases are random, though, while the XUSBSUPP pack triggers the problem every time I turn off the computer.

    Truth be told, the shutdown problem (I refer to it as a bug, maybe incorrectly) in Win95 is one of the most difficult and annoying to troubleshoot, it continued appearing even in Win98 and Win98SE, when I believe finally a patch to rectify it was prepared and distributed.




  6. Hi guys,

    I was "lucky" enough to install this pack on my Win95 machine in order to be able to use an USB flash drive. At that time (late 2016) I did not do much testing to see if the pack worked without serious problems. Nowadays I need to use the said flash drive extensively on this particular machine. This is how I found out that the USB mass storage pack has serious deficiencies. Namely, once a flash drive is ejected, it cannot be reconnected with the machine, as it is not recognized unless the computer is restarted.

    Furthermore, after trying to uninstall the driver pack, the machine becomes unstable and either cannot boot the OS altogether ("while initializing device ntkern windows protection error. you need to restart your computer"), or it crashes (BSOD).

    The creator of this ill-fated pack did not bother to provide an uninstall utility; and gives some vague instructions a few posts above in the topic about how to uninstall the whole thing.

    Normally, I would reinstall the OS and start anew, the problem is that I have spent literally months to fully set up this machine with tons of software. Thus I would very much like to rectify the problem without reinstalling everything from scratch.

    I hope someone can help me out with the following, which I believe is the culprit for the instability of the machine: the USB pack install its own patched nodriver.inf file in



    so my question is - should I leave this file as is, or try to replace it with a previous version? This files originally comes from USBSUPP.EXE/WDMUSB.EXE - the official Microsoft USB update for Windows 95 versions 2.1 and 2.5. Seems that the creator of the USB pack modified it to go along with the drivers used in the pack.

    Any thoughts on this matter will be greatly appreciated.

    Thanks in advance.

  7. Hi luweitest,

    Thank you for trying to help.

    I however have to disagree with your statement. I cannot connect via TeamViewer between either of my three computers on the home LAN, even though "Incoming LAN connections" is set to "accept" as per your suggestion. My Windows 10 machine runs TV 15.11.6 (which is latest), my two Windows XP Home SP3 machines run TV 14.2.56676 (which is also latest for WinXP). Every time I try to establish a connection such as:

    - From Win 10 machine to Win XP machine

    - From Win XP machine to Win XP machine

    I get the following sweet message one (see below).

    When trying to connect Win XP machine to Win 10 machine, I get the similarly sweet message two (again see below).

    So TeamViewer is out the door for me. But TightVNC does perfect job in this regard - the only drawback is not so visible display, but this is not a big headache.

    Best :-)

    PS. Please note that Microsoft Remote Desktop does NOT work with Windows XP Home; works only with the Pro version.




  8. Hi guys,

    For about 5 years now, I have been using a headless box running updated-to-the-last Windows XP Home SP3 to store and keep my software, games, video and music files. TeamViewer was my tool to connect to this machine from my main computer for the purpose of manually updating the antivirus definitions (Symantec Endpoint Protection 12.1), browse the stored files, and finally shut down the machine when finished. It was a simple, workable solution that served me perfectly. The last version of TV on this machine was 14.2.56673.

    Unfortunately, TeamViewer in all their wisdom decided to ditch Windows XP altogether. Now I cannot connect to the storage comp either from my main computer (Windows 10 x64, TV 15.10.5), or from the third computer on my small home LAN - another XP Home SP3 with TV 14.2.56673. Forgot to mention that even the 5-minute limited session is no longer available.

    I spent some time on the Internets looking for alternatives to TV, but none is much to my liking. Also cannot use the Windows Remote Connection from my Win 10 machine because it does not work with WinXP Home versions (unless you convert from Home to Pro using hacks, which is something I do not want to do).

    Does anyone know of some tool that can remote connect Win 10 and Win XP machines (or Win XP Home to Win XP Home machine) similar to TeamViewer, but operating within the boundaries of the home LAN; meaning it does not have to go through some server somewhere on the Internet that requires account, ID, authentication and so forth? Please share thoughts and suggestions on this topic, will be greatly appreciated.

    Thanks in advance.

    Best to all :-)

  9. Hi guys,

    I have two retro machines running vanilla Windows 98SE US-English version. Video card in both is nVidia GeForce Ti 4200, AGP 2X/4X, 64MB RAM. DirectX is 8.1. Use these machines mostly for playing older video games, or using legacy productivity software. For the games part, I often have to rotate between different driver versions, going as far back as 30.82 and as recent as 81.98, which is the latest that officially support GeForce Ti 4200.

    While most of the driver versions install and uninstall without a hitch, 81.98 gives me headache every time I have to uninstall it. It throws the usual "Nvudisp has caused an error in Nvudisp.exe and will now close" and cannot uninstall. I have to go into a Safe Mode, revert to VGA driver, and use Driver Cleaner to get the job done. It is a hassle.

    If someone knows how to resolve this issue, please give a hint. Forgot to mention that I have tried both the English and the International versions of 81.98, same thing - uninstall is busted.

    Thanks in advance for any help.

    Best :-)

  10. Hi guys,

    Yesterday I tried to update my 3 Win XP installations:

    - Win XP Home SP3 without any MS Office suite

    - Win XP Home SP3 with MS Office 2010 suite

    - Win XP Pro x64 SP2 with MS Office 2010 suite

    and it failed on all occasions. Frankly, I expected eventual updates only on the installations that have Office 2010. However, all I got was some error messages from the Windows/Microsoft Update page.

    I guess M$ finally pulled the plug on the Update services for Win XP iterations? Probably because that will save them a lot of money for hosting and traffic expenses?



  11. For me the today's scan of Microsoft Update on a WinXP Home SP3 machine took a good two-hour period. When completed, three updates showed up, total of 41 MB. Installed without a hitch. Again M$ pushed a broken MSO.DLL (14.0.7252.5000), had to be replaced with the last good one (14.0.7214.5000) in order for the Office apps to work.

    Are M$ people really so dumb and stupid they still have no clue that their so-called updates for Office 2010 create problems for users?

  • Create New...