MDGx

Please see this post:http://www.msfn.org/board/?s=&showtopi...st&p=550394 ____________________________________ I have tried to install your hotfix v2 on Win98SE + IE 6.0 SP1 and all I get is this message:"The version of Windows you have installed does not match the update you are trying to install." So I extracted urlmon.dll, copied it over to %windir%\system and then regsvr32-ed it. The 1st hotfix [v1] works ok: http://www.mdgx.com/files/IE918899.EXE Please send me the official Q923672 fix at your convenience. E-mail [please click the blue E-mail link]: http://www.mdgx.com/form.htm Thanks in advance.

LLXX the_guy erpdude8: Here are the answers of the anonymous author of several unofficial 9x/ME patches to your comments/questions/requests: Hope this helps.

the_guy: Million thanks for taking the time to do this. That was the easy part though, to enumerate the added/removed/changed files. But the hard part [i was thinking of] is to figure out all the INF + REG changes since Dec 2005. Although I just reviewed all the INF files [and REG entries], and didn't find anything that would make a difference. In a nutshell [thank you again]: GDI.EXE/GDI32.DLL->912919 COMMDLG.DLL->WIN_19.CAB INTERNET GAMES MPLAYER.EXE->98SE DEVMGR32.DLL->98SE MPREXE.EXE->98SE START MENU TASKMGR->IE6SP1 DZIP32.DLL/DUNZIP32.DLL/ZIPFLDR.DLL->329048 TELNET.EXE->MS99-033 WEBVW.DLL->900725 MOVIEMK.EXE->262806 GDI.EXE/GDI32.DLL->918547 CLIPBOOK.EXE/CLIPSRV.EXE->ME The only files I can think of that could make a difference here might be the GDI*.* files [although they shouldn't]. The rest don't matter. ____________________________ PROBLEMCHYLD: Please try to use the GDI*.* files from 98SE2ME 12-14-2005 on your syster's computer, see if they make any difference. Thanks.

dhruba.bandopadhyay: IMO: Best full featured sound card for native DOS is SB AWE64. By far. It is compatible with most DOS games out there [sB, SB16, SBPro or AWE32 emulation for example]. You can actually play DVDs + DivX movies in native DOS by using 3rd party players + codecs. All you need is MS-DOS 6.22 or 7.10 [from Win98 SE]. You can also play MID, MP3, OGG, WAV, VOC, etc audio from native DOS, you just need a 3rd party tool. Or you can just listen to your audio CDs in the background while playing an SVGA game by using PLAY.EXE from Creative Labs. I use an SB AWE64 Gold for all DOS needs. I use an SB Audigy2 Platinum for all Windows needs [replaced the old SB Live!]. I quad-boot Win98 SE, MS-DOS 6.22, WinME and WinXP Pro SP2 [4 HDs in 6 partitions total]. AWE64 is completely disabled in 98SE, ME + XP [Device Manager X-ed, INFs + drivers deleted]. AWE64 runs in native DOS [either 6.22 or 7.10] enabled by these autoexec.bat lines [no memory used in this setup]: C:\AWE64\CTCM /B C:\AWE64\AWEUTIL /S /EM:GM /R:0 /C:0 C:\AWE64\MIXERSET /P /Q SET CTCM=C:\AWE64 SET SOUND=C:\AWE64 SET BLASTER=A220 I5 D1 H5 P330 E620 T6 SET MIDI=SYNTH:1 MAP:E MODE:0 BTW: The ftp.hornet.org links are 404. I've tried a couple of those DOS demos, pretty cool stuff. Thanks a lot. They work ok in native MS-DOS 7.10 [Win98 SE UI not loaded]. Using only UMBPCI.SYS + HIMEM.SYS in config.sys: http://www.mdgx.com/mem7.htm#7 AWE64 seems to provide proper SB emulation for sound. HTH

Sorry, I have not kept old 98SE2ME versions to compare, and besides, all the changes I've made in the past ~ 8 months or so are too numerous and too complex to try to go back.But if you kept the old 12-14-2005 98SE2ME.EXE edition, please send it to me attached to email [please click the blue E-mail link]: http://www.mdgx.com/form.htm and I'll see what I can do. As I said before, I don't think 98SE2ME is related to shudown/power off errors, those are Win98 SE errors that are quite well known, and there are a lot of things that can be done to fix them. More info: http://www.mdgx.com/98-5.htm#FWUE APM/ACPI/BIOS power saving issues are usually involved. Another good idea is to restore 98SE system files 1 by 1 from the backups created by 98SE2ME option 2 in %windir%\SYSTEM.9ME [usually C:\WINDOWS\SYSTEM.9ME]. Reboot each time after restoring a file. Please notice any difference in behaviour, and if you do, please let me know. Hope this helps

