erpdude8

yes Like I said before, you will need third party tools in order to do this. cant do it with Win98 alone. that kind of security is provided in third party tools for Win9xME and built-in NT-based editions of Windows using NTFS. Search for these tools at Google/Yahoo.

If you completely lock your C: drive then you can NOT use Windows anymore if Windows is installed on your C: drive. Do you mean preventing files from being changed or deleted on your C drive? Or even encrypt or hide files with sensitive stuff on there? File/folder encryption is possible but only for NTFS formatted volumes under Win2000/XP. if you want file/folder encryption under Win9xME and/or FAT32 volumes you'll have to use 3rd party utils for that.

I've just tested Safe mode on my bro's XP-based laptop and I CAN use the wireless USB mouse while running WinXP in Safe mode. If it worked in XP, than it should work in Safe Mode in Win98 AS LONG as usb emulation or usb legacy support (or usb mouse support) is turned on from BIOS setup. USB printers cant be used in Safe Mode because Windows disables them. You can only use usb printers in normal mode for Windows.

Already included. answer to ALL these questions is NO! well too many questions and requests could further delay the release of the next beta of the ME service pack.

USB mice can be used in DOS if USB Emulation or USB Legacy Support is enabled from BIOS setup. You'll have to press a key to enter BIOS setup when you turn on your computer and look for the USB option there. USB printers? FORGET IT!

How hard would it be to make one? They made one of the most common mistakes in programming, using signed integers when unsigned would be more appropriate. Maybe a suitable patch could be created?BUT WHO is willing to make one, LLXX? so far, nobody seems to undertake that kind of task. fixing this kind of problem with shell32.dll for Win98 could break something else in the shell32.dll file & may make things even worse. forget it man.

Windows Update for Windows 95 is still operational.... Petr yup but Win95 users will be using the V3 Windows Update site. Win98/ME users will be directed to the V4 Windows Update site. Is Windows Update still functioning for Windows NT4, Petr?

sorry about the slow download speed at Mytempdir. Good thing I still use third party download accelerator tools to download the file from Mytempdir. took less than an hour (between 45 to 50 minutes) to actually get the file from Mytempdir because the download speeds go up and down while downloading it, even with a DSL connection. no, I wont be making a separate page for the 98fe SP2 on my site and I am only be maintaining BETAS of this pack. RCs and finals of the 98fe SP2 will NOT be made by me. also MDGx change the name from FESP201B.EXE to FESP201B1.EXE so that there's less confusion. plus the FESP201-B2.EXE package that I am currently working on will be up in a few weeks.

Mcafee Virusscan Build: 10.0.27 Engine Version: 4450 Dat Version: 4796 Mcafee Personal Firewall Plus Build: 6.1.6144 Mcafee Privacy Service Version: 7.1.1.46 Mcafee SpamKiller Version: 6.1.07 These are all the latest updates. Now i have all my windows updates installed and don't have any problem with mcafee until i install gapes service pack and Tihiy RP pack. When i uninstall both of the above everything works normal. Try installing Gape's sesp21a pack first. DO NOT install Tihiy's RPLite pack. see if Mcafee software will work ok with sesp21a by itself first. I think RP will mess up Mcafee under Win98 because it installs some ME files. avoid using the RPLite and the 98SE2ME packs if they cause Mcafee software to malfunction.

However, in the Win2000/XP/2003/Vista versions of Notepad you can choose whether to save TXT files in Notepad either in ANSI Encoding or Uniccode Encoding from the Save As dialog box. From the Save As box, default encoding is set to ANSI not UNICODE. if you do the steps on that site to reproduce the problem but save the file in UNICODE format instead of ANSI format, the problem WILL occur. If you save the file in ANSI format, the problem will not happen.

or you can also use the XCOPY command. The DOS Copy command may not properly copy files that have long file names unless you use the Copy command from a command window inside Windows 98se. there is NO patch for the shell32.dll file for Win95/98/NT4 whatsoever that will fix the 2Gb+ copy problem. NOT even the Q313829, Q839645 & Q841356 shell32.dll patches can fix the problem from MS KB article 318293.

that's because the_guy did NOT actually post up beta 4 of the ME SP yet. I'll contact him immediately and have him post it up whenever he is ready.

where exactly did MS say they'll stop WU for Win98se after July 31, 2006? I found no info about it anywhere.

Petr, there's a third party DLL patcher that uses the mspatcha.dll file to "patch" files. I mentioned this to MDGx in the "98FE + 98SE + ME + updates + hotfixes" topic a few months ago. Use the WTL Patcher app from this site (requires registering with the Code Project site to download the program): http://www.codeproject.com/tools/patch.asp

Hi Gurgelmeyer, soneone in another forum recently asked how can we "help" UPDATE.EXE overcome the /integrate problem. Here's the quote- How do we 'help' update.exe? Because executing i386\update\update.exe /Integrate:D:\XP fails and says that you need to use /integrate with the original package.Thanks.

