MDGx

98MP10 · UPDATED · 12-10-2009 _____________________________________ DEL_DRM.INF does not delete/move/rename any files anymore. Only unregisters the DRM files [found in %windir%\SYSTEM] from the registry.Deleting the DRM files is not necessary if they are unregistered [using regsvr32.exe]. HTH

FYI... * RegMon v7.04 32-bit for Windows 9x/NT4/2000/ME/XP/2003/Vista/2008/7 monitors and displays in real time all Registry changes: http://www.microsoft.com/technet/sysintern...ion/regmon.mspx Direct download [265 KB, freeware]: http://www.filewatcher.com/m/Regmon.zip.271346.0.0.html How to FIX RegMon 7.0x to run properly on Windows 95/98/ME: http://support.microsoft.com/?id=931822 * Autoruns 32-bit for Windows 9x/NT4/2000/ME/XP/2003/Vista/2008/7 detects + displays all autostart/startup programs/monitors/TSRs/processes/services from all startup folders + Registry entries (freeware): http://www.microsoft.com/technet/sysintern...s/autoruns.mspx - Autoruns 9.56 for Windows 2000/XP/2003/Vista/2008/7 [577 KB]: http://download.sysinternals.com/files/autoruns.zip - OLD Autoruns 8.73 for Windows 9x/NT4/ME [485 KB]: http://files3.brothersoft.com/Autoruns-8.-73.zip * TCPView GUI + TCPVcon command line v2.54 32-bit tools for Windows 9x/NT4/2000/ME/XP/2003/Vista/2008/7 monitor, display + close all active TCP + UDP endpoints, lists remote addresses + TCP connection(s) status: http://www.microsoft.com/technet/sysintern...ng/tcpview.mspx Direct download [208 KB, freeware]: http://download.sysinternals.com/files/tcpview.zip Windows 95/OSR1/OSR2 require Winsock Upgrade 2.0 [963 KB] already installed: http://support.microsoft.com/?id=182108 * Process Explorer 32-bit for Windows 9x/NT4/2000/ME/XP/2003/Vista/2008/7 for x86, x64, AMD64 + IA64 CPUs displays + monitors ANY app/process/thread/TSR/executable (freeware): http://www.microsoft.com/technet/sysintern...ssexplorer.mspx - Process Explorer 11.33 for Windows 98/2000/ME/XP/2003/Vista/2008/7 [1.54 MB]: http://download.sysinternals.com/files/processexplorer.zip - OLD Process Explorer 9.25 32-bit for Windows 95/OSR1/OSR2 [1.18 MB]: http://www.toolzbydaman.com/utils/procexp.exe Windows 95/OSR1/OSR2 require Winsock Upgrade 2.0 [963 KB] already installed: http://support.microsoft.com/?id=182108 HTH Edit: Added MSKB fix URL for RegMon.

FYI...HKEY_LOCAL_MACHINE (abbreviated as HKLM) is the machine-wide hive key (HK) valid for all users on the same machine, and which takes precedence over any user key, i.e. HKEY_USERS\User_Name [HKU\User_Name]. Both HKEY_CURRENT_USER [HKCU] (the currently logged on user hive key) and HKEY_USERS\.DEFAULT [HKU\.D] (default user HK, in this case the current user) share basically the same information (mirror each other). Therefore, to answer your question, HKU\.D registry values are not needed if same values are already present under HKLM. You could manually (by using RegEdit.exe or by running REG/INF/VBS files) write/change valid values under HKCU and/or HKU\.D, but don't expect them to be also written under HKLM. In order to write/change a valid value for the entire machine, you have to put it under HKLM. The other way around... HKCU (and HKU\.D when that particular user is logged on) contain values specific only to the current user, to protect/preserve separate users + specific user settings. Also, needed machine-wide info is read from HKLM and written into HKCU (and mirrored into HKU\.D) every time a user logs on. In case u care to learn more about the registry: http://www.mdgx.com/reg.htm HTH

Who cares about MU, MF or RS? All 98 SE SP2 editions are here: http://www.mdgx.com/web.htm#SPX Enjoy.

So please update your documentation and accept my apologies for any confusion!No problem.Here is the updated Read1st.txt [look under the "KNOWN BUGS + FIXES" section]: http://www.mdgx.com/9s2m/read1st.php HTH