Sorry about misunderstanding your question.The USER*.* files don't have anything to do IMO with DOS mode exit/restart. What you describe are 2 different DOS modes, which you can go to in different ways. 1. DOS box/window/session is a virtual DOS mode emulated within Windows [a.k.a. Virtual Machine (VM)]. From that [either windowed or even full screen, don't let that fool you] you can type EXIT and press Enter to return to the Windows UI [user Interface]. 2. Native/pure/true/real MS-DOS mode is outside Windows UI, and can be achieved 2 ways: A. Either boot directly to real MS-DOS [with no way to return to Windows UI, unless you type WIN and hit Enter, which loads the UI] by tweaking your MSDOS.SYS: http://www.mdgx.com/msdos.htm and CONFIG.SYS: http://www.mdgx.com/mem7.htm#7 or B. Go to native MS-DOS [but be able to return to Windows UI by typing EXIT or WIN and pressing Enter] by running the MS-DOS Prompt shortcut created by Windows when you 1st installed your OS. More info: http://www.mdgx.com/last3.htm#DOS2DOS http://www.mdgx.com/lastweek.htm#MSDOSPROMPT http://www.mdgx.com/newtip1.htm#DOS Therefore, the inability of returning to Windows UI by typing EXIT and pressing Enter is not related [to my knowledge] to replacing system files with WinME versions by 98SE2ME. That is because I'm usually very careful not to disable Win98 SE features, especially the ability of accessing DOS modes. DOS shortcut properties can be changed by modifying a PIF file settings [the "Exit To DOS.PIF" shortcut for example] or whatever custom PIF [Program Information File] you might be using, or a PIF created/modified by some software/game you were installing/running [please see 3 URLs above for more details]. When you access native DOS under Windows [native DOS, but with the WIN module loaded in memory as TSR, you can see by running MEM/C/P], Windows creates temporary *.WOS files [backs up config.sys + autoexec.bat] and modifies original files to add this line: DOS=SINGLE This line won't allow Windows UI to (re)load/(re)start until you remove it from your config.sys and then reboot. More details at URLs above. There are other ways of disabling the return to Windows UI after going to DOS mode [similar to running "Exit To DOS.PIF"]. Example: modding WIN.COM as described here [you can download as 98ATXFIX.ZIP linked at URL below]: http://www.mdgx.com/98-4.htm#98ATX and/or loading NOOFF.COM in memory [as TSR = Terminate and Stay Resident] from autoexec.bat or from config.sys or from DOS prompt. NOOFF.COM is also linked at URL above. VPOWERD.VXD cannot be replaced with WinME version, because does not work at all. The explanation in the BUG + FIX issue you have read, refers to vpowerd.vxd, only to explain better the dependencies among system files. The USER*.* files from WinME to my knowledge [i have not compared them byte by byte nor decompiled them, and there is no documentation at MS web site that would explain such differences] correct a few system bugs [like mouse random moves, lockups, GPFs, IPFs etc], enhance performance by using better memory access, and probably streamline some UI features. Of course, all this is speculation, found by searching MSKB for USER.EXE + USER32.DLL bug fixes: http://support.microsoft.com/search/?qu=us....dll+windows+98 I've been using the WinME USER*.* files on my 98SE computers for > 5 years, and never had any errors that I could have linked back to them. I've also installed 98SE2ME on some friends' computers, with similar effects. I see no need to associate the USER*.* files strictly with option 3, because the file dependencies resolve ok with the WinME system files replaced by option 2, and these 2 files bring a large enough benefit to the OS in my opinion, in order to keep them as part of option 2. Another thing you may want to try, is fix or disable APM/ACPI/BIOS/CMOS/USB/monitor/hard disk power management features, which are the more likely culprit for DOS lockup and/or Windows shutdown/power off errors: http://www.mdgx.com/98-5.htm#FWUE In conclusion, to my knowledge 98SE2ME does not change DOS access abilities, but if you determine otherwise after detailed research, please let me know and I'll try to fix it. A good place to start is to restore 98SE system files 1 by 1 from the backups created by 98SE2ME option 2 in %windir%\SYSTEM.9ME [usually C:\WINDOWS\SYSTEM.9ME]. Reboot each time after restoring a file. Please notice any difference in behaviour, and if you do, please let me know. Hope this helps