[quote name='ykolomiyets' post='175944' date='Aug 25 2004, 08:20 AM']that thing only takes packaged updates from MS, so there's no way to run update with switches of an unpacked installation. i didn't manage to put the package back togeter with RAR, Power Archiver or any other, so i'm still looking for SFXCAB.EXE and hoping that it would work.[/quote] unfortunately, ykolomiyets, SFXCAB.EXE is not available anywhere and only Microsoft can make SFXCAB packages. Quote from Gurgelmeyer- [quote name='Gurgelmeyer' post='310133' date='Apr 24 2005, 04:11 AM']SFXCAB's are created only by Microsoft, and there are no tools, no documentation or anything else available to help others create SFXCAB's. The /integrate option btw is passed to UPDATE.EXE, which then examines the UPDATE.INF and does the slipstream - SFXCAB.EXE doesn't do much itself really. /integrate will FAIL if UPDATE.INF is not "signed" - that is, if it does not contain a reference to a Microsoft signed .CAT file with a checksum of the .INF itself. You'll need to "help" UPDATE.EXE overcome this and similar other "shortcomings" just to make it do anything at all btw. [/quote]

I wonder if you have tried using the latest version of UPDATE.EXE if that one fixed your "/integrate" problems. scratch that. i take that back. maybe the only to overcome the update.exe problem is to have MS digitally sign your package so that they can create a CAT file for it. that might be next to impossible.

thanx MDGx. I have created the unofficial Notepad updates for Win95, 98 & ME; all three of them have fixed all of the blunders from the Notepad patches wiSHmaKeR made [his notepad patches dont work at all for win95, notepad displaying error message 'There was a failure in launching Wordpad' when trying to open 64kb or bigger files, etc.] Let me know if you need them. and speaking of Notepad, take a look at this problem for the Win2k/XP editions of Notepad in this article: http://bink.nu/Article7429.bink but at least the Win95/98/ME editions of Notepad do not have the problem the Win2000/XP/2003/Vista editions of Notepad has.

Both of those problems have been fixed by my Notepad patches. I will send them to MDGx so that he may post them up on his web site. All of them should update Notepad whether it is running or not. If the older Notepad program is open and you have ran the update, you have to restart the computer in order for Windows to replace the older Notepad app that is running with the newer version. The updated Notepad files included in my Notepad patches should automatically launch Wordpad (not Metapad) when you try to open a file that is 64kb or higher in size in Notepad. These patches I've made are created from IExpress, not the one that wiSHmaKeR used. the patcher wiSHmaKeR used is incompatible with Win95 which was why his Win95 Notepad patches did not work at all. and speaking of Notepad, take a look at this problem for the Win2000/XP editions of Notepad in this article: http://bink.nu/Article7429.bink good news is the Win95/98/ME editions of Notepad do not have that problem.

what kind of Mcafee software are you using and what version of Mcafee is it, PROBLEMCHYLD?

some of the stuff written in MS article 197147 about Command-line switches for IExpress packages is incorrect. For example the /r:s switch, which supposed to make the package restart the computer without asking the user after install, does NOT really restart the computer automatically. Reading the INF + IExpress web guide about the 'Smart Reboot' switches, it's actually 'AS' [or /r:as]. If you want to force and IExpress package like any Win98 hotfix to automatically restart the computer specify the /r:as switch (or even the /r:is switch if the files that are being updated are in use by the Windows OS).

I wouldnt use that kind of TargetWin9xVersion setting for Windows 95. That may not work for Win95 B/C systems with the USB Supplement Update installed which updates Win95 OSR2 to either version 4.03.1212 or 4.03.1214. personally I prefer 'TargetWin9xVersion=4.00.950-4.03.1214' when making patches for Win95 see MS KB article 158238 on the 9x versions of Windows being used: http://support.microsoft.com/kb/158238 thanks MDGx for posting up the INF + IExpress guide.

version 5.3 of the riched20.dll file is also bundled in the Windows Installer 2.0 packages. so I guess MSI 2.0 uses the riched20.dll file. Microsoft Office programs like MS Word & MS Outlook also use the riched20.dll file. If you can't start these programs because of a bad or corrupted riched20.dll file, replace that DLL file with a clean one.

no bigbadsteve! no other MS update messed up the modified Notepad.exe file. wiSHmaKeR's Notepad patches modify Notepad.exe in Win95/98/ME to open files bigger than 64Kb to open in Metapad.exe, not Wordpad. wiSHmaKeR made them that way. plus wiSHmaKeR's Win95 Notepad patches do NOT even work under clean installs of Win95 unless certain Win95 DLL files are replaced by Win98 versions in order for the Win95 Notepad patches to work. EVEN BETTER! I've created unofficial Notepad patches for Win95, 98 & ME that will update the Notepad application and will properly and automatically open files 64kb and bigger in Wordpad and not Metapad. All of them will update Notepad by one build number (ex. my Win95 Notepad patch will update Notepad to v4.00.951, the Win98 Notepad patch will update it to v4.10.1999 and the WinME Notepad patch will update it to v4.90.3001). If anybody wants my unofficial Notepad fixes, let me know. BTW - Metapad can be found here: http://www.liquidninja.com/metapad/

and what will happen when %BrowserWarn% or %AppWarning% is used? What kind of message will %BrowserWarn% or %AppWarning% be displayed if you have defined one? -erpdude