MDGx

To my knowledge FASTVID does the same as MTRRLFBE, with 1 exception: MTRRLFBE does not set Write Posting, but FASTVID does. Please keep in mind these tools are only for Intel 4xx/8xx chipsets. If using AMD chipsets, must use other similar tools. Some of the Intel 4xx/8xx series chipsets already have some of these functions built-in. To use FASTVID you must (re)boot to native/true/real/pure MS-DOS mode: 1. By holding down Shift + F5 at the same time during BIOS boot POST (Power On Self Test) sequence. 2. OR by scrolling down using the down arrow to the "Command prompt only" option and then pressing Enter from the Windows 98 Startup Menu: http://www.mdgx.com/msdos.htm#MEN 3. OR from a Windows 98 SE Emergency/Bootup/Startup floppy/CD/DVD/USB/external disc/stick/tape. 4. OR by exiting Windows to native MS-DOS by using %windir%\"Exit To DOS.PIF" shortcut. Extract all FASTVID files into the same folder using an unZIPping tool: http://www.mdgx.com/toy.htm#ZIP Then run FASTVID without any command line parameters: FASTVID and follow the steps on the screen to activate/leave alone/deactivate any of its 3 functions. The last FASTVID command you see [which uses parameters], should be the 1 you can add to autoexec.bat if you want this to happen every time you boot. Example: C:\MAX\FASTVID.EXE 111 -128 C0000000 If you use MTRRLFBE: http://www.volny.cz/rayer/programm/mtrrlfbe.exe run it only from native MS-DOS without any parameters to see all its available command line parameters: Example of using MTRRLFBE in autoexec.bat:C:\MAX\MTRRLFBE.EXE LFB WC C:\MAX\MTRRLFBE.EXE VGA WC Please note that you must use an Upper Memory Manager [like UMBPCI.SYS] in order to take advantage of FASTVID or MTRRLFBE functions, because EMM386.EXE and all other Expanded/Extended Memory Managers [like QEMM386.SYS, RM386.EXE, 386MAX.SYS etc] will not allow FASTVID/MTRRLFBE video memory areas to be used, even if Expanded [EMS] memory is disabled on the EMM386/RM386/QEMM386/386MAX command line in config.sys. You can see which video memory area your video adapter/controller/card is using by running FASTVID without parameters. Example [my vid card uses C0000000]: FASTVID.EXE 111 128 C0000000 VSPEED.EXE [part of http://www.mdgx.com/files/FASTV110.ZIP] also shows video areas used by your vid adapter. You can also learn which memory areas your vid adapter uses from within Windows 9x: Control Panel -> System -> Device Manager -> Display adapters -> your video adapter name [example: NVIDIA GeForce Ti 4600] -> double-click on your adapter name -> Resources tab -> look [write down if you wish] all "Memory Range" ranges. To use UMBPCI.SYS, just add a line for it in your config.sys, in this exact order [example]: DEVICE=C:\MAX\UMBPCI.SYS DEVICE=C:\MAX\HIRAM.EXE DEVICEHIGH=C:\WINDOWS\HIMEM.SYS /NUMHANDLES=128 /TESTMEM:OFF /Q I use C:\MAX for these files, but you may wish to use a different folder/drive/partition, just make sure DOS4GW.EXE is in the same directory as FASTVID.EXE. Notice that you must use also HIRAM.EXE [found at http://www.mdgx.com/umb.htm#HIR in order to force UMBPCI to leave no foot print in conventional memory] + HIMEM.SYS [which is already installed in %windir% by your Win9x OS]. HIMEM must be used because UMBPCI is an extension to HIMEM. Please see this section from the UMBPCI.SYS documentation: http://www.mdgx.com/umb.htm#REQ to learn if your mobo chipset is supported by UMBPCI. If UMBPCI doesn't work on your computer [unsupported chipset], then use only HIMEM.SYS in order to be able to use FASTVID/MTRRLFBE [upper memory is not needed by fastvid/mtrrlfbe]. To learn about memory management, please see these text files installed by W95-11D.EXE: http://www.mdgx.com/95.htm MEMORY.TXT REGIONS.TXT EMM386.TXT MSD9X.TXT DOS9XMEM.TXT and see also: http://www.mdgx.com/mem7.htm WIN9XMEM.TXT and see also: http://www.mdgx.com/mem7.htm This file: MYTIPS95.TXT also contains a lot of MS-DOS + memory management topics you may wish to read. Those topics are usually refered to in the other text files listed above, and they are also available online: http://www.mdgx.com/newtip.htm HTH

