Leaderboard

This is one of the worst threads I could think of to have pinned. Pinned threads are reserved for important information that generally affects everyone using the OS. If there was a crucial fix that applied to everyone or just about everyone, then it warrants a pin. But pinning a thread will not give it more attention. I don't even know what the original post said but even then, this is more of a per user basis issue and not a widespread problem. I mean, you don't even have much explanation about what's so slow about it or when it occurs so how does that help anyone?

No.

Below is my guide on how to convert some of the Chinese still present in 360Chrome. Also includes a few tweaks to reduce/eliminate privacy risks. I'll unfold the guide a little at a time over a few weekends or so and have inserted "placeholder" posts to keep them all at the top of the thread. I use the Russian Repack from here (version 13 build 2206) -- https://lrepacks.net/repaki-programm-dlya-interneta/182-360-extreme-explorer-amp-portable.html Run the "_Unpack Portable.cmd" and it will create a "360Chrome" folder - we will be modifying files inside that folder. You can always revert back to original by renaming folder and running "_Unpack Portable.cmd" again. Freebie software that you will need. Resource Hacker --- I prefer the portable ZIP at the bottom of here -- http://www.angusj.com/resourcehacker/ PeaZip --- I prefer the 32bit Portable version from here -- https://peazip.github.io/peazip-portable.html Notepad++ --- I prefer portable version 6.8.8 but newer versions work just as well -- https://sourceforge.net/projects/portableapps/files/Notepad%2B%2B Portable/ Chrome PAK Customizer -- I use v2.0, grab the chrome-pak.7z from here -- https://github.com/myfreeer/chrome-pak-customizer/releases HxD Hex Editor --- I use version 2.4.0.0 from here -- https://mh-nexus.de/en/hxd/

I tested on a VMware virtual machine. Windows 98 was patched with AutoPatcher. I got in the menus right away after copying SwiftShader 2.01's d3d9.dll in the game folder since there's no 3D support in the virtual machine on Windows 98. I was unable to load any map at this point, it crashed, the error message mentioned stack fault. To be even able to see the error message, I had to force the game to run in windowed mode, I could do it by setting appropriate option SwiftShader.ini, otherwise, the game appeared to have just closed. I ended up modifying the executable file by changing the value of SizeOfStackCommit in IMAGE_OPTIONAL_HEADER32 structure from 4096 to 65536. It's pretty easy with OllyDbg, open the executable, press Alt+M, at the top, there should be an entry that says "PE header" under Contains column and "CoD2SP_s" under Owner column, double-click it then in the window that opens, find SizeOfStackCommit, double-click it, type 65536 in (Un)signed field, confirm, right-click on SizeOfStackCommit->Edit->Copy to executable, OK the message prompt, right-click anywhere in the window that opens and click Save file... and save it under the different name. NoCD patched executable is probably needed for this as copy protected executables are harder to tamper with. Multiplayer executable (CoD2MP_s.exe) doesn't have any copy protection out-of-the-box. So CoD2 doesn't seem to have any mandatory reliance on any special APIs, so the OP's issue must be related to DirectX/drivers, given the error message. And my experience hints that Windows 98 may not actually be able to grow program's stack on its own when the need arises. It's possible to enable log file by adding +set logfile 1 at the end of the Target field on the Shortcut tab in the game shortcut's properties. The file console.log will appear in the main subfolder, though it's possible that it may not actually log anything if it's forced to bail out too early.