LLXX:IMHO: This sounds like a good idea. If you can do it, that is. Basically, such a patch would: 1. detect the version/build installed 2. backup the original file 3. patch the orginal file 4. reboot. Example: UXTHEME.DLL patcher is a universal patcher which modifies this XP/2003/MCE DLL to be able to use themes without having to purchase WindowsBlinds or other 3rd party tools. Can patch all versions of the DLL, including XP RTM, XP SP1, XP SP2, XP Post-SP2 hotfix Q319740, 2003 RTM, 2003 SP1, MCE 2004, MCE 2005, Vista beta 1 etc. It can be found here: http://www.softpedia.com/get/System/OS-Enh...tiPatcher.shtml WindowsX is the author. Another example of a multipatcher is LvlLord's TCPIP.SYS patcher for Windows XP/2003 [increases the number of concurrent TCP connections, otherwise limited by M$ in the original driver]: http://www.lvllord.de/?url=tools Thanks for listening.

I've been using an SB AWE64 Gold and an SB Live! in native MS-DOS for quite a while. SB 16 PCI drivers: http://us.creative.com/support/downloads/w...mp;modelnumber= SB AWE64 drivers: http://us.creative.com/support/downloads/w...mp;modelnumber= SB Live! drivers: http://us.creative.com/support/downloads/d...p;x=23&y=11 SB Live!, 16 PCI, AWE32, AWE64 DOS drivers + tools: http://easymamecab.mameworld.net/html/snddosdr.htm http://www.vpk.psc.ru/sound_drivers.htm http://www.urr.ca/dosdrivers/drivers.htm More info on how to use an SB Live! in native DOS: http://www.mdgx.com/newtip18.htm#DGSBL Hope this helps

EXTRACT.EXE [only Short File Names = SFNs] or EXTRAC32.EXE [preserves Long File Names = LFNs] are installed by all Win9x/ME OSes and IE 5/6, and do the job just fine. These are command line tools.More info: http://www.mdgx.com/newtip15.htm#CABEX http://www.mdgx.com/last4.htm#EXTRACT http://www.mdgx.com/newtip8.htm#CABEX Download EXTCAB.ZIP and see the CAB*.TXT files: http://www.mdgx.com/files/EXTCAB.ZIP W95-11D.EXE [and *.ZIP] both also contain the CAB*.TXT files with all files from the CABs from all Win9x/ME OSes: http://www.mdgx.com/95.htm Hope this helps ______________________________________ oscardog: Inctrl5 can be found here [767 KB]: http://digilander.libero.it/rareware/inctrl5.zip HTH

Done.Thanks. Here they are: http://www.mdgx.com/dx.htm#DXM All 4 DXM*.EXE files are now updated with newest versions.

Thanks.Done. Please try it again: http://www.mdgx.com/add.htm#PNT

This WinME file is binary identical with the 1 from 98 SE setup CD.Version is also the same [3.10], it's the very old Win3.1 16-bit file. I don't know of anybody who uses cardfile currently. HTH

1. Your answer is here:http://www.msfn.org/board/index.php?s=&amp...st&p=547939 or see READ1ST.TXT, the "KNOWN BUGS + FIXES" section: READ1ST.TXT 2. About Jet database errors... Make sure you have all Jet updates + patches installed for your OS: http://www.mdgx.com/add.htm#JET IMO, I don't think the USER*.* files from WinME have anything to do with Jet errors. 3. 3rd party network/internet monitors [free(ware)]: http://www.mdgx.com/fw.htm#MNT Hope this helps Best wishes.

This issue is explained in detail, and how to fix it step-by-step, under the "KNOWN BUGS + FIXES" section of READ1ST.TXT: http://www.mdgx.com/9s2m/READ1ST.TXT Hope this helps.FYI: From now on please post all 98SE2ME related issues in the 98SE2ME dedicated forum: http://www.msfn.org/board/?showtopic=46349 That's the one I check frequently in order to be able to answer questions/requests/etc. Creating a new topic with the title 98SE2ME will only confuse everybody. Thanks.

DXM9X.EXE already includes DANIM.DLL 6.03.01.0148 [1.16 MB]: http://www.mdgx.com/files/DXM9X.EXE I have removed IE329919.EXE which installs older IEPEERS.DLL 6.0.xxxx.xxxx. Thanks again. Best wishes, MDGx

Correction:I have tested IE918899.EXE, and all files work ok with IE 6.0 SP1 on my 98SE setup. I have added IE918899 here: http://www.mdgx.com/ietoy.htm#IEC Download: Unofficial MS IE 6.0 SP1 Patch for Windows 98/98 SE/NT4 SP6a/ME [3.63 MB].

Thanks a lot for the fixes. I'll test them see if they work ok, and will post them at my site. EDIT: Posted all fixes: http://www.msfn.org/board/?showtopic=46581

