jaclaz

Do you have a comparison with some other system (like - say - Windows 7 or newer) on the same network and on the same NAS? Only to exclude that is *something else* outside the XP install. Do you have IPV6 installed in the XP? (there are reports of this creating slow transfers on local network) Then you can see if any TCP optimization helps: https://web.archive.org/web/20070228142414/https://www.psc.edu/networking/projects/tcptune/OStune/winxp/winxp_stepbystep.html And you can try to reduce SMB traffic generated by Explorer: https://blogs.technet.microsoft.com/askperf/2007/09/21/windows-explorer-and-smb-traffic/ jaclaz

Life is good because it is so varied I see those as features and advantages of Windows 7 when compared to 10. jaclaz

Abanoners? jaclaz

Get the manual for your motherboard: https://www.gigabyte.com/Motherboard/GA-H81M-WW-rev-10#support-manual Check ATTENTIVELY what is written on page 24 of the manual: Report how EXACTLY you have set the settings listed in it (except the Administrator and User password settings). jaclaz

Well, for the record, I don't think that the OP was attempting a (direct or indirect) upgrade, but rather replacing one of his two instances of XP with a fresh install of 8.1. jaclaz

Not strictly Windows 10 related, but close enough to be worth mentioning here, a good analysis/rant on OneDrive, aptly titled "OneDrive Down the Road to Madness": http://www.eejournal.com/article/onedrive-down-the-road-to-madness/ jaclaz

A new kid on the block (Windows 95, not 98), JFYI: https://github.com/felixrieseberg/windows95 The Verge commentary: https://www.theverge.com/2018/8/23/17773180/microsoft-windows-95-app-download-features is however puzzling, considering that original requisites for Windows 95 were : 1) 4MB of memory (8MB recommended) 2) 50-70 MB space on hard disk Personally I am not surprised at all, as a matter of fact I find it an unbearable amount of bloat. jaclaz

As often happens I may be wrong, but - provided that the picture was originally shot by FranceBB, the attribution by the Register: seems to me - besides "vague" - slightly offensive. jaclaz

Well, you asked for an urgent reply, you didn't specify you wanted a kind one, additionally. And we are still in the "my PC" undetermined realm. I would therefore take the occasion to kindly re-submit to your attention the opportunity to explicitly describe make/model of "your PC"[1] as this would likely allow this thread to move from (educated) guesses to (hopefully) suitable solutions to the problem you have. It is my pleasure to provide the following info: A PC may have : 1) a BIOS firmware 2) a UEFI ONLY firmware 3) a UEFI firmware with a CSM (Compatibility Support Module), i.e. an additional BIOS-like environment Your PC should belong to type #3 above, as the message the Windows 8.1 setup showed is related to a UEFI installation (that implies GPT partitioning), but since you are already running on that same PC a XP (that CANNOT boot in UEFI) and using a MBR partitioned disk evidently for *some reasons* either the choice between BIOS and UEFI was changed in the firmware settings or *for some other reasons* the Windows 8.1 setup mistakenly attempts to install the windows in UEFI mode. There are several different ways to either correct the cause of the problem or workaround it, including: 1) directly applying the install.wim to the target partition 2) using another method from the built-in Windows Setup to install the OS, like the good WINNTSETUP 3) temporarily change the partitoning from MBR to GPT (in a way that allows to not loose any data) and possibly more, but they may either have some definite prerequisites or possible unwanted consequences. So, in order to serve you at the best of my possibilities, before being more explicit in advising you I respectfully suggest that you provide the needed info. I perfectly understand how this, and particularly the tone with which such requests are made may cause you anxiety, stress, or more generally - directly or indirectly - inconveniencies, and of course I beg your pardon in advance, but it remains my firm belief that without these info there is - through the unfortunate suggestion of a specifically not suitable method - a possible risk for the integrity of your data. jaclaz [1] and - additionally - a description of the hard disk you have in it and the exact way you have it partitioned and formatted

1) that you have not a backup is a real problem, much bigger than your issue with installing 8.1 2) "my PC" tells nothing, you should provide some info on the system, and specifically if you are attempting to boot in UEFI mode: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-8.1-and-8/dn336946(v=win.10) https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/boot-to-uefi-mode-or-legacy-bios-mode Maybe you chose the UEFI device, like here: https://www.youtube.com/watch?v=-GSW3-dPC_c 3) JFYI, you won't make many friends on the board (nor you will be served better or faster) by using "urgent" and lots of exclamation points.l jaclaz

No comment [1]. jaclaz [1] Both as "No comment" and as "No comment needed"

Well, you posted: The little script above is a plain, simple, batch script, nothing particularly fancy, and definitely NOT Powershell, I don't think I EVER wrote anything so clear/self explaining. Essentially the variables are: %DirPath% <- comment: this is the directory path where you wish to search it is passed to the batch as first argument or %1 %LookFor% <- comment: this is the pattern to look for it is passed (optionally) to the batch as second argument or %2 The line in the batch: ECHO Looking for pattern "%LookFor%" in files in %DirPath% should have been self-explanatory. Abstracting from the minutiae, the batch is made of 3 (three) blocks of code: 1) do some minimal input validation: IF %1.==. (SET DirPath="%~dp0") ELSE (SET DirPath="%~1") IF NOT %DirPath:~-2,1%==\ SET DirPath="%DirPath:"=%\" IF NOT EXIST %DirPath% SET DirPath="%~dp0" SET LookFor=%2 IF NOT DEFINED LookFor SET LookFor=. 2) look for any file in with extension .zip in the path provided ECHO Looking for pattern "%LookFor%" in files in %DirPath%&ECHO. FOR /F "tokens=* delims=" %%A in ('dir /b /s %DirPath%') do ( REM ECHO %%~dpnxA IF %%~xA==.zip CALL :listzip "%%~dpnxA" ) 3) if such a file is found, use unzip to list its contents and pass these contents to the FINDSTR command: :listzip FOR /F "skip=2 tokens=* delims=" %%B IN ('unzip -l -q %1') DO ( SET Thisline=%%B IF "!ThisLine:~0,4!"=="----" ECHO.&GOTO :EOF ECHO %~1 !ThisLine:~28,50! | FINDSTR /I %LookFor% ) All the "magic" happens in this line where the filename found inside the zip is piped to FINDSTR: ECHO %~1 !ThisLine:~28,50! | FINDSTR /I %LookFor% FINDSTR is a documented command, its syntax is similar to REGEX, but not exactly it, a said: https://ss64.com/nt/findstr.html and can be replaced in the last line of the batch by any similar pipable command. like as said grep. If you have specific questions, by all means ask them. jaclaz