Which different language?The only language file that was fixed previousy [the unofficial copy files/folders 2-4 GB bug = SHELL98.EXE] is English (United States) = en-us. The anonymous author patched that shell32.dll 4.72.3812.610 [from SHELL98.EXE] to new version 4.72.3812.620 . So now SHELL98.EXE contains the new version: * Unofficial Windows 98/98 SP1/98 SE Explorer Lockups SHELL32.DLL 4.72.3812.620 Fix: http://www.msfn.org/board/?showtopic=84451 Direct download [475 KB, English]: http://www.mdgx.com/files/SHELL98.EXE HTH

soporific: Please download NUSB23E.EXE from my site: http://www.mdgx.com/spx/NUSB23E.EXE That's the one I've used to install unattended without any prompts. You may have an older/buggy/test version. [?] HTH

I'm sure there are, but M$ discontinued support for 9x/ME OSes, so to port other OSes fixes to 9x shell32.dll it's probably not as easy as it seems.Besides, some of the NTx [NT4/2000/XP/2003] OSes shell32.dll fixes are strictly NTx specific, do not apply to 9x [95/98/ME] OSes. The anonymous author agreed to fix this bug only because I mentioned it to him [and obviously he is a very nice person], and he has also read about our unsuccessful tests/workarounds/etc, here at MSFN. Please do not forget that this is only 1 person [not an entire team of software engineers] who does this in his own spare time [which from what I understand is very limited]. But I'll mention this to him nonetheless. HTH _____________________________________________ Unless it has just been updated, I had missed that so far.So, any more information please ? You say the size of the 32bits segments could be enlarged simply by modifying hidden system settings. Which ones and where please ? I'll mention your questions to the anonymous author.The GDI*.* fixes have not been updated recently. Last update was 8-9-2006, when Win98SE GDI*.* files were updated to version 4.10.2227 . To view this update, please go to: http://www.msfn.org/board/?showtopic=46581 and scroll down to: NEW 8-9-2006 HTH _____________________________________________ 98SE2ME does this by modifying the registry, not the file.Quote from READ1ST.TXT: http://www.mdgx.com/9s2m/READ1ST.TXT HTH _____________________________________________ As I've said before, it is not recommended to patch older files, which do not contain newer fixes, because system file patches are [and should be] cumulative. Patching older files with just 1 fix and ignoring all others defeats the purpose of having a fully-patched OS.But if you want the older file patched only for experimenting on your computer(s), that's an entirely different matter. I'll mention your request to the anonymous author. HTH _____________________________________________ Did you or some1 else test this patch on Win95 with Active Desktop?Does it work? If it does, I'll modify the installer to make it work on Win95. HTH

Another 7-zip SFX GUI tool [EasySFX], very easy to use [copyright free software]: http://www.excessive-software.eu.tt/ HTH

I'd love to test this RASPPPOE environment and replace whatever files need to be replaced with older Win98SE counterparts, but unfortunately I don't have such a connection, nor do I have access to another computer that does. Therefore it's up to you and/or other RASPPPOE users to test this. There is an older post in this 98SE2ME forum: http://www.msfn.org/board/index.php?s=&amp...st&p=327274 in which I explain which files one may want to replace in order to test RASPPPOE. If you're willing to perform such tests, please post your results here. Thanks. Hope this helps.

Updated installer with new files [11-7-2006]: * Unofficial Windows 98/98 SP1/98 SE Display Errors FORMAT.COM + FDISK.EXE Fix: http://www.msfn.org/board/?showtopic=85573 Direct download [110 KB, English]: http://www.mdgx.com/files/FDSKFRMT.EXE This NEWer FDISK.EXE Fix replaces OLDer Q263044 FDISK.EXE Fix: http://support.microsoft.com/?id=263044