Introduction: As the title implies, this post serves as a guide for anyone potentially seeking to install and use Vista on the Intel Ivy Bridge platform. I felt there was a need to create this guide, because although getting full driver support for Vista under Ivy Bridge IS possible, it requires you to use certain motherboard(s) from the Sandy Bridge era to get USB 3.0 driver support for Vista. Intel HD 4000 Graphics drivers are also not so easy to obtain for Vista, so a link to them has been provided below. Choosing the right motherboard: With Ivy Bridge, Intel dropped Windows Vista (and XP) support from its USB 3.0 drivers, rendering XP/Vista support for the Ivy chipset incomplete. To work around this, you will need to find a motherboard from the Sandy Bridge era that supports Sandy AND Ivy Bridge CPUs. Almost all Sandy Bridge motherboards, except those with the Q65, Q67 or B65 chipsets, will support Ivy Bridge CPUs through a BIOS upgrade. A notable example of such a motherboard is the Asus P8Z68-V LX. This motherboard in particular has Asmedia USB 3.0 controllers, and Asmedia has excellent driver support for Windows Vista. Gigabyte also offers a number of boards that include third-party USB 3.0 chipsets, which support Vista. Be aware that you might have to purchase (or borrow from a friend/relative) a Sandy Bridge CPU to boot up your system for the first time if you are building from scratch, as the original BIOS version for these boards does not support the use of Ivy Bridge CPUs and will not allow you to boot the machine with an Ivy Bridge CPU without first updating your BIOS. For Ivy Bridge-E processors, the X79 chipset is fully supported on Windows Vista and you may choose any motherboard you like (the BIOS update situation still applies). If you do not care about or need USB 3.0, then you may choose any Ivy Bridge motherboard you like. Chipset drivers for Ivy Bridge do support Vista and can be downloaded here. I personally use the ASUS P8B75-M motherboard with Windows Vista Ultimate, and I find it to work well (Vista simply uses its generic USB 2.0 drivers for the USB 3.0 ports). Finding Intel HD 4000 Graphics drivers: You can download the Intel HD 4000 Graphics drivers here: 32 bit - 64 bit For some reason, Intel decided initially to not support Windows Vista with its HD 4000 graphics chipsets. However, it appears that they later decided to add in Windows Vista support, evidently via backporting Windows 7 drivers, since this installer claims that the drivers are for Windows 7 but doesn't mention Vista specifically. Despite this, the drivers work just fine in Windows Vista. I have studied the driver setup information (.inf) files and found that both desktop and mobile HD 4000 graphics chipsets are supported, so this driver should be able to be used with any Ivy Bridge graphics chipset under Windows Vista. That's it! No additional special steps are required, and you may install and use Vista normally with full driver support on the Ivy Bridge platform (arguably the best platform for XP/Vista). I hope this guide helped you!

Are you installing KernelXE lite over full KernelXE? That's definitely bound to cause problems cause BlackWingCat ntdll. Also, I plan on adding the newer version of devmgr.dll to full KernelXE. It's not needed in KernelXE lite cause it's made to install on top of BlackWingCat's extended kernel, which already contains the new devmgr.dll

I rarely touch Java, but what i have laying around is Jportable (from 2014). Portable Java environment that can run .jar files. I checked my old backups and its PackageVersion=7.0.55.0 This runs on xp x86 SP2 with SP3 reg hack. Did some snooping and found this info that may be helpful. Here is an official link to the installer and a link where you can download the jPortable_7_Update_55_online.paf.exe that i've tested in the past. It links to the official file that they still host so i believe that running it would create a portable version even today. http://javadl.sun.com/webapps/download/AutoDL?BundleId=86895 DisplayVersion=7 Update 55 DownloadMD5=8793ef637ab0ea07973e81bf9515bd09 https://sourceforge.net/projects/portableapps/files/Java Portable/ If you try the portable route make a zip backup of your CommonFiles and JportLauncher folders for when they remove old versions from the web in the future. Good luck!

I've now put some hopefully useful links in the first post. Any that are not appropriate (or wrong!) and any further suggestions for additions, please let me know! Cheers, Dave.

