loblo

You're not running Potplayer on Windows98/ME or are you? Reason I am asking is that you operating system seems to be 2003 and that the only gripe I have with PotPlayer on Windows ME is that I can't access any configuration page in it aside from the initial one and that your screenshot shows a page I can't access.

Since KernelEx development has stalled and that I am no progammer and that I was keen on running certain applications that don't run even with KernelEx, I embarked into some experiments involving hexing functions neither present in in Windows 98/Me nor catered for by KernelEX for other ones present in Windows 98/ME and I can report some interesting successes: ActivateActCtx -> SetLastError CreateActCtxW -> SetLastError DeactivateActCtx -> SetLastError FindActCtxSectionStringW -> SetLastError InitializeSListHead -> SetLastError InterlockedFlushSList -> SetLastError InterlockedPopEntrySList -> SetLastError InterlockedPushEntrySList -> SetLastError QueryDepthSList -> SetLastError ReleaseActCtx -> SetLastError It also seems to work for: CreateTimerQueue -> SetLastError CreateTimerQueueTimer -> SetLastError DecodePointer -> SetLastError DeleteTimerQueue -> SetLastError DeleteTimerQueueTimer -> SetLastError EncodePointer -> SetLastError But those are already catered for by KernelEx but when I started those experiments I didn't figure out they were. HeapQueryInformation -> SetLastError also seems to work but only when the function HeapSetInformation isn't also required, and for example you can make the latest FFDShow Tryout clsid build from Sourceforge work by merely replacing the string HeapQueryInformation by the string SetLastError in the file ffdshow.ax with an hex editor. http://sourceforge.net/projects/ffdshow-tryout/files/SVN%20builds%20by%20clsid/generic%20builds/ffdshow_rev3984_20110922_clsid.exe/download According to the above rules I have hexed both msvcr100.dll and msvcp100.dll and I use them to succesfully run without issues the latest Luminance HDR build which relies on them: Hacked MSVCR100 and MSVCP100: http://www.mediafire.com/?49bc54r28b94w0x Luminance HDR 2.1.0: http://sourceforge.net/projects/qtpfsgui/files/luminance/2.1.0/Luminance-HDR-Win32-SETUP-v2.1.0.exe/download No guarantee those tricks will work on everything as they must be ugly as hell but it's working very well on quite a few things I now have tried them on so i thought I'd share that with everyone. Cheers

Put Foxit in Win2K compatibility mode and you'll have readable bookmarks.

Your monitor might well be the cause then, perhaps you should try to connect another one more standard if you've got got one and see how it fares. Anyway good luck with sorting this out.

Professional audio with onboard AC97... You are joking, right? Because that's what you are showing us if I am not mistaken. A windows 98 system with an M-Audio 2496 or one of the M-Audio Delta series will have sound playback and recording quality leagues above a Windows XP/Vista/7 system with onboard AC97 chip or latest Creative Labs card...

You've got everything you need to get started in the post I wrote above, if you don't understand something or need more details, then ask and someone will answer you. As for the rest of what you wrote in your last post, yeah I think resetting the BIOS to default settings is certainly something to try. Btw, are you sure you had chipset drivers installed on this board in the past? I am not aware there are any Win 9x compatible drivers in existence for nForce 4 boards. Also, try to boot your system with the minimum possible hardware, eg, motherboard, graphic card, 1 RAM stick and the boot drive only and making sure everything is properly connected and see if the problem is still there.

I can think about three possible things that may slow down boot time considerably, faulty hardware, not properly installed, wrong, corrupted or conflicting drivers or boot drive with a bunch of very slow sectors where files required for boot are located. By the looks of it, it seems more likely it is a driver issue and you should fiddle around to try to get those exclamation marks to go away in the device manager. Also, enabling boot log and analyzing this with boot log analyzer might prove useful to figure out what's going on.. http://www.softpedia.com/get/System/System-Miscellaneous/Boot-Log-Analyzer.shtml You should be able to rule out faulty hardware if successfully booting from a live XP or Linux CD at acceptable speed. As for possible slow sectors you may want to test your drive with Victoria, either with the DOS version from some emergency/rescue boot CD or the Windows version from within Windows (unlike stated in the link it runs on Win 98, it just cannot use API mode but PIO mode only). http://www.x-drivers.com/catalog/benchmarking/hdd_ssd_flash/companies/hdd-911/models/victoria/10903.html

