MDGx

I stand corrected, unfortunately. I found a bug in NVidia 77.72 video drivers for Windows 95/98/ME. This happens in 98 FE, 98 SE + ME. Trying to play any DVD movie [even region free (encoded as "region 0")] using PowerDVD 4.xx or 5.xx [any build] pops up this error message: "Error Code F4D41436 The TV out port of your display card is not working properly." And this is the Detailed button message: "This copy protected disc cannot be played when the TV out function is enabled." Say what? This never happened with any other driver build, and I tried them all. Nothing I have tried fixed this. WinDVD 4/5/6, WMP9, WMP10 [from XP SP2] + MPC [Media Player Classic] work ok though. But PowerDVD is my favorite DVD player, so until I get to upgrade to a newer version, I reinstalled older NVidia 71.84 [corrected] drivers.

To my knowledge 98SE2ME files don't change the OS version. Even after installing option 3, if u want to reinstall 98SE, it should work ok. Why I suggest doing this from native MS-DOS, is because after u installed MS IE 5/6 you won't usually be able to reinstall over into the same folder, unless u run the DOS setup. What to do even if u have a full setup CD: it might work as upgrade if you rename all WIN.COM, VERSION.DLL, VER.DLL + WINVER.EXE files on all your HDs. Then reboot from a 98SE floppy, pop in the CD and run setup from native DOS. I have a full CD and setup works ok from DOS. Hope this helps.

95 + 98, same as ME [all part of the 9x series] are based on DOS the same way. None of them can load without the good ol' 16-bit DOS layer. Try to remove IFSHLP.SYS from ME, see if the UI loads. I'll save u the trouble, it won't. They all use the DOS memory scheme [conventional, upper, high + extended] the same way. The only improvement ME came up with was the new [at the time] WDM/WHQL driver model taken from 2000 [*.SYS drivers instead of *.VXD], and later on adopted into XP + 2003. Longhorn will use an even newer drive model. Moreso, try to delete IO.SYS, COMMAND.COM +/- MSDOS.SYS, 9x can't even boot. 1 of the few changes they made to ME in order to mimic the loading style of NTx, was the inclusion of HIMEM.SYS as part of IO.SYS. Yes, u can delete HIMEM.SYS from ME, but that's called faking it, because the HIMEM model is identical with 98 FE + 98 SE. Just because MS disabled [read "hid really well"] the native MS-DOS mode, that doesn't make it so. Just apply 1 of the available real DOS mode patches: http://www.mdgx.com/dos.htm#ME to the ME system files, and you'll have full DOS mode back. The usability of RAM is restricted by the 32-bit X86 CPU, which can address a maximum of 4 GB of memory [virtual address space] and up to 128 GB [physical memory space], divided in 4 MB [4096 KB] blocks. 64-bit CPUs can address up to 16 TB of RAM [virtual] and respectively 128 TB [physical]. Further restrictions exist because of the ancient MS memory model implementation [in Windows they call it VMM = Virtual Memory Manager], which in 9x series can address only up to 2 GB [theoretical limit], but in reality this is only 1 GB or in rare cases 1.5 GB [practical limit]. This is because 2 GB out of 4 are reserved for the OS itself, kernel, core, memory management + disk swapping [file paging], and only ~ 2 GB are available to programs, minus ~ 1/2 GB reserved for HD + video hardware. User resources are an entirely different matter. These are globally called "system resources", and consist of two 64 KB blocks of memory Windows allocates to programs/processes/TSRs for tracking purposes. 1 of these blocks makes up the user resources and the other [as u probably guessed] makes up the GDI [Graphics Device Interface] resources. Neither of these have anything to do with real memory, a.k.a. RAM. Resources are only place holders [pointers] for programs [dialogs, icons, bitmaps, cursors, menus etc] + hardware [keyboard, mouse, printer, VGA card etc]. If you wish to know more on these subjects, MSKB, MSDN + MS TechNet offer plenty. I've been using all MS OSes + environments [that's what the 3.x series are actually] starting with DOS 5.0, and played around with ME for almost 2 years until I went back to 98 SE. And I have to say ME is overall one of the most troublesome MS OSes. ME should have been released for what really is, just a patch to 98 SE. Just because u [and I and a few others] didn't have many BSODs, that doesn't make ME a reliable OS. Take for example the hordes of users who felt like throwing their computers out the window just because ME blew up on them. It all depends on the hardware and driver compatibility. If you care to classify, the best MS desktop OS to date is XP Pro in both 32 and 64-bit versions, and the best MS server OS is 2003. But in the server world, many people trust the NIX/BSD models better. In the end, it's all a matter of opinion.