If that means we have [a small] chance some1 would like to volunteer to develop exFAT drivers, that would be awesome! But if that requires to pay for licensing, and implicitly charge for the drivers, thanks, but no thanks. Because a boatload of new devices will be released in the near future, I'm hoping: a. Either MS will relax the licensing issue, and *if* that happens, maybe a Linux developer can create a nix driver. In that case, I'm assuming it should be fairly easy to port such *nix driver to native DOS environment or even Win9x. b. Better, maybe some1 can develop their own exFAT driver [outside US] without having to go thru the MS license/patent process, and therefore that driver should be distributed for free [GPL?]. So... any volunteers? Just my 2 ¢ ... [rant] Patent on FAT? Sure, why not? Let's also patent the air we breathe. [/rant]

UPDATED · 11-27-2009 These updates have a new home. Enjoy. ___________________________________ 11-27-2009 UPDATE Here: http://www.mdgx.com/upd98me.php#112709 ___________________________________ * MSXML4.MSI -> updated. Thanks RetroOS! * SCR579X -> updated text for VBS 5.6. Thanks Fredledingue! HTH

You need to stop Windows from re-installing those 2 files [uSBMPHLP.PDR + IOS.VXD] each time after you update drivers or re-install NUSB, because you need to keep the updated versions installed by NUSB 3.3.If you have Win98 SE setup CAB files (copied by you or by 98SE setup) on your hard disk(s), it's a good chance they are located in %windir%\OPTIONS\CABS [%windir% = usually C:\WINDOWS]. Just rename that directory to something else, like C:\WINDOWS\OPTIONS.old\CABS.old (example). Then re-install your drivers and/or NUSB. And when Windows prompts you to reinstall/restore needed system files from Win98 SE CABs [you just renamed] or setup CD-ROM [make sure 98SE setup CD is *not* inside your CD/DVD drive(s)], answer Cancel or No [or similar]. Later when you're done installing your USB drivers + NUSB, rename that folder back to the original name: C:\WINDOWS\OPTIONS\CABS Done. FYI: Guide on how to copy Win9x/ME CABs from setup CD-ROM to your hard disk: http://www.duxcw.com/digest/Howto/software...bs/movecabs.htm HTH

Just FYI... I posted a link to updated WPI 2.2 here: http://www.mdgx.com/upd98me.php#112309 which is the new home for 1st post here: http://www.msfn.org/board/index.php?showtopic=46581 HTH Best, MDGx

Many thanks for your help.I've added your fix to READ1ST.TXT under the "KNOWN BUGS + FIXES" section: http://www.mdgx.com/9s2m/read1st.php Thanks!

Unfortunately Gabest and his followers (Gabest v2) discontinued development of MPC (ANSI) for 9x OSes in October 2008. Newest MPC (Unicode) newest build (106) is installed only by K-Lite Codecs (Unicode) for NTx OSes [2000/XP/2003/Vista/2008/7]: http://www.codecguide.com/about_kl.htm Older MPC (ANSI + Unicode) builds are available at the Gabest v2 SF site: http://sourceforge.net/projects/guliverkli2/ More links here: http://www.mdgx.com/toy.htm#MED Careful here... MPC Unicode (any build) may not be compatible with all 9x OSes functions, even if KernelEx allows it to run without error messages. And do not try MPC-HC (Unicode only) with 9x OSes: http://mpc-hc.sourceforge.net/ Won't work. Same here: newest MPC-HC build (1.3.3.3) is installed only by K-Lite Codecs (Unicode): http://www.codecguide.com/about_kl.htm User has choice which MPC edition to use during KLC install. IMO: MPC-HC (1.3.3.3) is still buggy, "normal" MPC (106) is better. HTH

UPDATED · 11-23-2009 Enjoy. ___________________________________ 11-24-2009 UPDATE Newest updates [11-23-2009] moved here: http://www.mdgx.com/upd98me.php#112309