UPDATED 11-7-2006 * Unofficial Windows 98/98 SP1/98 SE Explorer Lockups SHELL32.DLL 4.72.3812.620 Fix: http://www.msfn.org/board/?showtopic=84451 Direct download [475 KB, English]: http://www.mdgx.com/files/SHELL98.EXE BUG: This SHELL32.DLL fix breaks the ability of removing annoying arrows from Desktop shortcut icons! FIX: See "PATCHED SHELL32.DLL BUG + FIX" in TIPS98.TXT (included) for complete details: http://www.mdgx.com/98-5.htm#PSBF This SHELL32.DLL Fix corrects Windows Explorer and similar tools lockups while trying to copy/create/move/delete/rename large files/folders, even if Internet Explorer 5.xx/6.xx already installed. Please see 1st post for details: http://www.msfn.org/board/?showtopic=84451

Posted here: * Unofficial Windows 98 SE Display Errors FORMAT.COM + FDISK.EXE Fix: http://www.msfn.org/board/?showtopic=85573 Direct download [110 KB, English]: http://www.mdgx.com/files/FDSKFRMT.EXE This NEWer FDISK.EXE Fix replaces OLDer Q263044 FDISK.EXE Fix: http://support.microsoft.com/?id=263044 Keep up the good work, Petr.

http://www.mdgx.com/98-1.htm#98ESS HTH

Thanks. I have changed the text to read: Unofficial Jet 4.0 SP8 Patch for Windows 9x/NT4/ME/2000 [1.9 MB]: http://www.mdgx.com/files/Q918144.EXE

Re: smartdrv Glad you found a solution that works for you. Smartdrv cannot load from within Windows nor from a DOS box/session/prompt within Windows. The only way to load smartdrv is either from config.sys, autoexec.bat or native MS-DOS prompt, before Windows loads. But if you have one of these lines in your C:\MSDOS.SYS [and/or C:\WINBOOT.INI] under the [Options] section: DoubleBuffer=1 or DoubleBuffer=2 you need to change it to read: DoubleBuffer=0 Then reboot. This line may try to load/search for smartdrv in %windir% [default location]. If DoubleBuffer=0 IO.SYS stops looking for smartdrv. Or [like you already did], just move smartdrv.exe away from %windir% , any other directory would do. Or if do not use [or plan to use] smartdrv at all, just delete all instances [including the one you renamed to *.old] from all your hard drives/partitions. I'm not experienced with VIA drivers/chipset, never had a VIA mobo. BTW: What do you mean by "DOS audio" with your Audigy 2 ZS? Can you use the Audigy 2 card in native/true/pure/real DOS [outside Windows], or just in DOS boxes/sessions [within Windows]? HTH

USBMTE now here: * Unofficial Windows 98 SE IEEE 1394 (FireWire) + USB HOTPLUG.DLL 4.10.2224, USER32.DLL 4.10.2223, SYSTRAY.EXE 4.10.2224, USER.EXE 4.10.2226, HARDWARE.HLP, 1394.INF, NODRIVER.INF, NTMAP.INF, USB.INF, USBNTMAP.INF, USBSTOR.INF, NTMAPHLP.PDR 4.10.2223, USBMPHLP.PDR 4.90.3000, 1394BUS.SYS 4.10.2226, NTMAP.SYS 4.10.2227, OHCI1394.SYS 4.10.2226, SBP2PORT.SYS 4.10.2226, USBAUTH.SYS 4.90.3000, USBNTMAP.SYS 4.90.3000, USBSTOR.SYS 4.90.3000, USBU2A.SYS 1.42, DISKTSD.VXD 4.10.2223 + IOS.VXD 4.10.2223 Fix [586 KB, English]: http://www.mdgx.com/files/USBMTE.EXE BTW: This looks like an older NUSB [Native USB] edition which installs older versions of files. [?] IMHO: NUSB 2.3 [current edition] installs all these files, but newer versions [649 KB]: http://www.mdgx.com/spx/NUSB23E.EXE If this is true, USBMTE.EXE should be removed, and NUSB should be used instead. Just let me know. HTH