OEMBIOS.BI_BOOT.BIN NT5INF.CA_ OEMBIOS.CA_ OEMBIOS.DA_ DPCDLL.DL_ PIDGEN.DLL SETUPREG.HIV OEMBIOS.SI_

That must be a typo. There is no Win98 ver 5. Ver 5 are only Windows 2000, XP, 2003 + Longhorn. WinME is 4.90.3000, which is the newest they made from the 9x series. More info + links about all MS OSes builds/versions/releases: http://www.mdgx.com/win.htm Hope this helps.

If u are using this computer in a multiuser environment, and u don't have admin or owner privileges, there is not much u can do, unless u email the sysadmin to allow u to use sysedit, and he/she is nice enuff to let u do that. If u are using some sort of software that is protecting your boot and/or system INI files from being modified, u may need to disable it. Also, see if u have a progman.ini file in your %windir% folder [usually C:\WINDOWS]. If u do, open it in Notepad and look for a line that stars like this: [Restrictions] EditLevel=x where x can be from 1 to 4 . If u do find such line, place a semicolon [ ; ] in front of it and save the file. More info @ MSKB: http://support.microsoft.com/?id=75337 You may need to change PROGMAN.INI attributes if it is hidden, system or read-only: ATTRIB -H -R -S %windir%\PROGMAN.INI This primitive protection function is reminiscent from Win3x days. That Control Panel issue should not affect the use of sysedit. Sysedit.exe is a very old Win3x 16-bit executable, like a stripped-down text editor, that can edit only 4 small ASCII files. Preventing only it from running is not that simple, because by doing so, u may also disable from running other similar executables. So it is more likely that something that is already loaded and running, is preventing your boot files from being modded. I know firewalls that protect local system files from being deleted/moved/edited/etc. I can't think of anything else for the moment. Hope this helps.

Hi MDGX, I suppose it is too soon to sent this alpha version to the general public. I need more test results before this. Too many files are updated, not the same as in SE package. Petr Roger that.

Thanks for your feedback. I know only few 98SE computers that can use ndis.vxd from WinME. Unfortunately majority can't.

Things I've done to help spread the word about your SP:- I put a link at my front page [i have ~ 4000 unique hits/day]: http://www.mdgx.com/ - I added a link here: http://www.mdgx.com/web.htm#SP1 - and here [98SE2ME forum]: http://www.msfn.org/board/?showtopic=46349 Things you can do to spread the word: - ask Gape if he would like to make your topic a "sticky". - edit the 1st post here, add the rapidshare link and a few words about the SP at the top. - email Jim or Tim @ MajorGeeks [they are buddies of mine, u can mention my name if u think it helps]: http://www.majorgeeks.com/page.php?id=2 - as you should email Danny Boss @ SoftPedia: http://www.softpedia.com/ - email a few other high visitor hit count news web sites, I would suggest at least: - WinXPCentral [Digital Dave is a buddy of mine, u can mention my name if u think it helps]: http://www.winxpcentral.com/ - TechSpot [Thomas McGuire is a buddy of mine, u can mention my name if u think it helps]: http://www.techspot.com/ - Fred Langa @ LangaList [Fred is a buddy of mine, u can mention my name if u think it helps]: http://www.langa.com/ - PC World: http://www.pcworld.com/ - Scot Finnie: http://www.scotsnewsletter.com/ - Warp2Search: http://www.warp2search.net/ - BetaNews: http://www.betanews.com/ - NeoWin: http://www.neowin.net/ Hope this helps.