I have compared the two files ('DirectX_Dec2006_redist' & your 'Unofficial DX90C'):-> there is 4 different files dsetup32.dll dxdllreg_x86.cab DXSETUP.exe dxupdate.cab but well, could be only because of the new files, -> and 11 new files (with new content) APR2007_d3dx10_33_x86.cab APR2007_d3dx9_33_x86.cab APR2007_XACT_x86.cab APR2007_xinput_x86.cab AUG2007_d3dx10_35_x86.cab AUG2007_d3dx9_35_x86.cab AUG2007_XACT_x86.cab FEB2007_XACT_x86.cab JUN2007_d3dx10_34_x86.cab JUN2007_d3dx9_34_x86.cab JUN2007_XACT_x86.cab but to say they are useless ... From what I remember from way back when...Dxsetup.dll + dxsetup.exe are from a previous DX install package, in order to allow unattended install [command line switches are enabled]. That's because the newer dxsetup.* files from official MS DX9 package won't allow unattended install [command line parameters are disabled]. More info here: http://www.appdeploy.com/packages/detail_pf.asp?id=169 and here: http://www.msfn.org/board/directx-9c-silen...allation-t.html and here: http://www.msfn.org/board/index.php?s=&amp...st&p=157335 and here: http://www.msfn.org/board/index.php?s=&amp...st&p=163905 Actually those cab files [xact, dx9 x64 + dx10] apply only to NTx OSes [2000/XP/2003/Vista/2008]. They have no meaning for Windows 9x/ME. And I don't think APR2007_d3dx9_33_x86.cab, AUG2007_d3dx9_35_x86.cab + JUN2007_d3dx9_34_x86.cab [managed dx9 newer than December 2006] work with 9x OSes either. Unless some1 would like to test them, and *if* they do work, please post here. Tx! But you are right [thanks for reminding me], looks like the unofficial DX 9.0c package is not that useless after all... Dxsetup.exe + dxsetup.dll allow unattended install with command line switches. So I just put back the link to unofficial DX installer: http://www.mdgx.com/files/DX90C.EXE here: http://www.mdgx.com/dx.htm#DX9 HTH

Tried it, rebooted, same problem.Aaah, shucks! We need somebody who connects to the internet using a dial-up modem to test this environment. Any volunteers? Thanks in advance for all the trouble, time and concern.

