gerwin

For Atom N270 Chipset, the above quoted hardware. EDIT, hold on, I think we have mismatch, and that both your systems actually have a newer Atom model CPU, compared to the Atom N270/N280 that I first got as a search result. "GMA 3600, This integrated graphics system was released in Intel Atom (Cedar Trail, 32 nm) and based on PowerVR SGX545" See this topic, which seems to be an exact match of the issue at hand: https://community.intel.com/t5/Graphics/Intel-R-Graphics-Media-Accelerator-3600-Series-WINDOWS-XP-driver/td-p/214041 In the last post there, there is a working 4shared link to "intel® graphics media accelerator 3600 series - winxp-x86-sp3.zip". If that does not work either, I don't know what to suggest. I remember, back in the day I got an Atom N280 Netbook especially because Netbooks with newer Atom CPU's/Chip-sets were dropping Windows XP driver support.

Your ACER D270 seems to have a Diamondville N270 Atom processor on the usual intel chipset with integrated graphics. It should be a netbook actually, smaller then a laptop. https://en.wikipedia.org/wiki/List_of_Intel_Atom_processors#"Diamondville"_(45_nm) I stored this intel graphics driver for use with an N280 Atom netbook, and it could run some Direct X games: https://www.mediafire.com/file/bjrem67xjmizvt5/VGA_iGMA950_WinXP_v6.14.10.4926.zip/file (VGA iGMA950 WinXP v6.14.10.4926.zip, 17 MB, 15-02-2008)

The browser discussions were moved here: https://msfn.org/board/forum/201-browsers-working-on-older-nt-family-oses/

Code::Blocks Win32, rev.12857, June 20, 2022 with working symbols browser. Kindly provided by developer Miguel Gimenez on request. Download link here https://forums.codeblocks.org/index.php/topic,24592.new.html#new Link is told to expire soon, so download now if you care for it. The drmingw-0.8.2 trick still applies.

Even if they included those, one would still have missing calls in kernel32.dll and ntdll.dll. On second look codeblocks-20.03 still shows promise for running under Windows XP. The dependency trouble all branches from exchndl.dll, which branches to dbghelp.dll and mgwhelp.dll. The issue is with this debugging library, v0.9.1.0 https://github.com/jrfonseca/drmingw Download v0.8.2.0 from there and copy the dll and sym files to the codeblocks 20.03 folder to make it run in Windows XP. (I did have some wxWidgets non-fatal error, which was caused by v20.03 portable referring to my v16 install location. When putting 20.03 portable in the path that I had previously installed v16 to, there is no error) Edit: Deal breaker in attached image, back to v16 or v17. Or if someone manages to find a Win32 nightly build dated march 2021 or later, which is when the symbols browser was fixed.