98SE voltrack.vxd patch was created by a person who is using only 98SE, I'm afraid.And unfortunately I don't have the hexed bytes info, and even if I had that, hex code is probably different in 95, and probably different bytes need to be modded.

Welcome to MSFN forums, WatcherSea. Please accept my sincere thanks for your kind appreciation regarding 98SE2ME. I'm glad you found it useful. About your problem, this is what u can do: Restore [extract] sysedit.exe from 98SE setup CD back into %windir%\SYSTEM , in case it was damaged. More info: http://www.mdgx.com/me1.htm#RESE If that doesn't work, scan [run scandskw] for errors + fix all your HDs/partitions. If that doesn't work, scan your computer for viruses. More info on how a virus can disable programs in Windows: http://securityresponse.symantec.com/avcen...siral.b@mm.html If that doesn't work, see this security restrictions guide and make sure registry values which disable programs are not turned on: http://www.mdgx.com/newtip9.htm#RESTRICT If that doesn't work, search your entire registry for any sysedit.exe restrictions: run regedit -> Edit -> Find -> type sysedit -> view all keys/values (if any) containing sysedit.exe and sysedit, and if u think they disable it, delete them. Make a full backup of your registry [i.e. save it as REG file] prior to modifying it. More info: http://www.mdgx.com/newtip12.htm#REGBAK If that doesn't work, make sure if running Norton SystemWorks or similar tool that system files protection is not turned on. You may need to turn protection completely off. If that doesn't work, use the alternative sysedit tool [31 KB, free] linked at URL above: http://www.mdgx.com/me1.htm#RESE Hope this helps.

Petr, I've tried your alpha FESP on a "fresh" install of 98FE + IE 6.0 SP1 + DX 9.0c + MS Intellipoint Mouse 4.12. Works ok so far. Good job. Because I have installed DirectX 9.0c prior to FESP, it prompted me to keep these files: kswdmcap.ax joyhid.vxd which are newer than the ones from FESP. Because I've installed MS Intellipoint Mouse drivers 4.12 prior to FESP, it prompted me to keep this file: msmouse.vxd 1 minor annoyance [same as you mentioned]: that mqrt.dll [Message Queue Run Time] dialog pops up the "cannot find" prompt, but installer finishes ok if box dismissed. I was wondering why do u need to use mqrt.dll? Is it necessary for Gape's infex installer? So far I've seen very few tools that use it. Another thing: I noticed you are using Gape's modded explorer.exe [also patched by Dr. Hoiby to fix 8-bit icons]. When one clicks the Start button, it shows the "Windows 98 Second Edition" banner, only if "Show small icons in Start menu" box is not checked in Taskbar Properties. I fixed the BMP to show "Windows 98 First Edition" [71 KB]: http://www.mdgx.com/spx/FEEXPLOR.ZIP Please let me know after you downloaded the zip so I can remove it. Replaced BMP using Resource Hacker: http://www.users.on.net/johnson/resourcehacker/ New bitmap included in zip. Keep up the good work.

Petr, All your "TargetWinxx=" directive tips checked out ok. Many thanks. Therefore I repacked these iexpress updates [same file sizes as old files]: 98KRNLUP.EXE = replaces both FEKRNLUP.EXE + SEKRNLUP.EXE Q249824.EXE = replaces both F249824.EXE + old Q249824.EXE * Unofficial Windows 98/98 SE KRNL386.EXE build 4.10.1999 Fix [172 KB, English]: http://www.mdgx.com/files/98KRNLUP.EXE This Fix may correct Kernel errors after installing Cursor + Icon Handling Fixes. * Unofficial Windows 98/98 SE 255 Devices Additions + Removals Error VOLTRACK.VXD build 4.10.1999 Fix: http://support.microsoft.com/?id=249824 Direct download [105 KB, English]: http://www.mdgx.com/files/Q249824.EXE Posted here: http://www.mdgx.com/web.htm#98SE I've tried them and they work properly with 98 SE and 98 FE.