Hi, I wanted to share my experience of running Windows 8.1 on Dell inspiron 15 3567 with 8th gen i3. I honestly did not expect this but after 40 hours of searching for all drivers, the system works amazingly well. Compared to Windows 10 the battery last around 6-7 hours compared to just 4. It also is more snappy. Even though there is no official support and no official drivers, the laptop is rock solid. Never had any bluescreen, nothing. I'm just wondering how windows 10 can be possibly worse when it has all the support (from dell, intel etc..). Ram usage is also lower on 8.1. Came from 3.7gb to just 1.6 gb. Btw that 3.7gb figure was taken from clean install of windows 10 (no preinstalled dell bloatware). Also I can set display brightness independently (like when the computer is on charger or running from battery). That did not work on Windows 10. On Windows 8.1 there is no random "Fan ramp up" when the computer is running idle or playing videos. I tried windows 7 but unfortunately dell locked windows 7 in bios. It actually says that windows 7 is not supported on this device and bios prevented it from booting (very strange in my opinion). I have picture of this behavior if anyone is interested. Windows 8.1 is running on this device since november 2020 btw.

Actually if you are able to find kabylake chipset then there are drivers for 7/8/8.1. It is just not "officially" supported.

here is my device manager: https://prnt.sc/yepa6c Aside from the fingerprint driver (there is modding group working on it) everything is installed. The uhd 620 does not have official driver but I found some folks modding the kabylake one.

I also have to share that Win8.1 works flawlessly on a cheap MacBook Air clone that I with a Pentium n4200 (Apollo Lake CPU based on Kaby Lake CPUs) with all drivers (installed using Driver Booster) except the Intel HD Graphics 505 driver. The stock MS Basic Display Adapter driver is used, and mysteriously, Aero Glass for Win8+ works! Windows 10 was sloooooooooow on that laptop, compared to 8.1 which is a lot faster.