BTW, this page doesn't function properly with Firefox 3.5.5 either [links in tabs don't work]. Seems it requires MS IE. Another "brilliant" implementation of MS proprietary "standards"? Thanks for pointing it out. Unfortunately MS fee [they don't post the actual amount of money, but I'm sure it's a hefty one] are the show stopper. And looks like MS will make a lot of money from this license, because soon SDXC memory cards/sticks will need exFAT support: http://en.wikipedia.org/wiki/ExFAT#Disadvantages

As often happens, OFF-TOPIC, but not much :How much money do you think these guys are making nowadays from selling this?: http://www.techsoftpl.com/vxd/index.htm at US$ 429 apiece? http://www.techsoftpl.com/vxd/order.htm Maybe if they would decide to "let go" that software or provide a "complimentary copy" a C programmer willing to take the challenge could even be found.jaclaz Well, if the VXD model is not a viable solution [those guys sell their developer package waaaay too expensive, something I had no idea about because I am not a programmer], how about the SYS driver format [WDM, introduced in WinME + 2000]?The complete 98 DDK is still available [and free]... http://www.mdgx.com/add.htm#DDK respectively here: http://www.mdgx.com/spx/98DDK.RAR BTW: WinXP + 2003 DDK packages include all that is needed for Win98/ME programming, so one needs XP or 2003 to work on 98 SE/ME drivers, in case 98DDK [run from within Win98/ME] is not an option. About the native DOS driver model... I know 2 DOS low-level/driver programmers who might be able [and hopefully willing] to do this, I just haven't had time to write them yet, and I was actually waiting for some positive feedback from you guys @ MSFN. 1. Jack Ellis [makes free native DOS drivers for the FreeDOS.org project]: http://johnson.tmfc.net/dos/driver.html 2. Bret Johnson [makes free generic USB drivers for native DOS]: http://www.bretjohnson.us/ [All I'm saying is that FAT64 should be implemented in 9x OSes if possible *and* feasible. And I know it's possible, we just need to find some1 who agrees to do this for free. Edit: According to this Wikipedia page: http://en.wikipedia.org/wiki/ExFAT one needs a Microsoft license to distribute FAT64 software/drivers/etc. I have not checked to see if this license is free or not. If any1 knows more on this subject, please post here. Thanks. HTH Edit #2: Unfortunately MS charges fees for distribution, therefore not feasible nor affordable to develop independent exFAT driver.

I meant cluster size [smallest 4 KB -> largest 32 KB]:http://technet.microsoft.com/en-us/library/cc768180.aspx I've being collecting this info for years, and posted all here: http://www.mdgx.com/secrets.htm#FAT32 Source:http://www.ntfs.com/ntfs_vs_fat.htm You may want to take this up with the people @ NTFS.com. Source:http://en.wikipedia.org/wiki/ExFAT Please e-mail me if there is some eroneous info @ this Wikipedia page, so I can correct it asap. Please e-mail me with any corrections, so I can update the web page. Thanks for your time + concern. Edit: Updated my page with latest Wikipedia info: http://en.wikipedia.org/wiki/ExFAT

vwin32.zip link has changed its URL [seems that character capitalization matters on Japeth's server ]: http://www.japheth.de/Download/VWin32.zip HTH

I have received a PM from some1 who actually took time to analyze that file at my site, and he said it does not contain anything useful, because the last official MS update as of Dec 2006 already contains/installs all necessary files. So I removed the link to it from my DX9 page.But the file itself is still available [i won't remove it], if any1 cares to test it: http://www.mdgx.com/files/DX90C.EXE HTH

Gee... that's not good. Unfortunately I can't test a dial-up modem/connection on my system, I don't have one, and all my buddies have cable or DSL. Did this happen only with this new version of 98SE2ME? Have you tried older 98SE2ME versions, and if you did, did they work ok with your modem connection? Thanks for your time. Everybody: If any1 in this forum can test this [similar environment], and if any fixes/workarounds found, please post here. Thanks.

To my knowledge exFAT (FAT64) is available only for Windows 2000, XP, 2003, Vista, 2008 + 7 [look under "NEWS FLASH:"]:http://www.mdgx.com/secrets.htm#FAT32 But some1 with driver level programming skills who can afford to spend a lot of time developing + testing this can probably make a native DOS driver, or even adapt the XP one [EXFAT.SYS], or at least make a VXD driver compatible with 9x OSes. [?]

Unfortunately, like u said, this is a community run forum, and because of that, most of us here have only limited spare time for updating our projects and reading forum posts, which [if u ask me] is time consuming. That's why is difficult to keep an up-to-date centralized database of all updates.

However, Microsoft states in their MS09-062 security bulletin that KB958869 supersedes the KB938464 GDI+ update referenced in the MS08-052 security bulletin you cited. Therefore, the latest version of gdiplus.dll should be 5.2.6001.22319 and not 5.1.3102.5581. Curiously, the version of gdiplus.dll on my Win98SE system is 5.1.3102.2180 (from WinXP SP2) and I'm not sure how it got to be that way. References: http://support.microsoft.com/kb/954593 http://support.microsoft.com/kb/958869 Yeah, I'm aware of this new version, but I didn't have time to test it, and eventually [if it works properly = unless you or some1 else already tested it successfully] make a 98/98 SE/ME installer.If a new 9x installer is appropriate, I'll post it here when I have time. Please be advised that Windows XP/2003/Vista/2008/7 versions of GDIPLUS.DLL are usually not compatible with 9x OSes. You have to use the specific 9x versions Microsoft makes for these OSes. WinNT4/2000 versions may or may not work with 9x OSes. Therefore all new versions MS puts out must be tested 1st for compatibility. HTH

Must be KernelEx that provides compatibility with 98/ME, because MS has removed 9x support from the DX installer long time ago. [December 2006 ?] Anyway, even if the installer works ok with 9x OSes, there are no new files to be installed since Dec 2006.

Added links for all languages that I know of: http://www.mdgx.com/ietoy.htm#ICU * Unofficial Internet Explorer 6.0 SP1 Component Update (MDIE6CU) 2.9 for Windows 98 SE installs all current MS IE 6.0 SP1 updates + security fixes: http://www.msfn.org/board/index.php?showtopic=97816 - MDIE6CU 2.9 [13.6 MB, English]: http://www.mdgx.com/spx/MDIE6CU.EXE - MDIE6CU 2.9 [13.6 MB, German]: http://www.mdgx.com/spx/IE6CU_DE.EXE More info: http://www.nandlstadt.com/downloads.htm - MDIE6CU 2.9 [13.7 MB, Russian]: http://www.mdgx.com/spx/IE6CU_RU.EXE More info: http://forum.ru-board.com/topic.cgi?forum=...9&start=780 HTH