Github currently works reasonably well with current NewMoon (Palemoon) 28 unofficial fork supplied by Roytam, together with an unofficial "github-wc-polyfill-1.2.19.1" extension, also supplied by Roytam (based on JustOff's original). See the "My browser builds" topic on this forum.

Multi-function Printer Epson WF-4830DTWF (sold from 2020 to this day) with driver package epson645995eu works on Windows XP SP3. Scanner part also works with driver package epson636209eu.

The guy behind the website wp.xin.at is also a user of the Vogons forum nicknamed GrandAdmiralThrawn https://www.vogons.org/viewtopic.php?p=784051 . Surely it is all with best intentions, though you cannot expect someone to check all the sourcecode when doing some backporting.

I am not an expert, but so far I have done a few Kernel-ex mods without changing anything to the main Windows XP installation. Instead it was done by adding the wrapper dll files in the root of the troublesome program, then hexedit the executable of the troublesome program, to refer to the wrapper dll names instead of the original windows dll names. Like search for the "advapi32.dll" string and changing it with "advapixp.dll", and make sure the wrapper dll is in the same folder as that modded executable, and has the file name advapixp.dll. That xp suffix is just something I made up, it does not matter what it is, just that it is different from the windows one. Sometimes things are more entwined with multiple dll libraries involved.

This project also wraps RegGetValueA https://github.com/UncleVasya/EU4_WinXP_fix/blob/master/source/advapi32/advapi32.cpp

This donation of mine was never acknowledged here, AFAIK: 50,00 USD 16-09-2021 Paypal reference 9J944236YT7310825 ---------------------------------- This one added today: 25,00 USD 10-03-2022 Paypal reference 3LL94829V36859139

Yeah, my fault, I mistakenly understood that the lock-up occurred when starting your computer, but it occurs only when you start that particular program. So my advise did not really apply. I suppose the Nirsoft monitoring tools, which were advised by jumper, are the first way to go. If those do not suffice maybe try OllyDbg 1.10. It can hide its presence with plugins.

Sorry it seems these shortcuts have the "lnk" extension. But the extension is hidden in the GUI. "pif" was also a Windows shortcut format, but an older one for MS-DOS executables...

@Ben Markson - Thanks! That works.

I don't follow the discussion much. But I do find that .pif shortcuts to executables can slow down things in Windows XP. Especially when you put about two dozen in the start menu, and wait for that to open.

Thanks! Any chance for a pre-build download?

When you are sure it is Norton software causing the problems, why not remove everything Norton? Or prevent any of its services and auto-runs, like with msconfig and such? Optionally in safe mode (F8). I also had some lockups on one of my XP systems recently. Hard locks like you described. It most often happened in the first 5 minutes after boot, especially when doing absolutely nothing. I figured it may have something to do with software trying to update. So I disabled all Windows Update / Windows Defender / Microsoft security essentials (MSE) related services and auto-runs there. I have not had a lockup since. (AFAIK it is not possible to keep MSE running, whilst preventing it from initiating useless update attempts. As visible in Eventvwr. Other systems with pretty similar setup somehow did not have any lockup problem.)

Can say that AutoCAD 2002 (full / non-lite) works on Windows XP with all POSReady updates just fine.

Error 0xe06d7363 with autoCAD; it seems like it can mean almost anything. I just fixed an AutoCAD 2002 on Windows 7 installation, which had this particular error message. The fix was in this case to empty out this registry key: HKEY_CURRENT_USER\Software\Autodesk\AutoCAD\R15.0\ACAD-1:409\File History And maybe prevent non-admin access to it, as to prevent future such issues. This AutoCAD 2002 can give all kinds of strange behaviors when the file history list contains a non-existing drive.

I have been using this compiler successfully for several hobby things, and thought it was worth a try to tackle its issues with the "\include" header-files folder. Using the command "cpp.exe -v" gives the list of search directories for header files. The result of which show again that it is overlooking it's MinGW include folder, and only looking in the more nested GCC system include folder. I found several messages on the internet reporting the same issue with certain MinGW/GCC homemade builds. The usual answer is to build GCC again properly, not as easy as it sounds. Instead, I tried several hex edits, and settled for this one: cc1.exe at offset E73C23 cc1plus.exe at offset F8B203 original string "i686-w64-mingw32/include" is to be replaced by just "include". The now unused characters need to be zeroed out. Then things work properly. Note that the search-order if the three header folders is a bit different, with the MinGW include folder now being 3rd instead of 1st. (Besides the ReactOS build environment package I also found this one GCC_8.4.0_for_MSYS2 . I only tried its cc1/cc1plus files, they have the exact same behaviour: WinXP compatible but include dir issue. The executables in this package are UPX compressed.) Edit: looking some more at that GCC_8.4.0_for_MSYS2 package. It is a much better example of how the folder structure was originally intended compared to the special purpose ReactOS package. It has a populated ".\i686-w64-mingw32\include" folder, and an empty but still present ".\include" folder. So instead of hex editing one can use ".\i686-w64-mingw32\include" and disregard ".\include". I will see what works better...

Another one here holding out with a classic. A sony-ericsson W800i (2005), nothing special. No whatsapp either. In my actual surroundings I am the last one that has kept it that way.

I agree that GZDoom was already one of the most mature and polished games many years ago. Especially for playing the classic contents. And as for dated operating systems, I worked on this one in 2014: https://doomwiki.org/wiki/MBF And here is another recent one for MS-DOS: https://doomwiki.org/wiki/FastDoom Some people from the ZDoom/DRDteam websites contacted me about MBF about a year ago. If their wiki entry was OK to me. No problem.

Thanks again! The toolbar icons became a somewhat ugly since previous versions. It seems they are made for white background only.

I also have an older iPad mini 3 with IOS 8.1.3 (2015), and I am using similar iTools v1.8.4.6 for it. That iTools version is just a single portable executable, and works great. Note that IOS 8 Safari Browser is unusable on the current internet. Anyways that old one may die one of these days, so when I saw an offer for a low-priced spare I decided to go for that. Even though there is a lot to dislike about iPads and IOS too, I know.

Big pleasant surprise here: Full connectivity with an iPad Mini 4 (2015-2019) with IOS 14.6 (24-05-2021) installed. Using iTools v4.3.5.5. This allows for access to photos, music, ebooks etc. So this iTools program downloads and installs apple drivers automatically (normally part of iTunes software), and it seemingly succeeds in doing that under Windows XP. (The currently latest version of iTools, v4.4.5.6. does not run on Windows XP. Many calls to unsupported functions. ) Edit: Latest 3uTools v2.57.031 (2021-08-30) is very similar. It seems to have more options. It also works under windows XP, and also successfully connects to the mentioned iPad. Actually this 3uTools works better compared to the mentioned iTools version, as it is more recent, and better adapted to IOS 14.6 specifics.