New development. I'll recount all my steps here in exact succession, in case this thread is of any use to anyone trying the same thing or writing guides/mods to make it all more tractable in the future. I just tried running the game again with the SwiftShader's d3d9.dll renamed and ollydbg modded cod2sp_s.exe and gfx_d3d_x86_s set to KernelEx XP SP2 compatibility (I for some reason haven't tried doing this before, but it appears not to be the issue afterall). The game offered me to "set optimal settings" since "the system config has changed", to which I clicked "no", the game then launched very quickly, when compared to the SwiftShader powered launch, where even the intro videos play choppy. The game now ran in D3d with much improved performance. I exited the game and went back to disable the KernelEx for the game exe and gfx_d3d_x86_s.dll, the game started fine again, so KernelEx does in fact seem to aid with install only. If I go back to enable/disable SwiftShader again, start the game and choose to "set optimal settings", then the Create2DTexture failed error comes up again. So it does appear that SwiftShader creates some prerequisites for d3d use in software for subsequent launches with Nvidia driver, which is Forceware 71.84 this time if it's of any importance. Issue resolved. Thank you everyone for your interest and participation, especially UCyborg, your expertise has been most helpful. I'll soon make a video of the game running with A3D and post it here if anyone's interest is already piqued. PS. Interestingly, I cannot get the above solution to work for my Radeon system, I keep getting this pesky Ddhelp error, even though the exe is now modified. My two Windows 98 systems are as follows: Core 2 Duo 6400 - Via P4M800Pro Mobo - 1GB DDR400 (no Mempatch installed) - Geforce 6800GT Core 2 Duo 6420 - i865G Mobo - 2GB DDR400 (Mempatch installed) - Radeon 9600XT

Make sure that you always use the stack size increase mod. You will get the Ddhelp problem even though it is not Ddhelp at fault if the original CoD2 executable is used unmodified.

I am not sure if it's of any help, but if I place SwiftShader's d3d9.dll in the game's folder, then I get the same error as with the gpu renderer: If I rename the gfx_d3d_x86_s.dll, then I get these two prompts: PS. With SwiftShader and Ollydbg exe mod, the game starts, runs, loads levels, but unfortunately performance is in the single digits on a Core 2 Duo 6400 and pretty much lowest settings at 640x480. A3D is also not menu selectable. PS2. A3D can be enabled through the console and seems to work pretty well. I'd just wish there was a way to run the game with Direct3D.

The theme can be renamed, version 13 is final, it is on 86 Chromium.

Jimmy Buffett - Pencil Thin Mustache (USA 1974) Jimmy Buffett - Come Monday (USA 1974)

LMAO I have moved on long ago. I'm not an id*** to refuse to update my OS so I can use visual software that's unsupported. I'm also not the first or the last person to think he should have open sourced it to help the community.

Not really though. This is a big part on Big Muscle. He was a sole developer that couldn't keep up and refused to open source the code and let the community help him. This project could still be alive and kicking had he thrown it on GitHub.

You can tell by inspecting the program's executable or its dependent DLLs whether they import GDI32.dll or not. Process Hacker comes with PE Viewer. Some programs are packed so their import table looks weird when inspected and I'm not sure whether all DLLs are shown or not. Also, OpenGL applications need certain functions from GDI32.dll. Though even if a lot of functions are used, which is probably a good indicator GDI is supported and that the program can do interesting things with it, it might just be present as the fallback. .NET programs call methods from System.Drawing namespace, which encapsulates basic GDI+ functionality. Seems System.Drawing.ni.dll is loaded by the process when used. Aye, it's pretty widespread and updated programs that use it are out there (KeePass. 7-Zip, HD Tune...). This should be re-targeted to lower .NET Framework version. Are there even any noticeable differences between different .NET versions? I suspect invoking GDI from .NET isn't very expensive.

for people who can't register here, there is another place you can create post for asking/help besides in github and blog: https://forum.eclipse.cx/viewforum.php?f=33

i use windows embedded 8.1 industry pro which is pretty snappy on my laptop and it seems faster than both 7 and 10

Where is my "I use vista on secondary machine"?

You must install KernelEx 4.5.2019.24 Updates first and directx 9c (2006) http://www.oldversion.com/windows/directx-9-0c-jun-2006 Link of KernelEx 4.5.2019.24 : https://icedrive.net/0/efIbMU55r5 And try to run the game on mode Windows 2000 or XP compatibility For more informations on how to operate with compatibility mode i found this video that might help you

2008WindowsVista I support your effort to keep these drivers alive. As you know Intel has a convoluted database that is hard to search for the drivers or they intentionally deprecate it and remove older versions (to save space) and only leave newer versions killing off support for older ones. I think these drivers are hidden from Z77 chipsets on the Intel website but should work. If not I'll back port them when I get a chance. I decided to help back up the Vista Drivers for integrated Intel HD Graphics for (Sandy Bridge / Ivy Bridge) Chipsets Z68 / Z77. Backup of the download page works although the download links are destroyed by Intel so I found a way to directly link them as long as WayBackMachine exists these files will never be lost. Archived for information purposes only and you can't directly download the files through this archive page. http://web.archive.org/web/20171008141948/https://downloadcenter.intel.com/download/20758/Graphics-Intel-HD-Graphics-Driver-for-Windows-Vista Vista 32-Bit Intel HD Graphics Drivers direct link to download file. http://web.archive.org/web/20171008142049/https://downloadmirror.intel.com/20758/a08/GFX_Win7_32_8.15.10.2761.exe Vista 64-Bit Intel HD Graphics Drivers direct link to download file. http://web.archive.org/web/20171008142245/https://downloadmirror.intel.com/20758/a08/GFX_Win7_64_8.15.10.2761.exe Now I haven't tested these recently but I seem to recall using Vista 64-bit Intel HD Graphic drivers on my Z68 and Z77 systems back in the 2012 time frame. The final test is did they retain the Windows 7 HDCP so even Vista can play Blu-ray movies properly or if this was just a basic graphics drivers. I'll have to test these later to see if they work but these new download links will ensure they will never be deleted even if Intel secretly removes them one day from their own server. I suggested people archive the two Vista 32/64 Bit direct download links as a bookmark in case MSFN goes down you can still find them. Readme file: http://web.archive.org/web/20171008143938/https://downloadmirror.intel.com/20758/eng/GFX_8.15.10.2761_readme.txt

That's an Intel chipset without a USB 3.0 controller. There is an additional NEC USB controller. NEC does provide XP 32-bit and XP 64-bit drivers. USB 3.0 in an of itself works on XP, both XP 32-bit and XP 64-bit.