Leaderboard

@dencorso Make that two, for I use Windows and MacOS interchangeably all the time You just never hear about it from me, because FAT32 is enough for most of my file copying needs, and read-only NTFS is adequate for the rest. Plus, there exists a read-only HFS+ driver for Windows XP and up which can help too, and one doesn't need to be running Windows on a Mac to enjoy it, for all you need to do is install two .sys files (four if installing on x64) plus a few registry entries to enable it on any PC running a supported Windows version. Link c

Except IE9 on vista x64. It needs some extra procedures to install. On x86 there is no problem

Yes but you need to properly update KernelEx which is not very straightforward. https://msfn.org/board/topic/175276-kernelex-unified-topics-links-index-thread/

SHA2 updates disable Windows Update, since they bump the build number to 6003 Yes, you open command prompt with admin rights, then run the commands. I recommend you put the updates in a path with no spaces, like "C:\Updates", just so it's easier to run the commands.

Change those bytes for steam.exe, steam.dll, and steamservice.dll

No. You'll need to use the WD Quick Formatter to reformat the 4 TB WD external USB HDD with 4 kiB sectors (= Windows XP compatibility option) so that XP will be able to use it. Afterwards you can format the this as a single primary partition with NTFS, exFAT (after installing WindowsXP-KB955704-x86-ENU, of course) or FAT32 (but for FAT32 you'd need Ridgecrop Consultants' FAT32Format and, of course, it doesn't support files bigger than 4 GiB). Because, nowadays, most of the ca. 1% of all PC users who keep on XP (a) don't have nor want Macintoshes and (b) have no reason at all to reformat the partition as exFAT, since the WD Quick Formatter yields the Windows XP compatible partition as NTFS, which is usually perfect to be used with XP+ and all PC unixes (linux/BSD/illumos). Or, in other words, you must be the first human being alive to face the type of problem you described, IMHO.

Strange. I typed the full hex string into HxD's search and got a match. And you can find that page here: http://web.archive.org/web/20030605104342/http://www.geocities.com/thejjoelc/XPbootcolors.html But I'm not sure if it would work well with x64 executables or Vista itself (for one thing, boot.ini has been deprecated). If you only need to change the colour of the progress bar, you only really need to change the appropriate hex values. As for my winload/ntoskrnl combo, it appears that all a user will have to do is bcdedit /set nointegritychecks 1, then copy over my versions outside of the OS, or set up an alternative boot menu entry with my files renamed while the OS is running. My patched files are stable, but I need to test modified ntdlls.

I'm trying to set up Windows 98SE on a Thinkpad X61 and as I now gather is to be expected, I'm not getting any sound. This thread seems like the most promising thing I've seen anywhere, so I want to see if we can generalize this success a little. From what I understand at this point, though, every single audio device could potentially require unique troubleshooting. Is there any chance we can come up with some step-by-steps in this thread that allow people to do it themselves? My Thinkpad X61 has an Analog Devices AD1984 sound device running on Intel HDA (there's a datasheet for the AD1984 available here). Using the GENHDA16.INF deomsh posted on the first page of this thread, I've installed HDA2.DLL from HDADRV9J and added HDATSR.EXE to my autoexec. This seems to work okay. One of my unidentified PCI Cards in Device Manager becomes a High Definition Audio Controller and an HDA Sound playback option appears under Multimedia Properties. HDALOG.TXT and HDAcfg.ini are also generated and so is HDAICIN.TXT if HDAICOUT.HDA is present. See my attached files for what these look like on my system. I can open WAV files in mplayer or sndrec32 and they appear to play, but I get no sound. Not through the laptop's internal speaker or through the headphone jack. I think this is "The Sound of Silence" as deomsh calls it, so I tried changing the volume or playback widgets listed in the HDAcfg.ini. I don't really understand what I should be changing them to, though. According to the datasheet for the AD1984, I have Audio Output widgets on nodes $02 (S/PDIF DAC), $03 (DAC_0), and $04 (DAC_1). Are these what I want to put into HDAcfg.ini? Or do I actually want to use the "Pin Complexes," which are $11 (headphone jack), $12 (line out), and so on? Or something else altogether? I've also tried using INTELHDA.EXE from this post, which seems like it should be a super useful program if only I could understand it. At least it confirms most of the widget info from the datasheet and I can also use it to see that node $12 is my laptop's internal speakers and that node $11 sees headphones when I connect them. INTELHDA.EXE also suggests that maybe (?) there's another Audio Output on $01. So all I've been doing so far is just testing all sorts of combinations of these node values in the HDAcfg.ini, but I haven't come across anything that produces any sort of sound. I definitely don't actually know what I'm doing, though, and there's lots of combinations to try. Some advice about what these widgets are supposed to be and how to identify the right nodes from either a datasheet or the "widgets" tab from INTELHDA.EXE might be useful and allow more people to troubleshoot their setups. One other oddity I've noticed on my system is that when I cold boot Windows, HDALOG.TXT shows nothing is returning and the CODEC section of HDAcfg.ini is all zeroes, but if I "Restart in MS-DOS mode" and then return to Windows using an EXIT or WIN command HDAcfg.ini does seem to populate correctly. The log and cfg files I'm attaching here are what I get after doing that. With a cold boot, HDAcfg.ini has CODEC BITMAP=00000011, CODEC Index=$1, and all the other CODEC lines are zeros. This seems to be some sort of failure, I think, right? I'm actually "cold booting" Windows 98SE from GRUB4DOS, so I don't know if that's part of the issue or what. Any advice or feedback would be much appreciated. It would be amazing to get sound working in my 98SE install, especially since it's otherwise working very well. HDALOG.TXT HDAcfg.ini HDAICIN.TXT

I sure do miss my window borders. Don't get me wrong, I love translucency, but to me the biggest improvement I've felt from Big Muscle's software is to be able to create compositing resources that include a visible border. There is no substitute for visually finding the window border for resizing, etc. I can't tell you how many times I've been frustrated by trying to grab the corner, no, inside the corner, no just outside the corner, only to have a window underneath jump up unexpectedly or something. -Noel

Sorry I was unable to relpy sooner. RLoew, You have done a great service keeping win ME(9X) alive with your ram patch, and various other programs. I think I speak for the community in general when I say, R.I.P, and your work will be sorely missed. Thank you for all your help, and rest well wherever you are now.

Yes, I would appreciate it too so it will be released when it is ready. Current status is that it does not work correctly yet. On the other side, I doubt that someone needs to upgrade to new builds immediately when it is released, especially when some needed software is not compatible with it.