jaclaz

Related thread about CHKDISK issues (only to keep info as together as possible): OIS.EXE should be the Microsoft Office Picture Manager, I believe it is not in Office since Office 2010 version, so maybe you installed that (or an earlier version) or some other MS Office components of that (or earlier) version? jaclaz

IMHO: 110 F -> 43 C is already "warm" (but still fine) 127 F -> 53 C is definitely "hot" and the vibration is NOT ok. Depending on the specific model/make, and depending on your (temporary) setup those (higher) temperatures might still be fine, but normally a hard disk does not vibrate at all (or in a way that you can appreciate without touching it) unless maybe during spinup/spindown, in some cases when the drive is at speed you need to hold it in your hand and try turning it to feel the gyroscopic effect to understand if it is spinning or not. jaclaz

Good , now you should re-enable it and add the chkdisk to the list of exceptions/allowed programs, see: https://www.tenforums.com/performance-maintenance/129008-chkdsk-f-fails-unspecified-error-occurred-2.html#post1596216 https://www.tenforums.com/tutorials/113430-add-remove-allowed-apps-controlled-folder-access-windows-10-a.html jaclaz

Also a .ttc file is a sort of "compressed archive" of (more than one) .ttf fonts, ttc actually stands for True Type Collection, so you need a corresponding .ttc. Maybe you can try with MSYH.TTC? https://github.com/owent-utils/font https://github.com/owent-utils/font/tree/master/微软雅黑 No idea if it would work better (or work at all). jacla

There is a long thread on Dell's about this (or similar) model and these (or similar) issues, possibly depending on the actual firmware version: https://www.dell.com/community/Laptops-General-Read-Only/17R-7720-SE-Lost-BIOS-Access/td-p/4081838 though as always happens there is everything and the contrary of it, the consensus seems to be that removing the HD should work. Besides taking out the hard disk, more generally (official Dell support page) F2 must be "tapped like mad as soon as you apply power" (this is not exactly what they write but it better conveys the idea ): https://www.dell.com/support/article/en-ie/sln143038/access-uefi-bios-system-setup-from-windows-on-your-dell-system?lang=en jaclaz

Actually it can have a disk partitioned GPT style. At least according to the same people that call "boot" a volume that all the rest of the world calls "system" and viceversa[1]: https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/windows-setup-installing-using-the-mbr-or-gpt-partition-style Or, a partition type 0xEE in the MBR partition table is a protective partition type used only on GPT style disks. Firmware = BIOS or UEFI (or both) Disk partitioning style = MBR or GPT (but the GPT style also has a "protective" MBR) Boot = BIOS mode or UEFI mode jaclaz [1] BTW in that vocabulary volume is what most other people would call partition (and a few filesystem) and that is assigned (by the same good guys) a drive letter (BUT a volume label)

Download link: http://jfx.cwcodes.net/WinNTSetup/Release/WinNTSetup4.rar is working just fine now, at least from here. jaclaz

Yep, everything is good then . the 524225 was chosen to fill the disk to the brim, without taking into account CHS boundaries, but with the "right" 524097 the partnew coonversion is correct, good, it is the classic GIGO case, not a fault of grub4dos partnew. the use of :~ to get substrings is identical to the CMD.EXE (Win2K and later) expansion, as a rule of thumb a sequence of IF conditional executions is only "ugly", and usually slower in execution, but it won't actually make any difference in practice in such a small/simple script. And no, there is no actual *need* to use the same date/time algorithm as DOS does, as a matter of fact since the volume is in RAM, and you won't normally have two of them the serial/volume ID could be also be "fixed", but I believe that - to be on the safe side - it should be set to non-0 values as it is likely that before or later you will find some tool/program that for some reasons checks that and panics if it finds a 00000000. Good. jaclaz

Nice. JFYI, grub4dos batches support both decimal and hex values in variables, i.e.: set /a mynum=64 set mynum mynum=64 set /A mynum=64 set mynum mynum=0x40 set /a mydec=0x40 set mydec mydec=64 i.e. (example): if "%secclust%"=="\x40" set /a secpclus=64 if "%secclust%"=="\x20" set /a secpclus=32 if "%secclust%"=="\x10" set /a secpclus=16 if "%secclust%"=="\x08" set /a secpclus=8 if "%secclust%"=="\x04" set /a secpclus=4 if "%secclust%"=="\x02" set /a secpclus=2 could become: set /a secpclus=0%secclust:~1,3% About partnew not writing to cylinder boundaries, I am not sure what you mean? You give partnew command the LBA addresses and it auto-translates them to CHS values, maybe there is an issue with the used geometry? Or is it a bug (that needs to be reported to the Authors)? JFYI, and as a side-side note, if you want an entirely "kosher" filesystem. Volume ID/serial is not (entirely) "random" on FAT (DOS), see: https://msfn.org/board/topic/152097-on-superfloppies-and-their-images/?do=findComment&comment=973205 https://msfn.org/board/topic/152097-on-superfloppies-and-their-images/?do=findComment&comment=987748 https://www.forensicfocus.com/Forums/viewtopic/t=2134/ https://msfn.org/board/topic/152097-on-superfloppies-and-their-images/?do=findComment&comment=980297 jaclaz

