jaclaz

@Cixert MB alignment on XP is not in itself an issue BUT you SHOULD NOT ever use XP Disk Manager if you have logical volumes inside extended. See here: http://reboot.pro/topic/9897-vistawin7-versus-xp-partitioning-issue/ basically when doing even minor adjustments in Disk Manager (such as changing the active/boot status of a primary partition) Disk Manager checks, finds invalid and (wrongly) "corrects" (silently) some sectors offsets in the EPBR chain inside the extended partition making logical volumes in it "vanish", primary partitions are unaffected. About FAT/FAT32, the generic idea is (should be) that of "optimizing" the volume, now what "optimizing" means is up to debate, having larger cluster size implies more space "wasted" for smaller files but smaller File Allocation Tables, viceversa having the smallest possible cluster size implies having larger FAT's. MS (in their wisdom) set cluster size depending on volume size, and - strangely enough - documented the default settings (though somewhat wrongly, as there was no FAT32 in NT 3.51 and 4.0): https://support.microsoft.com/en-us/topic/default-cluster-size-for-ntfs-fat-and-exfat-9772e6f1-e31a-00d7-e18f-73169155af95 there is a hardcoded limit in the amount of clusters in a given filesystem, so when the volume grows in size you need to make larger clusters to keep the number of clusters low enough. In theory you could make very large sized clusters with the consequence that - since the cluster is the minimal unit addressable by the filesystem - even a 1 byte file will take a whole cluster. They allowed largish clusters (up to 64 KB for FAT16) but later they went for much smaller ones (16 KB for FAT32), the reason being either that of not using too much space for small files or (more probable) to push for NTFS. The hardcoded limits are: For FAT16, 2^16-1, i.e. 65,535 in theory, a few less, depending on implementations, as some values are reserved, usually 65524 or 65526 is the actual max For FAT32, 2^28-1, i.e. 268,435,455 (yes FAT32 is actually more like FAT28 as only 28 bits are used, 4 bits are "reserved") The idea should be that the smaller size cluster is better, as long as the total amount of clusters is within the limits, but since this implies larger FAT's the overall performance of the filesystem may suffer from it, the MS defaults are a compromise of sorts, particularly for FAT32, where the number of clusters is artificially limited to around 2 millions that at 16 KB/cluster sets the (infamous) FAT32 max 32 GB size. . But each program (within these hardcoded limits) can decide to use this (or that) cluster size for a given volume size (a few allow you to choose the cluster size), then some tools may not like non-standard values, old thread where dencorso listed in detail how 6-8 million clusters may be a better compromise: https://msfn.org/board/topic/118623-clone-easily-windows-98-and-xp-in-the-same-computer/?do=findComment&comment=866527 jaclaz [1] Yes, I know these should be called GIB and KIB nowadays

Let's introduce a good nonsense poem (by Mervyn Peake) https://www.mervynpeake.org/nonsense.html THE TROUBLE WITH GERANIUMS The trouble with geraniums is that they’re much too red! The trouble with my toast is that it’s far too full of bread. The trouble with a diamond is that it’s much too bright. The same applies to fish and stars and the electric light. The troubles with the stars I see lies in the way they fly. The trouble with myself is all self-centred in the eye. The trouble with my looking-glass is that it shows me, me; there’s trouble in all sorts of things where it should never be. jaclaz

For use under XP, JFYI,Tiny Hexer is an useful hex editor that has templates/structure viewers: https://www.softpedia.com/get/Others/Miscellaneous/tiny-hexer.shtml some structure viewers for it (shameless plug): http://reboot.pro/topic/8734-tiny-hexer-scripts/ jaclaz