The "Send To/Copy To/Move To" shell right-click functions are installed [actually repaired] whenever you first install 98SE2ME.EXE on your hard disk, even if you don't install any options [1 to 8].More details in READ1ST.TXT [the "98SE2ME.PIF COMPLETE GUIDE" section]: READ1ST.TXT On a "virgin"/from-scratch Win98SE system, these are the only registry values for Send To/Copy To/Move To [if you wish to restore them, but they usually prove to be buggy]: Save the above as C2M2S2.REG [example] and then double-click on it to merge it into your registry.But first you should uninstall Copy To/Move To/SEnd To from Control Panel -> Add/Remove Programs = as detailed above, and only after that merge C2M2S2.REG into your registry. The NOTEPAD.EXE file associations in the registry are repaired/installed whenever you install option 1 [which also installs PFE32 (better NOTEPAD)] or when you install PFE32 by itself [option 5]. Options 1 + 5 install these registry values, by running: RUNDLL32.EXE %windir%\SYSTEM\ADVPACK.DLL,LaunchINFSection C:\9!M\O6RES.INF,PFE The PFE section from O6RES.INF points to the AddReg=FX registry section, which is responsible for installing all PFE text files associations in your registry: Failure to uninstall option 3 might be due to different versions/builds of system files you had in %windir%\system before you first installed option 3 [if installed it more than once]. O3.BAT has version check commands in place [using getver.exe] to make sure only original Win98SE system files are backed up, and not other newer versions [i.e. from previous option 3 installs], which would defeat the purpose of backing up original files. For example, if you already installed option 3 in the past, your system files are now WinME builds. Option 3 backup function will not backup/restore WinME files, only Win98SE files. BTW: I have double checked [again], and option 3 installs + uninstalls properly on my PC, but I have used original Win98SE CD-ROM files in %windir%\system before I installed option 3. These are the files installed by option 3 (quoted from READ1ST.TXT): These replace Win98SE files with older builds, normally found in %windir%\system .Original Win98SE files should be [x means any number, which means you may have different versions installed from different sources, but which will be all backed up/restored by option 3]: %windir% [usually C:\WINDOWS]: EXPLORER.EXE 4.72.3xxx.xxx %windir%\SYSTEM [usually C:\WINDOWS\SYSTEM]: COMDLG32.DLL 4.72.3510.2300 DIMM.DLL = not found in Win98SE [therefore not backed up] DOCPROP.DLL 5.00.1897.1 DOCPROP2.DLL = not found in Win98SE [therefore not backed up] FONTEXT.DLL 4.10.1704 MYDOCS.DLL 4.72.3xxx.xxxx NETPLWIZ.DLL = not found in Win98SE [therefore not backed up] PLUSTAB.DLL 5.00.1528.1 SHELL32.DLL 4.72.3xxx.xxx SHSCRAP.DLL 4.00.950 IESHWIZ.EXE 4.72.3xxx.x WEBVW.DLL 5.00.0312.0 HTH

Jscript.dll 5.6.0.8833 is not meant for 9x OSes, works [and regsvr32-s] properly only with 2000/XP/2003. The last official jscript.dll that works properly with 98/98SE/ME is 5.6.0.8831 : http://www.microsoft.com/technet/security/...n/ms06-023.mspx JScript 5.6 Patch for Windows 98/98 SE/ME [329 KB]: http://download.windowsupdate.com/msdownlo...d10b72452f7.Exe HTH