"registering a .dll" may be different from "registering a .dll". In a nutshell a .dll may be : 1) containing NO registering info for Regsvr32 or equivalent 2) containing ONLY part of the full registering info for Regsvr32 or equivalent 3) containing ALL registering info for the FULL registering for Regsvr32 or equivalent Additionally another program may add or modify registry data related to a given .dll. So, unless a .dll is of type #3 above there is simply NO way you can "repair" its Registry info using Regsvr32 or equivalent. Hence the provided resources, containing the "standard" Registry entries for that particular .dll, try it and report: https://forums.majorgeeks.com/threads/ie-will-not-display-png-images.150568/ jaclaz

And - specifically - given the (hopefully already past) known issues of WIndows 10 with multiple monitors and DPI scaling they made the wiser choice. jaclaz

But before that, are you sure that the dll actually needs to be registered? Windows errors can be sometimes misleading, maybe is some other file that creates the issue. Can you provide some context? There is a known issue related to that file in combination with some Java programs/updates, maybe you are having something similar: https://windowsexplored.com/2012/01/09/the-case-of-the-ie-hangs-and-missing-png-images-or-killing-two-birds-with-one-stone/ This may (or it may not) be the fix you need: https://forums.majorgeeks.com/threads/ie-will-not-display-png-images.150568/ jaclaz

No, it is not at all "unique" Binary (actually hex) is a representation of values. What is used is bytes, that can have values between 0 and 255 or - in hex - 00 to FF. Bytes can be grouped in words (2 bytes or 16 bit values), long words (4 bytes or 32 bit values), quad words (8 bytes or 64 bit values) when they represent a number. Otherwise they are taken as single bytes. A subset of bytes value, 0 to 127 (or 00 to 7F or 7-bit values) are used to represent most common letters, numbers and symbols (and non printable "control codes"), according to ASCII: http://www.asciitable.com/ and values 128 to 255 (or 80 to FF or 8-bit values) represent "extended ASCII" i.e. additional letters and symbols. Then there is Unicode that uses a two bytes encoding: http://www.unicodetables.com/ (but the first 128 characters are anyway the same as ASCII) In the Registry the "binary" type of data corresponds to *any* number of hex bytes. These hex bytes may represent text or numeric values or *something else*. Only text represented as bytes can be read/translated back to text. As an example, check your HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices You will find there ALL and ONLY Reg_Binary keys. If you click on some of them, you will see how some of them (those corresponding to USB sticks or more generally removable devices, i.e. those beginning with 5C 00 3F 00 or 5F 00 3F 00) will be long and "human readable" in the pop-up modify value window, whilst those corresponding to partitions/volumes on internal hard disks will be shorter and (unless by sheer coincidence) not readable. This is simply because the former are text strings (encoded in Unicode) whilst the latter represent different data, namely the first four bytes are the Disk Signature and the other 8 bytes are a Quad Word with the offset in sectors to the volume beginning (in practice last three or four bytes will almost always be 00). jaclaz

The OOBEtimer key contains binary values, nothing that you can ever trasform into a "comprehensible string", unless - by sheer luck - those values are in the ASCII range of printable characters AND they are readable. Have a look at the value in Regedit, example: I don't think that "ÿÕqÖ‹joÕ3“ý" means anything. jaclaz

The blinking cursor - generally speaking means that the stick has some issue in its partitioning/format (typically a mismatch between CHS and LBA but also a mismatch with the geometry of the device). Try booting the stick on another PC, if it boots there, the stick (and its partitioning/format) is fine and you need to find out what settings on your new firmwatre allow to boot from it, there may be other settings that are in conflict. Historically there are BIOSes that simply won't boot from this (or that) code (as an example Insyde BIOS had issues with several grub4dos and syslinux versions), but it is strange that this (recent) Intel one fails with Rufus. jaclaz

XP (or its setup) is NOT bootable on UEFI. You need to find the setting (if any) in your firmware to activate CSM (Compatibility Support Module) or "legacy boot" (in other words: BIOS). jaclaz