Since you have a Windows 10 available, use the fsutil to check the sector size that the disk exposes. If it exposes 512 bytes/sector, you won't be able to access more than 2.2 TB (a special formatting is possible to access up to around 4.4 TB, but it won't work in XP only in 7 and possibly later) If it exposes 4096 bytes sector (aka 4K native), then it should be possible to access the whole 5 TB from XP (but the disk won't be bootable, for other reasons). The fact that all tools you tried set a limit to 2-2.2 TB should mean that the disk exposes a 512 bytes/sector, and as such you cannot go past the 2^32-1 sector llimit. The 1 MB in front of the partition you created is rather "normal", it is the "new" alignment to 1MB (2048 512 bytes/sector) introduced since Vista as opposed to the traditional 63 sector (cylinder/head alignment) used up to XP (but XP has no issues with 1 MB alignment UNLESS you use logical volumes inside extended). The thread you referenced is about a very peculiar external case with two connection interfaces, eSATA and USB) that provided a "pass through" on one interface and a "translated" one on the other, your disk has only one interface (USB) so it is unrelated, it can only be useful if you need to (tangentially) learn more about the implications of 512/512AF vs. 4K disks. Check the disk with gdisk: https://www.rodsbooks.com/gdisk/ not the most friendly tool around, but the only one that will provide you with the exact data in either the MBR partition table or GPT. jaclaz

I don't know about MSDN subscriptions, but both Visual Studio 6.0 and 2015 are available on archive.org. https://archive.org/search.php?query=subject%3A"visual+studio" jaclaz

Maybe useful, maybe not; http://laurencejackson.com/win32/ https://archive.org/details/msdn-3345.2-012007 jaclaz

Probably the only way is to execute some commands when starting Chrome (i.e. it doesn't work for "current session"): https://stackoverflow.com/questions/53505079/how-to-change-default-download-folder-in-chrome-using-powershell You will have to try, but it seems that to "reset" to the "generic default directory" it is enough to delete the "default_directory" line/element in the Preferences, it should be something like: "download": { "default_directory": "C:\\datashop\\downloads", "directory_upgrade": true, "extensions_to_open": "", "prompt_for_download": false }, There might also be a Registry "policy", but that will - I believe - override any setting in "preferences" https://admx.help/?Category=Chrome&Policy=Google.Policies.Chrome::DownloadDirectory jaclaz

Unihertz are among the very few that make nice small phones (everyone is going 5-6" size or bigger). An alternative (do you remember the times when a cellular phone was called "handy") is Cubot (another Chinese brand). I quickly bought one of their "rugged" 4" ones when it became compulsory to scan people's "green pass" (for COVID 19 vaccination) and needed a small, tough device. Cannot really say how it works as a phone, for what I bought it (checking QR codes to validate with the Italian app) it worked just fine, and having costed around 120 Euro, it has well repaid itself, the one I have is the King Kong Mini, it is very heavy for the size, but has a good grip with one hand, the "rugged" is more esthetics than actual protection/ruggedness, but it contributes to avoid it slippong from your hand. They made a new version: https://www.cubot.net/Smartphones/KingKong-mini-2 and a "pro" version: https://www.cubot.net/Smartphones/Kingkong-mini2-pro jaclaz

Check also here: https://github.com/KunYi/WDK_DDKArchive/releases jaclaz

You will need to use (and peruse) the Wayback Machine for most of the given links. For those where a filename is provided, usually a google search gives some results. It is of course a hit and miss game, and YMMV. jaclaz

Check here for the old ones: https://www.mdgx.com/add.htm#DDK jaclaz

Hey peeps, you seem like not having noticed how this thread is 8 years old, the original problem was presumably solved (or not solved) a loong time ago. It makes (IMHO) very little sense to reply to such an old thread, if there is something new (be it a problem, a question, whatever) it would be better (still IMHO) to start a new, specific thread. jaclaz

Very inconvenient, and a vast disadvantage, unless you conceive verbose lipograms in v. Have you tried the keyboard (and receiver ) on the other Windows 7 computer? And viceversa tested the other computer (cabled) keyboard on the one where the wireless is missing the v? Would it be possible that you or some programs remapped the v key to *something else* or plainly "killed" it? Check the Registry for anything "strange" in "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout" https://isenselabs.com/posts/keyboard-key-kills-and-remaps-for-windows-users I have seen reports of issues where different keyboards/IME are installed, but those should affect c, v and h keys (and possibly also t): https://answers.microsoft.com/en-us/windows/forum/all/chv-keys-fail-due-to-windows-ime/1dca583f-5b67-4095-bcc4-d1713587e7a2?tab=AllReplies#tabs In some cases, some fidgeting with the right Windows key may help, if you have installed some version of Office, it seems like in some cases it is the ctfmon[1]: http://jamesisin.com/a_high-tech_blech/index.php/2008/03/keyboard-input-ignored-for-c-h-t-and-v-keys-in-specific-applications-only/ the above lists a number of possible causes though it seems like it is a rare bug across many Windows versions (at least XP to 10) for which a real cause and unique solution has not been found or documented. jaclaz [1] if needed: https://www.gerhard-schlager.at/en/projects/ctfmonremover/

@Molly Dawn JFYI, I would expect that in the 12 (twelve) years that passed since last post (before your reply) on this thread the OP has solved (one way or the other) the problem. jaclaz

For the record your friend jaclaz meant to point to the whole thread (as he actually did), not to your specific posts that are "latest" but that imply already some experience with the tools involved. jaclaz

The grub4dos (normal and for UEFI) is available already compiled on its github page: https://github.com/chenall/grub4dos/releases There are usually no issues in having a "base VHD" with the OS and another attached VHD with all the programs (though not all "portable" programs are really-really fully portable) As a side note there is a relatively new feature of grub4dos (for UEFI) that allows using differential VHD's, that probably would be what you want to achieve, a "base", immutable, OS (in a VHD) and everything else on a "child" VHD. But I believe you are wanting too much all together, IMHO you should start with a simple - surely working - approach first, to get the hang of tools and methods, try this thingy by Wimb: http://reboot.pro/index.php?showtopic=22621 jaclaz

No, he is writing from seniority on MSFN.org. Joined yesterday 9:42, 1 post (on this thread, at 9:43), and it is about how great Windows 11 is. jaclaz

Well Portuguese literature (among many actual masterpieces) originated the immortal "English as she is spoke": https://en.wikipedia.org/wiki/English_as_She_Is_Spoke and - though not proved - we might have been deprived of this: https://en.wikipedia.org/wiki/Dirty_Hungarian_Phrasebook particularly, the very common and useful sentence "My hovercraft is full of eels." would probably have never been coined, and "Please fondle my buttocks" would have been far less used. jaclaz

Good, everything is well that ends well. :) jaclaz

As a side note there are traditionally issues with the NUSB in case of non-English installs (or anyway non-matching-languages), you might want to try an alternative, simple, USB mass Storage driver, some info: https://msfn.org/board/topic/171620-usb-flash-drivers-for-98se/ If you installed a non-matching language version of NUSB, it is likely part of the problems. jaclaz

9x/Me will do: https://msfn.org/board/forum/8-windows-9xme/ jaclaz

Yep. Windows NT systems are set (I believe it is a manufacturer default since - possibly - after Windows 2000) to automatically reboot if an error is encountered. (this is profoundly and utterly wrong, a system should STOP in case fo error) The setting is in the Registry, in CurrentcControlSet, CrashControl. The 3.0 (or 3.1 or 4.0, etc-, it won't make a difference) PE is only the most simple/common way to edit that key value, the issue with doing that from another "full" OS running is only that (it may depend on the OS's involved, both the "running" system and the "target" one) is with permissions on the specific Registry hive/key (but as said there are tools/methods//workarounds), for all it matters you can use (if you are familiar with it) a Linux system via hivesx or whatever else you can use, even a hex/disk editor from DOS (but this latter would be tricky to say the least). And yes, Easy2boot allows to add PE's (I seem to remember both as .iso and as partition/disk image). But even a Windows install DVD is running a (minimal/primitive) PE, so if you can boot from such a DVD (or from it's image) that would be enough (Shift+F10, then run regedit.exe). You can also use (if you are familiar with command line) the Offline Registry Editor: http://reboot.pro/index.php?showtopic=18527 http://reboot.pro/index.php?showtopic=11312 usage is well described in one of Misty's guides: http://mistyprojects.co.uk/documents/offlinereg/offlinereg.htm Before, you, can use the Offline Registry Viewer: https://www.nirsoft.net/utils/offline_registry_view.html to make sure the key exists and it is 1 (if it is already 0, the reboot happens earlier) . Both should work just fine from your installed OS on the offline registry (your neighbour's hard disk temporarily attached). In any case, your mission (the goal), should you accept it , is to change a single byte value in the Registry of the failed system (any which way you can). jaclaz

From a PE3 you should be able to (a PE3 normally has SYSTEM privileges): 1) backup (make a copy of) the Registry backing files (just in case): SAM SECURITY SYSTEM SOFTWARE NTUSER.DAT and since Vista BCD 2) mount in Regedit the SYSTEM as (say) my_system and check hive: \SYSTEM\CurrentControlSet\Control\CrashControl (it won't be actually "CurrentControlSet", it will be either ControlSet001 or Controlset002, check which one in key \SYSTEM\Select) The value of AutoReboot should be set to 0 (to avoid automatic rebooting and thus stopping with the BSOD in case of error) If you have a PC running 7 or later you may be able to do the same, but likely you would have permission issues to change the value, you could use something *like* NIrcmd, PSexec, RunAsSystem or RunAsTI: https://www.winhelponline.com/blog/run-program-as-system-localsystem-account-windows/ https://github.com/jschicht/RunAsTI to start the regedit with higher privileges. Then reconnect the hard disk on the original PC, and try booting, two possibilities: 1) no change <- this would mean that the issue is in any of the earlier booting files/code (MBR/PBR/BOOTMGR/BCD/WINLOAD.EXE) but usually (not always) errors in these result in either a black screen or an error message (white on black) 2) you get a BSOD (white on blue) with a STOP ERROR <- post this to further troubleshoot jaclaz

If I may, there are many possible causes of this happening, Tripredacus checked one and then (IMHO mistakenly) stated "The issue is elsewhere". It is very likely that one of the updates of the (stupid) forum software is causing the issue, the "Oops! Something went wrong, Please try again" is the typical (stupid) error message (meaningless) that the board software produces, so definitely the issue/bug is on msfn.org, though I believe that pinpointing it won't be easy, over the years many similar issues surfaced, particularly with thread notification mails (that may or may not be related to confirmation ones). jaclaz

In case of need, besides the "without patch" one already linked to: https://msfn.org/board/topic/183753-windows-me-patch-for-dos-mode-is-incompatible-with-letter-assigner/?do=findComment&comment=1222058 MDGX has 4 patches listed (no idea what the differences are among them): https://www.mdgx.com/dos.htm#ME Maybe also this can be useful: https://msfn.org/board/topic/140391-windows-98-live-cd-project-update/page/4/ leading to: https://www.mdgx.com/newtip2.htm#EXIT As said, sometimes instructions/info from MDGX are not (to me) very clear, so some experimenting will probably be needed. About XMS/EMM386 (if needed) there is some new info here: https://msfn.org/board/topic/183250-how-to-disable-the-built-in-xms-driver-in-windows-mes-iosys/ jaclaz