Restore Damaged Registry is here: http://www.mdgx.com/newtip10.htm#RDR HTH

May I have a copy of KB830460 please?Thanks in advance.

I have removed WinME DSKMAINT.DLL from 98SE2ME a long time ago: March 18 2005.I have also added code into O2.BAT [installs options 1 + 2] a while back to restore DSKMAINT.DLL from Win98 SE setup CD, just in case some1 still has the WinME file by accident. HTH

PsycoUnc: I've tried all 8 options twice each, and all worked ok [no errors, all files copied ok] on my tweaked system and also on a fresh [from-scratch] install. Please notice that there is now file check and version check in place to detect if certain files [all files in %windir%, %windir%\sysbckup, %windir%\system\iosubsys, all ME files from C:\9!M which are newer than the ones from the ME setup cd, all files in C:\Program Files\GameZone, etc] are already installed. If newest versions are already installed, those files are not copied over anymore. Please download 98SE2ME.EXE one more time [3 MB]: http://www.mdgx.com/4 98SE2ME.EXE you had might have been corrupted... [?] Please try again at your convenience, and please let me know if it works ok. Thanks for your feedback.

I have added new hhctrl.ocx to HHUPD.EXE [unofficial HTML Help 1.41 for 98/NT4/ME]:http://www.mdgx.com/add.htm#HHU and included the reg entries from the Win2000 INF. Thanks. ____________________________________ I have [hopefully ] fixed 98SE2XP:http://www.mdgx.com/98-5.htm#MP9 Please try it again, and let me know if it works ok. Thanks for your feedback. ____________________________________ I believe MS updated only XP SP1 + 2000 SP4 versions of URLMON.DLL, which do not work properly with 98/ME in my experience.The last 98/ME urlmon.dll version that works properly with IE 6.0 SP1 on my PC is 6.00.2800.1551 [from official cumulative update MS06-042]. HTH ____________________________________ This mean deleting large files bug is fixed?No, not to my knowledge anyway. The only fix I'm aware of is to replace the IE 6.0 SP1 BROWSE*.DLL files with older IE 5.5 SP2 files from newest cumulative update. HTH ____________________________________ erpdude8: I have fixed GRPHFLTS.EXE: http://www.mdgx.com/add.htm#PNT Please try it again, and let me know if it works ok. Thanks.

I have posted step-by-step instructions on how to install DX9c August 2006 Redist:http://www.mdgx.com/dx.htm#DX9 HTH ____________________________________________ I have tried the new hhctrl.ocx from Win2000 fix on my 98SE computer for a week, and works ok.I have opened + browsed through a bunch of different CHM files, created mostly for WinXP + 2003. So I have added this new hhctrl.ocx version to HHUPD.EXE: http://www.mdgx.com/add.htm#HHU Just download "Unofficial Windows 98/NT4 SP6a/ME HTML Help Update 1.41 5.2.3790.309". HTH

I'm not Eck, nor anybody else, my only "handle"/"nick" here at MSFN is MDGx. You got a couple of good points about posting a little more info about the official bug/fix and related link(s), if any, at each unofficial fix/update. I'll try to do this from now on. Although [in case you haven't noticed], I always post a link to the official MS0x-0xx and/or KBxxxxxx article for all unofficial updates. Reading through those MS articles enables the reader to understand where the file comes from originally, and what is the purpose for the respective bug and its fix. IMHO: About posting more links/comments to justify why an update [official or unofficial] is needed, I think that if I post a short description of the bug and a link to its fix, that's enough reason to install it. Besides, I always post the link to MS0x-0xx and/or KBxxxxxx article, which explain(s) in detail the bug and its fix. EDIT: BTW: All updates that link to MS0x-0xx articles are called "Security Vulnerability Fixes" [usually critical from security point of view, must be installed if using networks/internet]. All updates that link to KBxxxxxx articles are called "Fixes" [not critical from security point of view, but useful, because fix OS bugs, which sometimes can be serious]. HTH Thanks, MDGx

All free(ware): - Firewalls: http://www.mdgx.com/fw.htm#FWL - Anti-spyware: http://www.mdgx.com/fw.htm#ASP - Anti-virus: http://www.mdgx.com/vir.htm#TL - Ad+ popup killers: http://www.mdgx.com/fw.htm#AKL - Net monitors: http://www.mdgx.com/fw.htm#MNT Security guides: http://www.mdgx.com/modem.htm#TS MS OSes + web browsers bugs: http://www.mdgx.com/bug.htm If you wish to get free email newsletters: http://www.mdgx.com/bug.htm#ENL HTH