This is probably due to NVidia INF file installer which resets all Video Overlay registry values to "factory" defaults every time it installs a new driver version.What I do: I keep a backup of the Video Overlay registry key + values, install the new drivers, and then run the REG file to restore my favorite settings. Then if I'm not happy with the way it "looks", I play a DVD, reset the brightness +/- contrast from Display Properties or DVD/video player until looks ok, and then make a new backup of those reg keys + values. Have you tried to: right-click empty Desktop background spot -> Properties -> Settings tab -> Advanced button -> GeForce 6800 GT [name/model/type of your video card here] -> Color Correction -> "Apply color changes to:" -> select Overlay -> select All Channels -> make sure "Color Profile:" is in Standard Mode -> drag the Brightness + Contrast sliders to right/left until your video/DVD/movie playback looks satisfactory [play a DVD or video while doing this so u can see the changes] -> Apply -> OK -> OK. This applies to all DirectX 7/8/9 compliant DirectShow/NetShow APIs driven tools, including WMP 6/7/9/10, Media Player Classic [MPC], Nero Player, DivX Player, Real Player/RealOne, Sonique, WinAmp, JetAudio, NVidia DVD/Video Player, WinDVD, PowerDVD, DVDPLAY.EXE [bundled with Win98/ME] etc. I have done this in both 98SE and XP SP2 using 9x/ME + 2000/XP 77.72 drivers, and it works. Hope this helps.

Thanks a lot for your cool batch tips.My idea: instead of creating a second, third, etc... backup copy of all those files each time the user installs option 3, it seems easier IMO to just detect each *.W98 file version using GETVER, and if all 98SE backed up files are found in the right places, give the user 2 choices: 1. either restore old 98SE system files from *.W98 backup [done by running RSTR3F.INF], then reboot, and finally, after 98SE UI restarts, the user can run again 98SE2ME.PIF to safely install option 3 fresh 2. or proceed to (re)install option 3 with 3 (sub)choices: 2a. create new backup set [not overwrite old ones] and then install option 3. 2b. overwrite old backups with new ones and then install option 3. 2c. install option 3 without creating new backups. But it's getting late, so I'll probably do this tomorrow. Laters

As far as I know, SETUPX.DLL is targeted specifically for each OS build. 98SE 4.10.2222 uses setupx.dll 4.10.2222, which allows to install 98SE OS from CABs the way MS wants, which is to first check [among other things] for previous OS compatibility and compliance. No previous WinOS, no go. Example: if u have 98SE upgrade setup CD and want to install it onto an empty HD [without any previous MS OS], u can't, unless u mod SETUPPP.INF right after starting the install [example]: [data] OEMUP=1 and create a new MSBATCH.INF with this line: [setup] ProductType=1 This applies also but the other way around to 98FE/98SE OEM setup CDs. And this "fix" also needs a hexed setupx.dll, which is pretty hard to do, because in each language edition and in each setup CD version [Full, Upgrade, Updates, OEM, MSDN subscriber, custom OEM/VAR, etc] setupx.dll is different. This works great with 98 FE as far as I know, but might not work in 98 SE, if u don't hex setupx.dll from 98SE CD properly. More info [OSR2]: http://www.mdgx.com/osr2.htm#INSTAL More info [98 FE]: http://www.mdgx.com/98-1.htm#BLUES IMHO it's best to keep original setupx.dll [from setup CD] for each OS, unless u want to hex it for extra power.

Petr,Wow, looks like u solved the SED "Targetxx" problem. Many thanks for your hard work. I'll try your tips to recreate some of my iexpress packages to make them install on both 98FE + 98SE. I found something about INF "CopyFiles" directive length limit @ MSDN: http://msdn.microsoft.com/library/en-us/in...fb2d300.xml.asp and other good to know INF limits. But here is my idea [besides deleting all spaces, which I'm sure you've done already]: try to shorten each string to 1, 2 or 3 characters. Example [applies to the 1 u posted] = broken in half by 1 space so it will fit in this page: CopyFiles=CBT,CCB,CMD,CEB,CF,CGR,CGR2,CHL,CHT,CIN,CIO,CMA,CME, CMS,CMI,CMU,CS,CS32,CSB,CTC,CTR,CTV,CVM,CKB891711 This way string length was reduced from 285 chars to 102 chars [not counting the "CopyFiles" string]. Now it should work ok. Hope this helps.