Perhaps but I don't think those you specifically mention should be an issue. Anyway, thanks to TmEE we know that the latest Flash 10 should run on your T-Bred Athlon so it's got to be something else than a CPU issue. Perhaps you could try to see if the standalone Flash 10.3 projector runs on your system and if it doesn't, inspect it with Dependency Walker, including profiling it, as to perhaps get a clue why it doesn't work. http://download.macromedia.com/pub/flashplayer/updaters/10/flashplayer_10_sa.exe http://www.dependencywalker.com/depends22_x86.zip You'll find a standalone Flash 9 projector in the archive below should you want to test it with dependency walker as well to see the eventual differences with the Flash 10 one. http://fpdownload.macromedia.com/get/flashplayer/installers/archive/fp9r280_plus_archive.zip Not sure all that Flash discussion has anything to do with KernelEx btw, and perhaps it should be moved to the other thread, your call DenCorso.

Six months ago the hardware requirements for Flash 10.1 were: Today the requirements for Flash 10.3 are: This most certainly means that a CPU supporting SSE2 instructions is now mandatory for running the latest Flash 10 builds whereas the earliest ones didn't even require CPUs having SSE support, Athlon 600Mhz having only MMX and 3DNow. I think you've got to find the most recent possible Flash 10 compatible with your CPUs on OldApps, FileHippo or any other similar website. http://www.oldapps.com/flash_player.php http://www.filehippo.com/download_flashplayer_firefox/ I might be wrong though but you'd better try that first and then report whether you can run earlier Flash 10 versions or not.

What you experience is typical of FAT corruption and it's got nothing to do with installing KernelEx IMO since it happens only on one partition. Scandisk and/or Norton Disk Doctor are the tools you need to run to fix this but I suggest you copy all that is valid onto another drive/partition before you do so.

Cool, thanks.

I've just installed a 400GB Maxtor hard drive I bought last year for £1 from a guy who sometimes comes to my local market to sell bits and bobs. It seems to be in perfect working condition.

Sounds kind of interesting but unfortunately: May I suggest you use MediaFire which is in my experience very nice and always promptly delivers.

What matters most IMO is how good your soundcard DAC is, if it's crap even the best speakers in the world won't make it sound any good.

Of course not. http://msdn.microsoft.com/en-us/library/ee416769(v=VS.85).aspx

It's because you removed IE I guess. Perhaps you can fix it if you get shlwapi.dll from IE6 and register it in your system with regsvr32.

You're having some odd problems dude.

I can't say I had any problems with my ME system (2GB of RAM and an XFX 7800 GS 256MB) which required it so far but this card plus the 2GB of OCZ RAM I have just bought on eBay to push the system to 4GB makes the purchase of this patch compulsory now.

I have no issues here with Firefox 3.5.19 and JRE 6u24.

Resurrecting that topic as it seems it's the one in which the 7950 GT is the most discussed. OK so I bought a second hand XFX 7950 GT 512MB on eBay for £62 last week and received it earlier today and can confirm what everyone knows already, it doesn't work properly on an unpatched Windows ME system. The best I could get, after it was successfully recognized by Windows and the unofficial nVidia drivers installed, was booting into a system at 16 colors at 640x 480 resolution with device manager listing the expected nVidia driver files and assessing the device as correctly installed and without problems. None of the nVidia helper apps and dlls were loading and I was unable to get even in 256 color mode at 800x600 despite my fiddling with a number of settings. Time to buy that RAM patch from rloew I guess.

I could open 50 DOS boxes (command.com) before getting the "not enough memory" error message and was unable to launch any more of them but was still able to launch more Win32 apps, albeit not too many as my USER resources where then too low to carry on. Thanks for the tips about safe mode but I never go into safe mode, whatever maintenance I need to do on the system drive I do it from a live CD.

In space no one can hear you scream.

Ok, I think I can say that the problem was down to that gearaspi.vxd since the issue has not reoccured a single time even though I have now increased the Vcache value to 512MB (524288) while keeping an AGP aperture of 256MB. Why do you recommend a Vcache value of 384MB if I may ask? I have seen it mentioned here and there but without understanding what issue exactly it meant to avoid. I don't seem to have any issues with 512MB here.

That's the only known workaround I am afraid and I did mention it in another thread (without going in such great details though). I think it's worth mentioning that, using the template you provided, one can easily create other entries for other suitable applications to appear in the Opera "Open With" menu.

Unless I am wrong of course, the AGP aperture value is the amount of system RAM that is allowed to be used as a (slower) substitute for video RAM in case applications (3D games mostly) need more video memory than the graphic card provides so that if I was happy with with say 128MB of Video RAM + 128MB of AGP aperture, I'll have more than enough of AGP aperture with 32MB when using a 256MB card for running the same applications.