oerg866

I'm sorry, you're telling me I should read 23 pages of discussion instead of asking for a simple two-line summary for what's the latest browsers I can run and what I need to install for them? I read most of the thread and I have absolutely no idea what's going on q.q PS: Not a fan of cliché philosophy quotes.

Hello, i'm sorry to ask this but can someone actually summarize what is and what isn't possible on Windows 98 as of now? It's never quite understandable from pages and pages of context-based chatter What can I and can't I run?

Hello everyone, I am having quite some trouble on my Q6600-based machine which I want to get Windows NT running on. It just won't recognize more than two cores, no matter what I do. To install it I have to limit CPUID, I install SP6, and then remove the limit and it recognizes only "2 processors". I'm completely stumped. Any input is appreciated. I tried NT4 Workstation, Server and Terminal Server edition, to no avail. (Also SP6 slipstreamed versions of these) All the best, Eric

You can use the NDIS2 driver.

Hi all, did anyone ever figure out how to get Win9x running on the later nforce chipsets? I know NF4 runs 98 very nicely but I can't get it to boot on an NF5 board I have (more specifically, Abit AN52V)... Cheers.

No I mean hardware components. If you do full hardware redetection (like 2nd setup stage does) or single device redetection, some system devices will not be recognized properly. It might be reproduceable by deleting the PS/2 mouse or Floppy disk controller devices from device manager and rebooting. With old SETUPX.DLL those will be reinstalled normally, with the new one there will be yellow exclamation marks all over the place Cheers!

Hello PROBLEMCHYLD SetupX.DLL must be reverted to Win98SE version. Hardware detection fails to properly install system components (yellow exclamation marks, "BIOS did not declare resources properly") with the new one. It turned out that only the updated COMMCTRL.DLL was needed to fix the large driver DB problem, so it's not really a loss.

Your suggestion to disable kex for wmpshell.dll has done the trick so far... If I get the time I'll do it more thoroughly as you suggested. Thanks a ton for your time and engagement!

I'm sorry, my lack of sleep might be playing tricks on me, but what do you mean by "full error text details"? Do you mean this? EXPLORER caused an invalid page fault inmodule UNICOWS.DLL at 016f:7f2daf19.Registers:EAX=ffffffff CS=016f EIP=7f2daf19 EFLGS=00010286EBX=00000000 SS=0177 ESP=01bde438 EBP=01bde438ECX=81e0d404 DS=0177 ESI=01bdeee4 FS=350fEDX=00000000 ES=0177 EDI=000000a7 GS=24b6Bytes at CS:EIP:66 8b 08 40 40 66 85 c9 75 f6 2b 45 08 d1 f8 48 Stack dump:01bdee70 7f2f879b ffffffff 4548532f 4c484c4c 39565f50 616c5020 442f2079 4f617461 63656a62 454e3a74 45504546 41424648 41414141 414f4141 41414142

I've installed softice in the VM now and this is the location of the crash and the call stack. EDIT: Forgot to configure it properly, gonna post a better shot in a bit EDIT2: I remember this problem from KEX 2015.8. This one is KEX 2015.9 from the installer posted last page. Perhaps this is more helpful? 100% reproducable: Install MPlayer 9.0, SP3 and KEX 2015.9 in any order, double click media file. -> Crash

It again seems to happen only with SP3 and MP9 installed... Some things are a bit odd with this setup, bear with me as I create some reproducable tests

Found another bug. After installing kernelex, you cannot double click any media files anymore.

Ohhhh!!! That's pretty cool. I must have been blind. Alrighty, I'll check that out.

Doesn't work for me. SP3 3.46 + KEX 2015.9 = death.

Did you remember to take the POST-INSTALL commctrl.dll? You can see it via the size difference (~45kb vs. ~160kb) It's in PRECOPY1.CAB as kommctrl.dll (copy & rename)

So far no issues, but it will of course be put through extended testing through my integrated ISO which I unfortunately can only share privately to avoid breaking forum rules / legal issues. On a sidenote I noticed too that the stock COMMCTRL version is 4.10.1998. Maybe they forgot to include the new one when releasing 98SE?

Could not reproduce this on my machine

Hello, The 2MB driver database limit has been eliminated. All you have to do is replace SETUPX.DLL and COMMCTRL.DLL with their Windows ME variants. The problem did not seem to be that it had problems READING a big driver database, but something faulty was generated in those unknown fields in the header causing it to have issues later on. After replacing the DLLs, it still would crash reading the DRVIDX.BIN file from before. Generating it from scratch, it had no problem even with 3 MBs worth of information Kind of disappointing fix, considering the hours I've wasted debugging this with SoftICE and IDA (It always seemed like some sort of issue with COMMCTRL's implementation of dynamic pointer arrays being buggy, but considering the latest findings that seems to have been a side effect??).... But I can finally lay this nightmare to rest

Hm, that's odd. It is working for me with a SoundBlaster Live! card. The package shouldn't require kernelex at all. Try turning off kernelex and see if it works then maybe? Cheers.

You can use Outlook's online interface

The regular skype verisons prior to 6.2 do not allow you to log in. This one does. I should clarify: Vilko managed to reverse engineer and modify the older skype versions to the point where they would run and connect - but not on Windows 98. I made necessary changes for Windows 98 such as removing the portable launcher that doesn't even work with kernelex and packaging it.

Skype 3.8.0.188 for Windows 98 / MEInstaller package created by Oerg866(C) Skype Technologies SA(C) Microsoft CorporationAll rights belong to Microsoft Corporation.Original modified Skype 3.8 version by VilkoPLEASE NOTE: After starting Skype for the first time, it may take a few minutes to load the contact list and you may get an error message about your internet connection. This is normal, don't worry.This package was created to give people a chance to connect to the Skype network from old Operating Systems like Windows 98, 98SE and ME.It does not intend to undermine Microsoft Corporation's authority over their Skype service and exists purely for experimental and nostalgic purposes.tl;dr please don't sue me ;_;DISCLAIMER: I'M NOT RESPONSIBLE FOR ANY DAMAGES TO YOUR COMPUTER(S) AND/OR SKYPE ACCOUNT(S) AND ANY OTHER THINGS THAT GO WRONGtl;dr please don't sue me either ;_;Download

I just found this: http://www.msfn.org/board/topic/170950-windows-2000-on-haswell/page-3 this is the same problem as with Windows 2000!

Okay, as it turns out, Windows NT refuses to boot if I have anything other than the standard hal.dll installed. If I run a MPS kernel with either uniprocessor or multiprocessor support it won't boot. Cheers

Those > are to symbolize what happened here. I did those things, I wanted to test a few DOS drivers so I grabbed a hard disk from my stash and the IDE controller, a NT4 installation was already on it and I didn't pay attention only to find a fully booted NT4. Strange, isn't it? But I'm content