jaclaz

USSR, last time I checked, was dissolved https://en.wikipedia.org/wiki/Soviet_Union https://en.wikipedia.org/wiki/Soviet_Union#Dissolution jaclaz

How would you rephrase (if you think it is needed) "one billion people have chosen"? https://blogs.windows.com/windowsexperience/2020/03/16/windows-10-powering-the-world-with-1-billion-monthly-active-devices/ also (IMHO) choosing != loving jaclaz

Vista and 7 (let alone 10) have changed a few things that make *somehow* more difficult (or however "different") to create drivers for hardware, so a lot of tools that are used in the manufacturing would need new drivers for the new OS's and possibly noone wants to risk production issues due to some possible bugs when they already have tested and working ones. A common example is those "manufacturer tools" for USB stick controllers, some need a dedicated driver to talk to the controller, and AFAIK those were made for XP and never re-created for later OS's. jaclaz

The disk (I believe you actually mean file system) corruption is "queer", whilst 95 A was different, both 95 B and C should have no real differences when compared with 98, regarding file systems and disk access, jaclaz

Check this here: Maybe it helps jaclaz

Try using this: https://rjnoe.home.xs4all.nl/0/pc/soft/win/setup/msbt95a.txt as a reference, it is a thoroughfully commented MSBATCH.INF example. I seem to remenber, but a lot of times has passed and besides my fading memory it could be related to 98/Me (instead of 95), that you need to modify MSDISP.INF. But wouldn't it be easier - since your "unattended" actually boots, though to a "different" video driver, to install the VBEMP driver via Runonce or however through a script after install/at first boot? jaclaz

Here it is: MSFN links translated (see converter in my signature): https://msfn.org/board/index.php?showtopic=90495 https://msfn.org/board/index.php?showtopic=112610 You'll need Wayback Machine for most of the other ones, particularly those in this post: READ ATTENTIVELY this: before anything else. jaclaz

Good , you are welcome. I checked the Wayback Machine copy: https://web.archive.org/web/20080111095518/http://www.msfn.org/board/WinRAR-SFX-Commands-t34343.html and the copy/paste of that works, so definitely is (stupid) board software corrupting the contents of the "CODE" box. jaclaz

https://aware7.de/en/blog/eternaldarkness-critical-vulnerability-in-windows-10/ The article provides some mitigation info, but the no compression is seemingly only working on the Server versions. jaclaz

It is well possible that the copy/paste (or even the original on MSFN due to a number of board software updates) is no good. Read this: jaclaz

Naah, no bags, let alone aplenty. Though we have saddlebags besides holdalls and carryalls (UMPTEEN of 'em). jaclaz

Yep, to clarify, the spammer sent PM's and the board sent notification of the (new) PM to the e-mail address, So, the e-mail address is not viewable/usable by the spammer (or by anyone else) directly, it is the board notification system that actually sent the e-mail. jaclaz

They are actually countless. jaclaz

Not necessarily, unless the chip itself is damaged, if the issue is simply a corruption of the contents it can usually be reprogrammed "externally", either through some manufacturer provision or with a proper programming tool see - only as examples - these: https://forums.lenovo.com/t5/Lenovo-B-and-G-Series-Notebooks/Unbricking-G580-after-BIOS-update-failure-Solved-Guide/td-p/3953208 https://www.chucknemeth.com/flash-lenovo-x230-coreboot/ Of course, if *something like* the first is available/possible on that Dell, it is easy/fast/cheap, if *something like* the second is needed, then it has to be evaluated if it is convenient in terms of time and money spemt for the tools. jaclaz

Maybe they were these; https://qemu-devel.nongnu.narkive.com/2tj5RqNp/es1370-problems-with-win98se https://web.archive.org/web/20060222083500/http://franklinschools.nls.k12.la.us/download/drivers/audiopci.zip 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