Eck: Try these: 1. Delete completely SMARTDRV.EXE from all your hard drives/partitions. You can always get it back from the Win98SE or WinME CD-ROMs. Reboot. Or, if you prefer to use smartdrv, just add this line to your config.sys in C:\ root: INSTALLHIGH=C:\WINDOWS\SMARTDRV.EXE 12288 16 A- B- C+ D+ /N /Q Adapt this line to your HDs: here it caches drives C + D [seen as HDs]. If smartdr.exe is located somewhere else on your computer, modify the path above. If not using EMM386.EXE, UMBPCI.SYS, RM386.EXE, QEMM386.SYS etc to provide upper memory, no need for INSTALLHIGH= above, which you should replace with INSTALL= . Reboot. 2. Make sure your %windir%\IOS.INI lists smartdrv.exe among its drivers. If it does not, extract a fresh copy from the Win98SE CD-ROM [CABs]: EXTRACT/Y D:\WIN98\WIN98_50.CAB /L %windir% IOS.INI Change path to CAB if different. %windir% = usually C:\WINDOWS . Reboot. 3. In Control Panel -> System -> Computer -> System Devices -> PCI Bus -> IRQ Steering tab -> make sure IRQ steering is turned on -> reboot if making any changes under this tab. 4. Ndis2up bootlog errors are "normal". To read bootlog details and see delays in boot times, use Bootlog Analyzer [free]: Boot Log Analyzer (BLA) v1.23 32-bit for Windows 9x/ME checks/reports on slow loading/failed drivers (.SYS, .VXD, .DRV, .DLL, .386 etc) at bootup by analyzing C:\BOOTLOG.TXT: http://www.woundedmoon.org/win32/bootloganalyzer123.html Direct download [235 KB, freeware]: http://www.woundedmoon.org/win32/bootloganalyzer123.zip More info: http://www.mdgx.com/newtip14.htm#SUYG 5. Look under Control Panel -> System -> Performance tab -> if any of your drives/partitions is using "MS-DOS compatibility mode". If this is true, you may need to update VIA drivers for your mobo/chipset. 6. If your VMM32.VXD file from %windir%\SYSTEM got corrupted, you can recreate it. Look under this registry key [using Regedit]: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\VMM32Files Save the list of VXD files in a REG file [Regedit's Export function]. Copy that list and save it as wininit.ini inside %windir% [example]: Add/remove files until your list matches the 1 from the registry key above.Extract all these files from the Win98SE CDROM [CABs] into C:\VMMTEMP [example]: EXTRACT/Y D:\WIN98\WIN98_54.CAB /L C:\VMMTEMP NTKERN.VXD All files and their CAB locations are listed in CABL98SE.TXT [extract it from this zip]: http://www.mdgx.com/files/EXTCAB.ZIP Reboot/restart Windows. BTW: Make sure all VXD files newer than the ones from Win98SE CD-ROM are located in %windir%\SYSTEM\VMM32 . Optional: download these VMM32 tools: http://www.mdgx.com/files/VMMTOOLS.ZIP if you'd like to decompress [unpack] VMM32.VXD to normal size. More info: http://www.mdgx.com/98-3.htm#VXDBUG Reboot. HTH

It is, but still displays the license screen or if using an older version it will prompt to download a newer one.So you may wish to use the free, open source GPL [General Public License] version instead: http://arj.sourceforge.net/ Same features + command line switches, LFN support, but no nag screens, and no registration or prompt to download newer version. HTH

Please check your email.

the_guy is the author of this patch:Unofficial Jet 4.0 SP8 Patch for Windows 9x/NT4/ME [1.9 MB]: http://www.mdgx.com/files/Q918144.EXE It is part of the last batch of files he sent me a few days ago. I don't have Win2000 installed to test.

FAT = File Allocation Table: refers to disk structure implemented thru formatting an HD/partition with either FAT16 or FAT32 LFNs = Long File Names: refers to how many characters the OS supports for files + folders names + extensions. LFN = supports total 255 characters in M$ Windows OSes SFN [short File Name] = supports total 11 chars: 8.3 [MS-DOS style = 8 for name + 3 for extension] 911cd.net: http://www.911cd.net/ is a known web site where you can download emergency/boot/rescue CD [Compact Disc] images [iSOs] you can "burn" into a CDR [Compact Disc Recordable] and make it "bootable", so you can boot from it, and that way try to restore [some of] your data, if any was lost. Long list of boot CDs/floppies/images + rescue tools: http://www.mdgx.com/drv.htm#CDR HTH [Hope This Helps] _________________________________ BTW: SpinRite is shareware [pay $$ after trial limited time over]. 911cd.net + other similar sites provide rescue CDs/ISOs/floppies/IMGs for free [please see URL above]. If you're looking for backup, restore, formatting + fdisk software, please see this long list of free(ware) tools: http://www.mdgx.com/secrets.htm#FDPT HTH

Thanks, I didn't know about these 3 icon tools.Appears that they are all free(ware). BTW: IconLab works just fine under 98/ME [with GDIPLUS.DLL], even if the author says it is only for NT4/2000/XP/2003. I did not try IconLab under Win95. I've added them here: http://www.mdgx.com/toy.htm#GRA You may want to check out these icon editors [all linked at URL above]: PixelToolbox IconShop Free Icon Studio SnIco Edit Icon Suite

