The problem with such system Is no more official support Modern hardware is lacking of support too Modern apps will stop or stopped support it too
Who cares? Let these people have their fun and play around, they are not harming anyone and after thousands of posts on these boards, I'm sure they are well aware of the risks.
1) Fully updated OS means - FINAL build, finally after 18 years. Nothing bad in this point 2) Yes modern hardware will stop us one day - until Quibble or any other boot loader allow boot 32bit OS on x64 UEFI. Of course we need generic GPU driver as well - I'm sure we can manage to compile in WDK 7.1 first public code of basicdisplay driver in future. 3) Just use latest supported app for that purpose. There are still tons of apps that still runs on XP and are under active development
I still love this system, I say XP, 7, and 10 are the best system that exist too bad i can only run it under VM, and that includes w` 7 or consider to buy old used laptop for that purpose only
Well I have various old laptops, but I'm currently looking to get is Dell Alienware 15 R2 it have most powerful XP compatible GPU, question is, have this laptop CSM?
Oh yes, Marketers don't still even end up believing that software is getting old! A beautiful cash cow that has been well maintained for several decades now based on a serious lie maintained by fear of risk.
Screen from WinPE based on Windows 7. ListDisk seems good. One line for each physical partition and their volume informations when exist.
Any idea on a release? Been keeping the primary tab open for months and hitting refresh to see when it was last updated so I can finally use this on modern hardware lol
I respect the work, and yes you are free to do whatever, but, it's not secure, and, messing with hardware configfiles and using drivers that weren't really meant for XP and other such modifications could and most likely will, produce unintended consequences for your hardware in the long run. I could be wrong, but I wouldn't risk it for my hard earned money and purchased tech.
I just worked on an Alienware 15 R4, and it has a very strange BIOS build. It is both UEFI and CSM, but in the old CSM blue screen style, and it was using RAID0 for system storage on two separate ssd's to have them as one in Windows 11.
And that's your choice and that's fine, just like these folks have their choice and they want to mess around. Let them. It's almost like you want to spoil their fun and hobby.
A clear sign you need to snap out of it and be realistic. The guy is working on the project. If he sees something he doesn't like, he fixes it. When that will happen is entirely up to him and really not a subject of deadlines. On xda there's a rule against asking for ETAs for a reason.
Just use the Watch Thread function and you'll get a notification when someone replies, then you can come in and check and go about your day if it's not what you're hoping for.
I found why my ListDisk can't run on XP. I will update VS project to include XP compatible binary too. It must be dynamic build instead of static and doesn't matter if v141_xp or v142 toolset is used. Static buill works fine for WinPE 6.0+ for example. Btw, I think it's bug in Visual Studio headers itself when genrating static build. And of course this missing kernel32.dll imports will lead into another extender in future. I quess kernel8.sys will be added to kernel extender project.