jaclaz

Another option (easy if it works) would be to use RMPREPUSB: https://rmprepusb.com/tutorials/030-how-to-install-xp-onto-a-hard-disk-from-an-xp-iso-on-a-bootable-usb-drive/ or - even easier (once you get the hang of it) - Easy2boot: https://easy2boot.xyz/ Personally I would first try the Tutorial #30 with RMPREPUSB, or, if you can make a PE v.3, tutorial #82: https://rmprepusb.com/tutorials/082-install-xp-to-hard-disk-from-isos-using-winpe-v3/ jaclaz

That is a generic puff piece pushing a registry cleaner. Totally not useful. jaclaz

The STOP error may well be an issue with the actual CD or DVD burn, with modern, high speed CD/DVD burners it is not unheard of burned discs difficult to read on old readers. The flash drive issue is more likely to be connected to the way you partitioned/formatted it and in any case you cannot normally/easily use a CD/ISO image from a stick, and creating a stick capable of installing XP is complex. There are a few tools for that, you should try first thing WinSetupFromUsb: https://msfn.org/board/topic/120444-how-to-install-windows-from-usb-winsetupfromusb-with-gui/ but check other topics here: https://msfn.org/board/forum/157-install-windows-from-usb/ particularly this tool here: https://msfn.org/board/topic/149612-winntsetup-v526-53-beta-4/ but cannot say if current version is still XP compatible. jaclaz

It is a good idea (always) to have the OS stop (and not reboot) on BSOD's (for next time): HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CrashControl Autireboot (set it to 0 to prevent rebooting) Usually (but not always) minidump is enabled, so the nifty Nirsoft tool might be able to catch that (past) BSOD, to check if the minidump is enabled: https://blog.nirsoft.net/2010/07/27/how-to-configure-windows-to-create-minidump-files-on-bsod/ jaclaz

No idea about the BSOD after scandisk/Chkdsk, without a known STOP ERROR it could be *anything*. The Merge-Ide is "safe" in the sense that the only thing that does is to restore the "Standardl" Microsoft PCI/ATA controller driver (the one that is default when you install without any particular disk controller driver), it may (or it may not) have helped, but surely it didn't cause the BSOD in itself as by the time you rebooted and (auto) ran chkdsk it must have been already been replaced by the LSI driver. It could also have been a random "glitch in the matrix", or it could be that *for whatever reasons* one of the volumes was mounted read only and chkdsk needed instead to change something on it I think the only thing you can do is to make an image of the install volume (as a way back in case of issues) and see if the scandisk or chkdsk creates the issue again, as I see it chkdsk is a vital part of a Windows install, and you should not consider the install "stable" until you are sure that it works normally, jaclaz

JFYI, and in case of need, there is a tool to edit offline registry files "directly" (without importing the hive(s) in Regedit): https://labalec.fr/erwan/?cat=95 Reboot.pro is down, unfortunately, but there is a good guide for it here: http://mistyprojects.co.uk/documents/offlinereg/offlinereg.htm jaclaz

Try this: https://www.brighthub.com/multimedia/audio/articles/95590/ Anyway the software home page is: https://www.nch.com.au/scribe/ but, it is ANOTHER kind of software from what the OP asked for: Express Scribe Transcription Software Foot Pedal Controlled Digital Transcription Audio Player LegacyFan, if you were a greengrocer and someone asks you a lemon, you can't usually give them two cucumbers instead . jaclaz

Still : https://dictionary.cambridge.org/dictionary/english/enthusiast and punctuation/capitalization would IMHO need a check or two. jaclaz

Good start, keep 'em coming. But please watch the typos, it is really a pity when the reader fails to appreciate the contents because he/she is distracted by them, I counted at least 5 issues in: jaclaz

I see, it is a long term plan, halfway by Easter and the other halfway hopefully by Christmas 2023 Do post here every time you add something, it is important to document each step, so that we might later be able to make a documentary on "the making of". jaclaz

Viewing WHAT? The Few Things being ANY meaningful content. But please do keep up posted on the progress. jaclaz

AFAIK the Surface Go is a Class-3 UEFI: https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-8.1-and-8/hh824898(v=win.10)?redirectedfrom=MSDN And - still AFAIK - UefiSeven or similar is needed on such hardware: https://www.sevenforums.com/installation-setup/426914-installing-win-7-pro-sp1-uefi-class-3-gen-10-laptop.html https://github.com/manatails/uefiseven I consider that "a trick". jaclaz