No, you can't use Resource Hacker [RH] to do what is described above, because RH only edits 32-bit executables [PEs], not 16-bit. That's why Exescope is for, edits also 16-bit PEs. And USER.EXE in all 9x/ME OSes is a 16-bit PE. More info + more similar tools: http://www.mdgx.com/toy.htm#HEX HTH __________________________________ noguru: Thanks for the heads up, my mistake, I didn't bother to try the actual links to files. But I found a newer version [TClock2] and also a newer build of old TClock [2.2.9 = 000105en98.zip below], and if you have WinXP, check out TClock Lite + LClock: * TClock2 v1.20 32-bit for Windows 9x/NT4/2000/ME/2000/XP/2003 displays the date and time in the Taskbar Tray, changes Start button/icon, Start Menu color/bitmap, highly customizable (free GPL): http://www.shii.org/tclock/ Direct download [96 KB]: http://www.shii.org/tclock/tclock2_120.zip OLD TClock [179 KB]: http://ftp.cs.pu.edu.tw/Windows/Softking/s.../000105en98.zip TClock Lite for Windows XP/2003 [374 KB]: http://homepage1.nifty.com/kazubon/tclocklight/ LClock for Windows XP/2003 [186 KB]: http://www.neowin.net/forum/?showtopic=157465

PROBLEMCHYLD: You must have IE 6.0 [Pre-SP1] when trying to install IE834707. the_guy created it to install only on IE 6.0 [Pre-SP1], and will not install on any other newer or older IE build [that includes IE 5.5 SP2, IE 6.0 SP1]. IE 5.5 SP2 files are build 5.50.4807.2300 IE 6.0 files are build 6.0.2600.0000 IE 6.0 SP1 files are build 6.0.2800.1106 So if the SED file contains [for example]: then you won't be able to install IE834707 even if using Win98SE, because it won't install on IE 6.0 SP1 nor on IE 5.5 SP2.It requires IE 6.0 [Pre-SP1]. HTH

Couple of important things we all need to know about properly using XMSDSK: http://www.mdgx.com/newtip12.htm#RAM Please read about the /T switch under "IMPORTANT:" [red + bold fonts]. HTH

soporific: No need for NDOS/4DOS detection if using only the COPY command. All you need to do is replace COPY or COPY/Y from MS-DOS using COMMAND.COM as environment shell with: COPY/Y/Z to "cover" for the NDOS/4DOS COPY /Z switch. And even if using COPY/Y/Z with MS-DOS COMMAND.COM, it won't complain, it will work anyway. SET COPYCMD=/Y sets the /Y switch [always overwrite the same file if present into the target directory] in the environment [memory] as default, until you reboot or until a batch file/command overrides it with other command line switch(es). To add this command to the "master" environment [before Windows 9x loads], you need to either add this line to your autoexec.bat or config.sys [MS-DOS older than version 6.00 does not support config.sys SET commands], or run it either from a batch file of from the DOS prompt before Windows loads. If you run this from within a Windows DOS box/session, it gets lost after you close the DOS box/session. Or add it into a batch file to always copy, even if it overwrites the same file in the destination directory. Run: COPY/? from any DOS prompt, or run: HELP COPY to see even more details. COPY is an internal [built-in] MS-DOS COMMAND.COM command, an actual file does not exist. NDOS + 4DOS also use COPY [built into 4DOS.COM], but with different switches. If you'd like to try 4DOS, it's freeware: http://www.jpsoft.com/download.htm Download [1.3 MB]: http://jpsoft.com/downloads/4dos/4dos750.exe Of course, you can detect the presence of 4DOS.COM in memory, if you like [example]: MEM /C | FIND /I "4DOS" IF ERRORLEVEL 1 GOTO D0S COPY/Y/Z X:\DIR\FILE ........ :D0S MEM /C | FIND /I "COMMAND" IF ERRORLEVEL 1 GOTO END COPY/Y X:\DIR\FILE ........ :END If you care to learn about INF + SED files to build iexpress installers, see: http://www.mdgx.com/INF_web/ and: http://www.mdgx.com/add.htm#INF Download CAB SDK 32-bit: http://download.microsoft.com/download/pla...n-us/Cabsdk.exe and start reading the DOCs. And Petr's findings are always invaluable: http://www.msfn.org/board/?showtopic=49202 HTH