https://www.theverge.com/2018/8/17/17724658/screen-time-blue-light-blindness-science jaclaz

Sure , little green men are known for going on boards overnight (when they are bored after stealing socks) and replacing the sixth letter of the alphabet with 1's randomly. It is a known 1act. d@mn , they did it again , jaclaz

Check the temperature of the CPU/that the heatsink is properly connected, first thing. Then, if that is OK, disconnect EVERYTHING from it (and from the motherboard). Leave ONLY video and keyboard connected. Boot (actually fail to boot) and enter the BIOS. If it stays on on the BIOS page, switch it off and re-add (one at the time or in small groups) all the other peripherals, add-on cards, hard disk(s), CD/DVD, etc. and repeat the above boot test (without starting the OS). jaclaz

The original Author has discontnued the tool. Have you tried the unofficial 2.0 version? https://github.com/Bioruebe/UniExtract2/releases jaclaz

Well, double-checking if it is a "1" or a "f" shouldn't take much time, at least we would know if we got that right or we are all barking up the wrong tree. jaclaz

Better (for next time ) and possibly also waaay quicker (for the specific task): http://www.virtualdesktop.org/complete/index.html jaclaz

Maybe . Snippet from the transcript of the video: On the page for the HP 15-F233WM there is only one file September 2016: https://support.hp.com/sk-en/drivers/selfservice/hp-15-f200-notebook-pc-series/7527799/model/8857447 F.32 Rev.A Release date: Sep 30, 2016 File name: SP77751.exe https://ftp.hp.com/pub/softpaq/sp77501-78000/sp77751.exe Whilst the F.29 Rev.A is from August 2016 Release date: Aug 1, 2016 File name: SP76871.exe https://ftp.hp.com/pub/softpaq/sp76501-77000/sp76871.exe and there are n later versions (that presumably and hopefully have not introduced a regression bug). The model name (in the video) is definitely HP 15-F233WM, maybe it is the same one as Tommy has , as I could find no trace of a HP 15-1233wm? The family is seemingly f200: https://support.hp.com/sk-en/product/hp-15-f200-notebook-pc-series/7527799 I have found a number of posts on HP support forums where the thingy is called 1233WM (and responders usually reply about f233WM) maybe the small "f" is printed in such a way that it can be confused with a "1"? Among the ones related to the f233 model, one (well before September 2016) has no issues with ACPI (only with USB, obviously): https://h30434.www3.hp.com/t5/Notebook-Operating-System-and-Recovery/15-233wm/td-p/5267922 and another one (October 2017) as well has no issues with ACPI, only with drivers: https://h30434.www3.hp.com/t5/Notebook-Operating-System-and-Recovery/HP-15-f233wm-laptop-installing-windows-7/td-p/6387015 Actually the latter (provided that the info in it is accurate) points to another HP model that should be using almost all the same drivers (NOT the BIOS/firmware) as the f233, the HP 250 G4: https://support.hp.com/us-en/drivers/selfservice/hp-250-g4-notebook-pc/7609933 jaclaz

I believe that kind of setup is called in jargon SMVMS (Slow Matrioschka Virtual Machine Set) or LTVMM (Letargic Telescopic Virtual Machine Mixup). jaclaz

You mean this one? https://www.youtube.com/watch?v=LDgEZ-6kGQU Surely a very good source of technical info. jaclaz

Naah, those apply to the southern hemisphere only, in the northern one you need a crossbow, an hourglass, three goats and a trumpet : https://www.imdb.com/title/tt1298650/quotes/qt1491333 Just in case: https://support.microsoft.com/en-us/help/262841/command-line-switches-for-windows-software-update-packages jaclaz

How (exactly) did you try to install? In some cases installing "the right way" (i.e. applying the .wim with imagex/bcdboot/bootsect thus bypassing the actual Windows setup and running - if needed - a bootrec.exe) allows to install. Check: http://reboot.pro/topic/10126-nt-6x-fast-installer-install-win7-directly-to-usb-external-drive/ and/or its successor WINNTSETUP: https://msfn.org/board/topic/149612-winntsetup-v391/ jaclaz

It's the same link twice, once in German, the second in English. The procedure is rather complex (actually more lengthy then complex), but it is broken down in 21 points, WHICH one(s) are not clear to you? jaclaz

The actual howto's being here: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/dism-operating-system-package-servicing-command-line-options https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-or-remove-packages-offline-using-dism This is simpler/more to the point: https://www.madsd.dk/blog/comments.php?entry_id=17 Though normally updates are integrated to the install.wim, not to the boot.wim, it is possible that there are some other pre-requisites/sub-systems that need to be integrated as well to have that working. jaclaz