Leaderboard

I've found out about it by reading a thread on VOGONS, where a user mentioned his RAM patch for Windows 98. While I never used his patches, being an XP user, it is a big loss for the entire community and the people who still RDD on Windows 98. Here's his obituary: https://kraussfuneralhome.com/tribute/details/858/Rudolph-Loew/obituary.html Rest in peace, @rloew. He was 67 years old and passed away the 11th of this month.

As an addition to what TrevMUN said, if youre going to get any BSOD related to acpi.sys (even if you don't, it is still worth replacing the file), make sure you slipstream the relevant acpi.sys mod, which can be found here. The link also contains a generic USB 3.0 driver. Here are the instructions on replacing this file in the installation medium.

If you can go with Team Red I'd recommend it from the security angle; as I understand it, AMD is not as vulnerable to Spectre/Meltdown as Intel's CPUs are. My own options were pretty limited with XP64 (not that I'm complaining, the new Broadwell-E setup is a major upgrade from my Kentsfield) but you should have better luck with XP32. From this thread I had posted observations made by people at Guru3D as to what post-EOL hardware is still XP-friendly. Though it's a Team Blue option, GIGABYTE's Z370s are observed to work without ACPI and that, generally, XP has been tested and found to work on the Z370s. This one's going for $120, and you should be able to find a CPU in the LGA1151 socket that would fit your budget. From that thread, @Dietmar found concrete evidence that XP can work on AMD's Ryzen line. Specifically, ASRock's Fatal1ty AB350 Gaming K4 motherboard, with a little tweaking. From what I understand AMD worked in some backward/forward compatibility with the Ryzen line and so you can use newer-generation Ryzen CPUs with the older sockets to an extent. You'd need to verify whether that's the case for that socket though.

Rest in peace, Legend Rloew. You were a Windows 9x god. For historical purposes, here is a recent archive of his web site, dated 12th August 2019. http://web.archive.org/web/20190812081523/http://rloew.x10host.com/

This is really sad, I recognized that name anywhere when it came to 9x enhancements. Rest in peace.

I've bought his Windows 9x AHCI driver, which works wonderfully. I've had many discussions with him on this very forum, I am still, to this day, thoroughly impressed by his work and knowledge. Rest In Peace Rudolph, you will be remembered.

I don't know if MSVC SSE build will work or not. GCC(MinGW) build may work. https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Cross_Compile_Mozilla_for_Mingw32$revision/1019972

SeaMonkey 2.48 (Firefox 51) for SSE http://forums.mozillazine.org/viewtopic.php?f=3&t=3026176&sid=1eac87b375d1e3f75fc1ea9c1bbc2d08&start=30 http://matejhorvat.si/en/unfiled/nosse2.htm

I changed the screen in my Asus netbook as it was fitted with a highly reflective one which was like looking in a mirror! The matt finish one I replaced it with is much better. It wasn't too difficult to do, but obviously this varies a lot between different units. Its native resolution is 1024x600, which means that Windows 8.1 apps will not open as they have to have at least 768 vertical resolution to work. I used a registry hack to enable me to switch the resolution to 1024x768 to use the apps, but in this mode the display is not only blurry, but also compressed vertically so everything is distorted. That is preferable IMO to the image being the right shape but vertically cropped! This is tolerable for temporary use to read the mail or news app, but hardly ideal, and is a good example of the undesirability of using any display at anything other than its native resolution.

My WimScript.ini is more or less the build in list that imagex.exe has. Microsoft is not using the WimBootCompress.ini to create the WIM they release. Adding to many entries could slow down the process as every filter has to be checked against every single file.

there is a newer servicing stack update (SSU) for Server 2008 - KB4517134. MS support article 4517134 says that this new update supersedes/replaces KB4493730.

This is extremely sad news indeed, I'm surprised more haven't replied to this thread already. He was certainly a genius when it came to figuring these things out. He'll always be a well respected developer and patron here. RIP rloew, we will all miss you. Thank you for all you've done for the diehard Win9x community.

No idea if this helps, it's just a pref for "dpi-scaling" Mozilla browsers, not the whole system.And am not sure if there's a difference between normal pagezoom and this dpi-faking. Anyway, perhaps worth a look as long as there's no easy solution for the whole system yet: https://www.ghacks.net/2013/06/24/firefox-22-0-find-out-what-is-new/ Pref: layout.css.devPixelsPerPx (String) 1.0 = use real resolution (everything looks sharp) -1 = automatic scaling (drove lots of people crazy when it became default and increased all image sizes, made them all fuzzy) Value can be smaller or greater as 1, in 0.05 steps, e.g. 0.8 or 1.25 or 1.5 etc. Since you want a HIGHER resolution, it means you want all elements SMALLER, that probably looks much less "fuzzy" as when increasing the size.

I was able to get UXP / Serpent to build ok for SSE only processors. Pic related! Thanks for your help :)

You can't invent pixels out of nowhere. What you are actually seeing is the maximum resolution of your screen, there's no way to increase it as every pixel physically correspond to an object on the screen that is charged electronically and displays a value between 16 and 235 (between 0 and 0.7 Volt) or 0 and 255 if it's full range of RGB which gives you what you see as an image. For instance, if you had a camera that was able to zoom enough you would see that when you are seeing white, each and every pixel is turned on with the maximum voltage available. You can basically see why you can't increase the resolution: there won't be enough pixels on your screen to fit it, so you would end up with a partially represented screen TL;DR parts of the elements of your desktop will fall out of your screen. - trick and attempt 1 If you are really willing to try, you can use the Windows scaling function to scale down desktop icons and text or in Firefox/Chromium to zoom out web pages. This won't give you more resolution, however it will make text and icons smaller and give you the feeling of having a higher resolution. - trick and attempt 2 Just like it's possible to encode images and video with a Frameserver, it must be possible to make a downscale of your desktop live. What I mean by that is that you will set the resolution very high and then you'll downscale the resulting signal down either via software or via hardware to fit the resolution of your screen. There are many resizing kernel like PointResize, Bilinear, Bicubic, Lanczos, Spline based resizers etc. I would personally suggest to use Spline64Resize or Lanczos. They are both very sharp, but spline is prone to create ringing on texts. This way you're definitely gonna make use of the space created by the new pixels, but you won't see them! What you'll see is rather an interpolation of them made by the resizing kernel you selected and it may look aliased or with ringing or even so mis-represented that it's impossible to read! If you wanna learn more about resizing kernel, check this out (beware, it requires at least a basic knowledge of linear algebra): http://avisynth.nl/index.php/Resampling Source: I'm a broadcast engineer you can find me on Doom9 (the international encoding forum) talking about... well... encoding all the time.

Kindlegen.exe (Free). for Atlantis Word Processor https://www.amazon.com/gp/feature.html?ie=UTF8&docId=1000765211 http://kindlegen.s3.amazonaws.com/kindlegen_win32_v2_9.zip Copy kindelgen.exe in %programfiles%\Atlantis and now you can save documents in .epub and .mobi

The 2nd post was not only spam; it was also deceptive: the link claiming to go to 123[dot]hp[dot]com actually goes to [...]! @dencorso, could you please remove the offending post (or at least "neuter" the deceptive link)? Thanks!

Extended v 3.0e was released yesterday. There are some bug fix. * installer is fixed on any rapid storage fails to patch options. * SHFSet.exe manages more resource for localize. * XP version Device Manager problem fixed. > How do i upgrade from 3.0c to 3.0d? Do i have to uninstall it first then reinstall it? I recommended to uninstall and you can overwrite it. But if you have installed same version overwrite before , don't uninstall it and you should overwrite it.

Try running the setup with the: /p i switch, note the space between p and i

EDIT: This method has recently obtained noticeable popularity, and seeing the troubles of other users and more confusing methods on places such as YouTube, I thought it might be a good idea to revise and clarify this a little. Despite the fact that the damage has already been done, perhaps people who come across this topic can be helped. HOW TO FIX ROBLOX ON WINDOWS XP, VISTA, SERVER 2003, and SERVER 2008. I realize this topic is a few days old, but it is now August 30th which means we can see what this actually means. I'm actually quite surprised that they have continued support for this long, but like most companies, have finally fallen to the wrath of Microsoft. Anyway, I have not really played Roblox in years, but I decided to see what could be done for XP and Vista players now that support has officially ended. Open launching a game we greeted with this error message. This is the same usual crap that is endlessly spewed about and of course depends on your definition of 'secure'. I wouldn't really consider the inescapable mass data collection in Windows 10 'secure' either. Moving past this, download your favorite Hex editor. I choose Hex Workshop, but it really does not matter. You can find Roblox's installation folder by simply right-clicking on the Roblox shortcut and selecting 'Find target' (On Vista, it is called "open file location"). On my installation it was installed in the following: If for some reason you cannot find Roblox's installation directory, simply re-download the RobloxPlayerLauncher by clicking the "Download and install Roblox" website prompt after the client gives you the unsupported error. In fact, I recommend this even if you can find the directory because some users reported problems while editing the launcher found within the directory. Open your Hex Editor. (The following instructions will assume you have HexWorkshop, but it should be a similar process no matter what you use. Open 'RobloxLauncher.exe' in your Hex Editor. You can simply drag-and-drop the RobloxPlayerLauncher into your editor, or click the open file button and find it yourself (wherever you saved the launcher to, for example: Downloads). Next, press ctrl key and then 'F' You should see a search dialog box appear. There should be an option for what you want to search for, select "text string" in the drop down. Search for the text string "XpVistaDeprecationLevel". It should now be highlighted. Next, right click on the selection and press 'Fill'. There should be a prompt asking what you want to replace the data with. Simply type '0' into the field. When your done it should become something like this: Now try launching RobloxPlayer again... The client should have updated successfully, now go to the website and play a game: Roblox is now once again working on XP, Server 2003, 2008, and Vista! I'm not sure how long this will work for, if what they say is true, dependencies will become a problematic in the future. Hope this helps you and other players who are having this same problem!

its more sad in Vista's case in my opinion because Vista was the os that changed windows it introduced desktop manager, wddm driver support and a new memory management model also Windows Vista and Windows 7 are far more similar under the hood than Vista and XP are

Since you're running 64-bit Vista, be sure to go to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO and delete the 'OSVersion' values in the 'TLS1.1' and 'TLS1.2' keys (folders).