Sure , the point is that a Win 2K may look like a Win9x but it is very, very different from it as an Operating System. For no apparent reason, an image video (no need for translation and worth more than one thousand words ): jaclaz

I believe you mean "it looks almost like it". jaclaz

I don't know, it is "queer" in the sense that no actual reason/cause for the behaviour (which is also seemingly not-so-common, but also not-so-rare) has been found (AFAIK). jaclaz

Maybe OT, maybe not, on other news: https://www.zdnet.com/article/windows-7-bug-prevents-users-from-shutting-down-or-rebooting-computers/ jaclaz

LOOONG shot, but maybe this driver can do something about it (or maybe not) diskmod.sys: http://reboot.pro/topic/9461-page-file-in-usb-hard-disk/?p=86619 mind you it could also make your system unbootable, so, if you wish to test it, be very, very careful. jaclaz

Sure , and wait until you find one where something (like not allowing to enter a number in engineering format) is by design, example : https://web.archive.org/web/20090626230528/http://support.microsoft.com/kb/135673 the motive: would be not as stupid as it may seem at first sight if not for the fact that anyone (in his/her own mind) would use the numeric keypad (and not the top row) when entering numbers. Or - IMHO even better - when Remove All Does Not Remove Everything (by design) https://web.archive.org/web/20080217232953/http://support.microsoft.com/kb/147373 jaclaz

Mtools can make larger volumes just fine. Of course you need the "right" version of mtools and the right command options, you seem like having the "right" version: http://reboot.pro/files/file/267-mtools/ http://reboot.pro/topic/14354-buidlingmodifying-floppy-images-with-mtools-as-replacement-for-winimageimdisk/ If you take the example "-f 1440"and use instead "-f 67000" it won't work because the "1440" is a known format, whilst "67000" is not. You know like: Here you will find a small batch which can be useful to understand (and make more explicit) the parameters involved: http://reboot.pro/topic/21664-makeiso/page-4#entry205455 jaclaz

Well, it depends. Extended partitions are intrinsically "safer" from some risks (when compared to primaries), as an example a (malicious) tool with the same capabilities of MBRfix (and no more) won't find the actual bootsector of the logical volumes so - in theory - can do less damages. On the other hand since logical volumes are addressed through a "chain" of EPBR's, thet are intrinsically "weaker", if any link of the chain breaks (for whatever reasons) you will have corruption (perfectly recoverable, still ...) A good (and infamous) example is attempting to manage extended partitions from Vista or later in XP. the good MS guys not only created the mess when "switching formatting paradigm", but also mis- or under- documented the issue and of course never issued a proper XP patched set of programs, again JFYI: http://reboot.pro/topic/9897-vistawin7-versus-xp-partitioning-issue/ http://www.dcr.net/~w-clayton/Vista/DisappearingPartitions/DisappearingPartitions.htm And not only, they also removed the KB that mentioned the issue (via Wayback Machine): https://web.archive.org/web/20080821212615/http://support.microsoft.com/kb/931854/en-us By definition, out of the four partition entries, only one can be active at any time, and only if primary, so it is implicit that any primary partition but one will be non-active. The (IMHO only) good news with GPT partitioning are that in GPT ALL partitions are primary and you have in practice no limit in the number of volumes (most implementations are for up to 128 partitions/volumes). jaclaz

Extended partitions have NOT (and cannot have) "drive letters" (as they are NOT "drives" NOR "volumes") MBRwiz is a wizard for the MBR, nomen est omen, it only accesses the MBR where there is NO info whatsoever about the logical volume(s) (if any) inside the Extended partition, which is BTW what I tried explaining in the previous post. I does anyway look in the Windows Registry to find the drive letter (and the label) of the drive(s) - please read as volume(s) it finds (in the MBR) To give you one of my (in-)famous layman examples , imagine that you have for some reasons a security camera reading the registration plates of vehicles passing by: 1st recorded plate is a car, AA123456, you can look up for the registration number and find out (say) that it is a 1989 Corolla 2nd recorded plate is a car, AB234567, you can look up for the registration number and find out (say) that is a 2010 BMW series 3 3rd recorded plate is a car, AC3425678 you can look up for the registration number and find out (say) that it is 2018 Range Rover 4th recorded plate is a lorry, BC 89765432, you can look up for the registration number and find out (say) that it is a 2006 Scania truck, a car transporter Now, would you be surprised that you cannot find which cars (if any) the last vehicle is transporting? If you want to check the start offset of logical volumes also you need another tool, PartInfo will do: https://www.terabyteunlimited.com/kb/article.php?id=288 https://www.terabyteunlimited.com/downloads-free-software.htm (but in this tool you won't see the drive letters, not for primary parttitons, nor for logical volumes) jaclaz