Yes, it seems like it is listed in diskpart but invisible in disk manager, also in later Windows versions see the image here: https://social.technet.microsoft.com/Forums/en-US/a0a64818-6150-40b4-b5b3-915eb8fe31c9/msr-reserved-partition-does-not-appear-in-disk-management-nor-in-my-backup-program?forum=w8itproinstall jaclaz

There are two base issues: #1 the Surface Go is a UEFI only machine, as such has no BIOS (or CSM) whilst Windows 7 has not built-in proper support for UEFI booting, this can usually worked around using a later Windows OS bootloader and a couple of tricks #2 if I recall correctly (but I may well be wrong) the Surface has UEFI GOP video which adds an additional problem, there is (right now the whole board is down, unfortunately) thread on reboot.pro about a possible way to force a Windows 7 to use a GOP driver through an extremely risky procedure (and BTW I cannot remember if it was a generic solution or specific to some particular hardware) AND a third one: #3 the hardware of a Surface (and particularly of the Go type) will need device drivers that simply do not exist for Windows 7 So, in theory everything is possible, but the issue is not "jailbreaking" (that usually means to expose existing functionalities that are locked down or inaccessible), one would need to have a whole replacement firmware AND all the needed drivers, as a parallel example you cannot install a *common* Linux distro on it, you need particular files: https://github.com/linux-surface/linux-surface because the Microsoft hardware on the Surface has its own peculiarities. jaclaz

It works on XP as well, at least on the 32 bit version. jaclaz

Sure, but whether Microsoft supports (or fails to support) any given OS does not imply that another OS can run on it. While, as said, it is very unlikely that 7 can be installed on a Surface Go for technical reasons, the fact that MS does not support it is not particularly relevant. jaclaz

AND it doesn't mention XP64. Here is a Wikipedia page about scope: https://en.wikipedia.org/wiki/Wikipedia:Out_of_scope It will help the OP as much as your post (not at all ) but you might find it interesting . jaclaz

@Comos Then that is likely the issue. The Hitachi microdrive filter is (was) specifically made at the time for CF cards/Microdrives and only "flipped" the "removable" bit, as Andalu suggested, the DiskMod is a newer (and more complete/more featured) filter driver that can "flip" *something else* and make the (queer) drive suitable to host the pagefile. jaclaz

I know, it was a rhetorical question to quickly check the reliability of the suggestion. jaclaz

Check this, though it is improbable: https://learn.microsoft.com/en-us/archive/blogs/astebner/registry-key-to-force-windows-to-use-short-filenames Maybe it is *something else* that *somehow* prevents the proper setting of the secondary entry, you could check the actual file/folder entry on the filesystem: https://www.ntfs.com/fat-filenames.htm AFAIK the long and short filenames are two separate entries (the short filename one is automatically generated at file creation), which explains why you have your long file name shortcuts still working, so it could be *something* that only shows the short filename. Does this happen with *any* copy utility/method or just with a given one? As well, do you see the short file name with *any* tool (dir from command line, explorer, other file manager, etc.) or just in a given one? Are you sure that the issue is with filenames (and not with long PATH)? jaclaz

Can you explain? Maybe that is the issue ("wrong" type of device). jaclaz

Only for the record the limit for a file in $MFT is around 750 bytes on 512 bytes sector ($MFT record sized 1Kb) and around 3800 on 4K sectors ($MFT entry sized 4Kb), exact values here: https://www.forensicfocus.com/forums/general/mft-resident-data/paged/2/ jaclaz

Does "CSM bios mode" exist on a Surface Go? jaclaz

I could not understand anything in your post , but - generally speaking - it is not multiplication where changing the order of factors does not change the product. jaclaz

The right video link, as the video in itself is "wrong", the first thing they say is that they are not going to actually install windows 7, but rather that they are going to install the Windows 7 inside a VM (Virtual Machine) running on Windows 8 or 8.1. Anyway the OP has seen people installing 7 on modern hardware, so possibly he could ask those people how they installed it, though I have to remind that modern hardware is not a synonym of a Microsoft Surface, and particularly not of a Surface Go. I don't think it is possible at all, due to the peculiarities of Surface's (generally) hardware (namely the UEFI only and - if I recall correctly - GOP only video[1]), but additionally the Surface GO is a relatively recent model and I doubt that - even if *somehow* you can get past the two mentioned roadblocks - appropriate drivers can be found for it. jaclaz [1] there are actually workarounds for these - though complex and risky - that may apply to some "modern" hardware, but I doubt specifically to the Surface