1. Windows Explorer toolbar can be customized only in ME, not in 98SE, unless you install 98SE2ME option 3.In 98SE without 98SE2ME, u can customize only the IE toolbar, no matter which IE version u have. This was another step towards achieving "perfect internet integration" [together with "Active Desktop"] MS implemented into ME. 2. Please post your config.sys + autoexec.bat [if u have any in C:\ root] contents here, maybe I can fix your winoldap problem. Config.dos doesn't do anything [it's 9x backup of MS-DOS 5/6 C:\config.sys], unless u rename it to config.sys and place it in C:\ root. Steps u can take to try to fix winoldap errors [without knowing more details about your specific error(s) I can't help too much]: - if u run older DOS programs/games from within Windows, make sure u create appropriate PIF files fo each of them, eventually following the manufacturer guidelines on which kinds/amounts of memory are needed for each. Note that there are certain DOS based programs/games that will NOT run from within Windows. In such cases, u need to exit/reboot Windows to native MS-DOS mode. More info here: http://www.mdgx.com/newtip23.htm#WDBT - scandisk all your HDs and fix all errors [if any]. - check device manager for errors/conflicts, red/yellow marks, try to fix them by (re)installing current drivers, or by enabling IRQ steering if not enabled. - use Startup CPL [freeware]: http://www.mlin.net/StartupCPL.shtml to disable, and use Ctrl+Alt+Del to close all running apps/TSRs/processes/DLLs, except necessary ones for Windows to run properly. 3. Option 3 backs up a bunch of system files in %windir%\system\*.W98 and explorer.exe as explorer.W98 in %windir% the 1st time u install option 3. But if u reinstall option 3, those *.W98 backups will be overwritten with the new backups made every time u install option 3, which means all 98SE backups will be replaced with ME backups, which means u can't restore option 3 anymore *if* u reinstall it. Therefore, try to install option 3 only once. I've added a new choice into 98SE2ME.BAT for option 3, to *not* install it [press N to not install it or Y to install it], only if previous *.w98 backups are detected in %windir%\system. 4. I have been able to reproduce the BMP, GIF + JPG file open errors, and found out how to fix them. This is due to installing shimgvw.dll from ME into options 1, 2 + 3. Please get 98SE2ME.EXE the 6-26-2005 edition to fix this. Hope this helps.

Try to run SETUP.EXE from native MS-DOS. Copy all files from the CD directory [if using 98SE: WIN98 is the CD directory name u should copy] onto your HD first. Then boot to native MS-DOS, eventually using a boot floppy. Then run SETUP from the CAB directory on your HD. If u need to use setup with particular switches: http://www.mdgx.com/last2.htm#SETUPSW Hope this helps.

I'm wondering if anybody [except MS] has such info at all, I've also been searching the net, but unfortunately found nothing. erpdude8 suggested I should email MS, so I can build hotfixes that would install on more than 1 particular 9x OS, because if using TargetWin9xVersion=4.10.2222 [example], the patch will only install on 98SE, but not on 98FE. To make it install on 98FE [but not on 98SE], this line must be TargetWin9xVersion=4.10.1998 As far as I can tell TargetWin9xVersion= [or TargetNTVersion=] must have full OS build in this form: x.x.xxxx or x.xx.xxxx otherwise won't work. If using TargetWin9xVersion=0 the patch won't install on any 9x OS. Similarly, if using TargetNTVersion=0 the patch won't install on any NTx OS. U can combine these 2 lines by adding 1 of each in your SED file, but u can't use more than 1 of each to specify multiple OSes. BTW: Newest versions of IEXPRESS.EXE, MAKECAB.EXE + WEXTRACT.EXE [the ones I'm using] are from XP SP2. They work for 9x/ME patches too. I believe 2003 Server also has these files, but haven't tried. The SED file you mention: http://www.lv.kernel.org/pub/recommended/l...tnew/latnet.sed is actually taken from NT Option Pack: http://www.gpick.net/sbr/asp/page103.asp respectively from this CAB file [right-click to save it]: ftp://tiger.gpick.com/NTOptionPack/windows95/rasics.cab SED = Self Extraction Directive CAB SDK + IEAK: http://www.mdgx.com/add.htm#DEV

These are the new URLs for UPDATE.SYS for both 98SE + ME, this time with installers, no need to copy them manually to %windir%\system32\drivers anymore, also posted here: http://www.msfn.org/board/?showtopic=46581 and here: http://www.mdgx.com/web.htm * Unofficial Windows ME Updated CPU Microcode UPDATE.SYS build 4.90.3001 Fix includes most current Intel CPUs: http://www.msfn.org/board/?showtopic=44388 Direct download [166 KB, English]: http://www.mdgx.com/files/MEUPDSYS.EXE * Unofficial Windows 98 SE Updated CPU Microcode UPDATE.SYS build 4.10.2223 Fix includes most current Intel CPUs: http://www.msfn.org/board/?showtopic=44388 Direct download [139 KB, English]: http://www.mdgx.com/files/98UPDSYS.EXE

I assume 77.72 are WHQL approved or candidate, but because MS doesn't support 9x/ME OSes anymore, they probably won't test them in these environments. If it is of any significance, 77.72 drivers for Windows 2000/XP are WHQL certified: http://www.nvidia.com/object/winxp_2k_77.72.html You can view the 77.72 PDF documents for more info: ftp://download.nvidia.com/Windows/77.72/ FYI: If using Windows XP, have an SLI compatible PCI Express mobo *and* 2 GeForce 6600 or 6800 series PCIx video cards in SLI, 77.72 drivers enable SLI mode even without the bridge device that physically connects the 2 cards. Or just get a new GeForce 7800 GTX if u have $600 to spare. Edit: Forget about NVidia PureVideo, it's 30 days trial, after which u have to pay for it. Bummer.

They did release MSXML3 SP5 a while back, but they must have made some changes [?] to the 6-23-2005 (re)release. The documentation doesn't specify what they changed, and guess what, the 2 files [old + new] are identical bit by bit.

Good news. If u want to see your boot logo [even if animated] from within Windows, get the XrX logo screen saver [shareware]: http://www.xrx.ca/logoutils/index.htm#Saver Hope this helps.

Hi tk323, and welcome to MSFN forums.Sounds like you have been using some other program to modify security settings. 98SE2ME does not touch security settings. To properly use 98SE2ME, please read READ1ST.TXT before replacing any files: READ1ST.TXT and also see the list of system files which should *never* be replaced: http://www.mdgx.com/98-5.htm#NEVER That's a big no-no: WINOA386.MOD should *not* be replaced. The only version that works with Windows 98 SE is the 1 that installs from the 98 SE setup CD [build 4.10.2222]. If u do, DOS box mode will be either disabled or messed up, and there is a chance your OS will lock up. I have a bunch of DOS tricks + guides at my site. Please see this page which contains the entire list: http://www.mdgx.com/newtip.htm U can find more info in these text files: MEMORY.TXT, MYTIPS95.TXT, REGIONS.TXT, EMM386.TXT, all part of W95-11D.EXE [freeware for non profit use]: http://www.mdgx.com/95.htm All online tips are also included in the text files from W95-11D.EXE if u wish to read offline. It's a lot of reading, but u may find what u need. Complete list of Registry keys + values for security permissions: http://www.mdgx.com/newtip9.htm#RESTRICT System + Registry tweakers [99.99% free(ware)]: http://www.mdgx.com/toy.htm#SYS Hope this helps. And thanks a bunch for your kind appreciation.