jaclaz

The file format (i.e. them being one of the various .doc or .docx formats) is largely irrelevant, as there are many converters to plainer formats such as .txt or .csv(I have to guess Unicode as Swedish has a lot of "strange" characters), given the intended use, losing the formatting of the text might be not a problem (or it may be one, as usually bold and italic are widely used in dictionaries). The real issue is that if these .doc's are more "freestyle notes" than anything else it will be tough to write a program/script capable of separating properly the fields. Essentially a dictionary is structured as a two field database, term/definition or key/value, if there is a meaningful, possibly unique, delimiter between the two, importing/converting the files will be easy to script, still there wil be errors/edge cases and what not. Then, a dedicated "dictionary/lexicography" tool might be needed (example): https://tshwanedje.com/tshwanelex/ https://tshwanedje.com/tshwanelex/overview.html for editing/assembling/formatting. jaclaz

It has to be seen, of course, but the symptoms seem a lot like those of a defective PSU and/or of an issue with one of the disks. The idea - more or less - is that during boot all devices are powered at the same time and there is a "absorption peak" at the PSU. Even if hard disk motors are (should be) of types that minimize the initial start current, they will anyway need a supplemental amount of power when spinning up. In multi-hdd builds (with a much larger amount of disks) staggered spin-up is used normally, see: https://www.45drives.com/blog/storage/staggered-spinup-and-its-effect-on-power-draw/ Besides there could have been a problem on the bearing of the disk. Basically when a disk stays unused/not powered for a length of time, the bearing(s) of the motor (and platters) may be opposing a much higher resistance to initial spinning, thus attempting to draw much more current from the PSU, usually this condition is temporary and resolves by itself, as the lubricants/fluids in the bearings start heating and circulating again. I would test anyway the PSU, but the common, el-cheapo CPU testers around only detect (and/ or measure) the voltage on the various rails/connectors which may be just fine without load, but drop when the load suddenly increases so that test might not be conclusive.

You may also realize that you replied on an almost 21 (twentyone) years old post, and thus you have been automatically registered as a contestant for "The most late reply of 2024 award". jaclaz

Sure, if an authoritative source like that doesn't mention XP it won't work with them. The whole point is that the translation happens in the hard disk controller, the older OS's will only see 512 bytes sectors, some newer ones may be able to also see the underlying 4096 bytes ones (but they will anyway use the logical 512 bytes ones). The whole stuff was developed to maintain compatibility with older OS's and with BIOS (that actually *needs* the 512 bytes sectors to boot form a disk). XP can anyway access 4K sectors (but won't ever boot from one of them), very likely 2000 cannot. We have the working experience (thanks to Dave-H's abillties in choosing the most incompatible hardware existing) about a "queer" hard disk (and its external enclosure) that exposed 512 or 4K depending on the interface and at the time we put together a workaround, JFYI: https://msfn.org/board/topic/173265-formatting-an-external-drive-using-different-interfaces/ https://msfn.org/board/topic/173642-mkprilog-batch-to-access-a-same-disk-under-two-different-interfaces/ Anyway the clarification only about the term "cluster" that only appllies to file systems and their structure, not to the disks. jaclaz PS: only as a reminder, a "new alignment" partitioning scheme has very high probabilities of being corrupted by Disk Manager of XP (not the primary partitions, but the logical volumes inside extended). As long as you NEVER use the XP Disk Manager on that disk there are no issues: https://msfn.org/board/topic/176917-help-i-aligned-my-partitions-and-now-the-pc-wont-boot/

@Dixel Not really. Clusters are a feature of the file system and they represent a set of sectors of the hard disk, "physical clusters" do not exist.. The disk has only the sectors, that can be physical (actual size on disk) or logical (the size that is exposed to the OS or its driver). Older disks had 512 bytes sectors (physical) that were exposed as 512 bytes (logical) More modern disks have 4096 bytes sectors (physical) that are exposed (logical) either as 512 bytes (so called AF drives) or as 4096 bytes (so called Native 4K, still pretty much rare). AF disks have (internally, physically) 4096 bytes sectors, that are converted by the controller to 8x512 bytes sectors. jaclaz

Generally speaking access is denied should be actually called "insufficient permissions". These can be either permissions related to the file (so NTFS permissions on the file or the folder containing it) or to an operation performed on its settings (Registry permissions on involved/related keys). You should check both. jaclaz

https://h30434.www3.hp.com/t5/Desktop-Hardware-and-Upgrade-Questions/4-TIMES-BEEP-RED-LIGHT/td-p/7451727 Power supply or graphic card?

Whose source code? You posted in "Install Windows from USB" which hosts a few different tools by different Authors... jaclaz

Only throwing things on the wall and see if anything sticks but for what it costs I would try both: [Keyboard] kbdhid = "USB Keyboard",files.kbdhid,kbdhid USB = "USB Keyboard",files.kbdhid,kbdhid and: [Keyboard] STANDARD = "USB Keyboard",files.kbdhid,kbdhid kbdhid = "USB Keyboard",files.kbdhid,kbdhid USB = "USB Keyboard",files.kbdhid,kbdhid and see what happens, though I remember seeing a lot of people having issues with attempts to install 2K with only USB mouse and keyboard on more modern hardware. I don't think a "working for all" solution exists, maybe - if you *somehow* manage to workaround the error - some "fully unattended setup" you may get past the text mode and hve later in the GUI a fully working keyboard, but cannot really say. Search on the board for related posts by bluebolt and tomasz86, they did a lot of work attempting to workaround similar USB keyboard issues, maybe some of those posts can provide some inspiration. jaclaz

Maybe useful, maybe not: https://github.com/adang1345/PythonWin7 jaclaz

Well, you are missing a large number of settings then (not only the Administrative templates/System). Check that you have all the .adm files in the right directories, this experiment to add gpedit to Home edition - as a side effect - provides all the needed info: https://www.oocities.org/kilian0072002/GPEditHome.htm This is more or less how it should look

Not necessarily on that model, but sometimes leds blinking mean "cannot boot". Sometimes these bricked devices can be resurrected with some magic spells (actually fiddling with inserting the power supply, pushing the reset button in a certain sequence, etc.), since it costs nothing you can try: https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=98742 jaclaz

As I cannot see, as in the screenshot you selected just the "root" aka "Local computer policy". Open "User Configuration", then: Administrative Templates System Not that it will surely work, but it should be there. jaclaz

@Dave-H My XP system is in italian, so I cannot make a direct comparison, but the italian version of that thing is there allright in the corresponding path to: User Configuration Administrative Templates System The one you found is in a completely different path. jaclaz

@Dave-H There should be an option to disable that message, if you are running XP Professional you can use GPEDIT: https://techjourney.net/disable-unsigned-driver-installation-dialog-prompt-in-windows-xp/ jaclaz