jimmsta

Didn't Intel just release their video drivers as opensource for linux? here it is: http://www.intellinuxgraphics.org/ This driver supports all intel graphics chipsets, going back to the i810, and up to the new 965G. I think this should suffice as documentation for you. Let me know if this helps you out.

Well, did you purchase XP, or did you install a pirated version? If the former, then try out Microsoft's diagnostics tool for WGA notification problems: http://www.microsoft.com/genuine/diag/ Otherwise, BUY A COPY OF WINDOWS. There's no LEGAL way around it.

MDGx made a 98SE 2 XP patcher, here: http://www.mdgx.com/98-5.htm#MP9 This includes WMP9, as well as a bunch of other unrelated files that have been tested on 98SE, and are from XP.

Then there's those of us that tend to hope and think that bits and pieces of ReactOS and WINE can be used in older Windows OS's. I'm 20, and I still examine these possibilities. I also attempted getting the skinning engine from early builds of Whistler to work in Windows 2000. I'm a dreamer, I guess. ;P

If you want I've translated SP for Windows98SE/ME, Native Usb, Revolution Pack, 98SE2XP, 98SEMP10 in italian. Certainly - PM me links to where I can download them all.

now I have. Check out the introductions.

Yes, indeed I was. I'm a contributor to classicbeta.com's wiki as well.

v4.1 has files for all English versions of Windows 98 FE/SE/Me. I'm working to get a multilingual version out, as well as getting all the latest patches together into... a patch. All you need to download is v4.1, and you'll be set with the patches for all Win9x OS's (that is, all 98+ versions, there aren't any 95 patches).

I have an Athlon X2 3800+, and have run Win98SE on it... and of course, to my dismay, it does not see two processors. NT 4 would probably see them, because it was designed with SMP cpu's in mind. Since Win9x is dos-based, of which, as far as I know does not support more than 1 cpu.... If you wanted to write a driver to support the second core, you may have to write a patch for IO.SYS so that it fully initializes the second core, and assigns resources to it. I don't even think FreeDOS supports dual core cpu's yet. It's just not needed. Win9x's kernel would need to be SMP-aware, and be able to fully multitask on multiple processors in order to utilize its full potential. (Which, as far as I know, it isn't designed to do this). This may be a pipe dream. There's too much that would need patching, and modding. Although I do wonder about WinME...

It's been about a month since the last update, so here goes... I'm thinking about splitting the pack up into two separate options - Unofficial Service Packs, and an Unofficial Patches/Addons compilation. Reason: To reduce size of package, and offer more of a choice for users of the package. Of course, v4.2 will be released as a full package, onto MajorGeeks.com and various other hosting options. This way, I can make a ~160MB USP version, and a ~ 90MB Unofficial Patches/Addons version. Both of which will be able to be put together to form the complete package. I'm also looking at replacing the Autorun app with a "TheOpenCD"-style replacement, which utilizes the Kameleon browser, and is completely OpenSource, and fully customizable... also, probably faster to use on older systems. The current Autorun takes a while on older hardware to initialize. I'm actively working on this project. I'm also working hard on my other compilation, BHT (v2.6/???).

http://www.yamipod.com/main/modules/home/ FREEWARE

At the very least, MCE should support Peer to Peer workgroups. I cannot be the only person who wants to store their media on another system, and stream it from there. At the moment, I'm using dhdan's script, which works ok for now.

I've tested it a few times... it doesn't work. ;( This isn't useful... Win MCE 2005 IS Windows XP Pro underneath it all. There's got to be a way to get everything back to normal.

About the only thing you could do then, is get a PCI IDE controller that has 137GB+ support (LBA 48bit). This patch is designed for systems where this hurtle is no longer an issue, but the OS's native support for LBA 48-bit is non-existant, hence the issue at hand.

as far as I can tell, the majority of the files are only stubbs, and still require the diskettes for win 3.1 support, and the CD for creation of bootable disks with all utilities. Keep in mind that Win98 boot disks are available freely, and contain nearly the same binaries found in this archive. I'll keep this up until a mod removes it, or asks me to.

Ah, that looks like it works. I'll test it out in a sec.

Exactly. I took an afternoon navigating the site and trying to find these files. I have no idea what the strings of text on my screen said, except for DOS and 7.1 ... I got lucky, I guess... Here's the creator: http://rapidshare.de/files/30030866/DOS71DL.zip I also have the DOS7.1 ISO file, but it might be deemed illegal by the board. If a mod or admin wishes to remove the file from this post, please do so. I don't want to be violating any rules.

That's already set - it doesn't seem to work properly under MCE.

I've managed to find the creation tools used by the guys who created the unofficial DOS 7.1 distribution that was on the net for free for a while... I'll release it here if it's deemed OK. As far as I can tell, it just creates the boot disks from the contents of the Win98SE cd. It can also create DOS 8.0 diskettes, but according to the Readme, it's somewhat buggy in this mode (WinME CD used). All the archive consists of is a batch file, and diskette creation utilities. I've also relocated the DOS 7.1 ISO, which was floating around the net for a while, but has been removed almost entirely. Again, I'll only post these if it's deemed OK to post. I don't want to encounter any legality problems.

I've got Media Center 2005 OEM installed, with all the latest patches. Since underneath it all, it's XP Pro, I'd love to know how, if possible, to re-connect the system with password-protected network drives on reboot. At the current moment, I'm stuck with re-connecting them manually, which is a hassle. I figure that there's probably a way to do so with a logon script. If it matters, I'm using a linux-based file server, running Samba 3.0.17a, with packet encryption enabled. Everything works normally, it's just the re-connection issue that doesn't please me.

So, now the question is: How do we create them? Is there a way, or an advantage to creating a VxD as opposed to, say, an external program loaded at startup? It seems to me that VxD's are supposed to be Services running on the Win9x platform.In which case, is there a way to implement more functionality into NTKern.VxD, or what? What I'm trying to get at here, is... would it make more sense to hack ntkern.VxD instead of kernel32.dll, for the Kernel Update Project? NTKern is supposed to be some sort of supporting library/service for NT-specific system calls... which I take to mean that it would be the best place to put updated functionality, instead of kernel32.dll. I'm probably wrong, of course. I'd love to know the exact boot order of Win9x. (NT's bootorder wikipedia page is incredibly informative: http://en.wikipedia.org/wiki/Windows_NT_Startup_Process )

Diantz may be using an earlier version of the CAB compression spec. "21xx" is found throughout diantz, while makecab has "22xx" (hexadecimal values in file). The files are nearly identical. There's a small section of data within the exe that is approx 16bytes, which is different between the two files. This may be the algorithm used. I have no idea though, as I'm not a real hacker/programmer...

I'm no artist, but I took a swing at it... here's my current work in progress. (see attached).

Earlier, I was in the midst of responding, when I noticed my "m" and "n" keys weren't working... - Looks like I'll be RMA'ing my somewhat new Logitech G15 keyboard. For now, I've got an older logitech wireless keyboard that tends to lag every once in a while, but is overall, too small for my hands/fingers.... And now I get to play with this neat tool. I like the fact that a slipstream app and a de-integrator have been released in the same day, which both offer great features to those of us that still use Win9x. (I use it for testing older systems, and drop ghost images of it on spare hard drives for testing). B)

You... do realize that this is an experimental patch, right? Problems like this are possibly going to occur. Also, what options did you use? I see you used Option 8, but what came first? I'm not going to lie, I've had problems when updating old installs of 98SE2Me to newer versions, and have had to re-image my virtual machines.