jaclaz

Good . I wouldn't attribute responsabilities to running this or that tool, this kind of issues tend to happen "just because", maybe defragging anticipated the failure of the disk by three seconds or by three years, you'll never know. jaclaz

Yep , there is not any "real" issue (or problem to worry about) but you actually stated you were not sure about using Windows 7 (actually the change in alignment happened in Vista) to partition the thingy. The amount of increased writes will shorten the lifetime of the SSD from (say) 10 years to (still say) only 8 years, but you will be having a new PC in 3 to 5 years anyway. The not-aligned status of the partition (or of the contents of the FAT volume, NTFS has not this issue) will slow down access and write times (not so much read ones), something that is noticeable on "slow" media (as USB 2.x sticks or external hard disks might be) but it won't be noticeable (short of benchmarking) on "fast" internal devices. As a matter of fact it is NOT a very good idea to partition "aligned" to MB on a system that uses Windows XP unless you are SURE that you won't have logical volumes inside extended OR that you will EVER use disk manager to change the active status of a partition, there is a known bug in Windows XP (at least 32 bit, cannot say if fixed on XP 64,which is actually more "Server 2003") that can effectively mess up with the EPBR chain, to the effect that logical volumes will "disappear": http://reboot.pro/topic/9897-vistawin7-versus-xp-partitioning-issue/ http://reboot.pro/topic/9897-vistawin7-versus-xp-partitioning-issue/?p=124095 jaclaz

Well, then you formatted it "wrongly". Unless special provisions are made, the "normal" (pre-Vista) OS FDISK or similar partitioning tools create the "wrong" offset to the volume(s). AND if you are using FAT/FAT32 even using a proper alignment to the partition, the volume contents will come out unaligned. See: And: http://reboot.pro/topic/16775-discover-allocation-unit-and-other-information-of-ufd-under-windows/ http://reboot.pro/topic/16783-rmprepusb-faster-fat32-write-access-on-flash-memory-drives/ And: http://reboot.pro/topic/18182-uefi-multi-make-multi-boot-usb-drive/?p=209528 jaclaz

Well regsrv32 is a way to (re-)register the executable in the Registry, though it didn't work for you I doubt that even if it ran it would have changed anything. The "No DOS or PE signature found. This is not a valid 32-bit or 64-bit Windows module." is "queer", the .cpl files are renamed .dll's (hence the possibility to run them via RUNDLL32), that DW should "understand" just fine. It should mean that *somehow* the actual timedate.cpl is corrupted. I just checked on an old ME install disk I have (it is inside \win9x\WIN_9.CAB\) the file there is 36864 bytes in size, dated 2000-06-08 and - once extracted - opens just fine in Dependency Walker. (this is an English version, I don't think I have handy an Italian version, that may well have different date/size, to check it) In any case, if you open it in *any* hex/disk viewer/editor, its first two bytes should be (regardless of the version) the "normal" DOS signature of 4D5A or "MZ": https://en.wikipedia.org/wiki/DOS_MZ_executable jaclaz

What happens if you: http://www.tburke.net/info/rundll.htm run from a command prompt window: RUNDLL32 SHELL32.DLL,Control_RunDLL TIMEDATE.CPL,@0,1 It is possible that the actual timedate.cpl is just fine but *something* has happened to one of its dependencies, you might want to try tracing it in Dependency Walker: http://www.dependencywalker.com/ jaclaz

The link I posted earlier says that it is possible to use the XP Mode on 32-bit Windows 7. What I don't know the XP mode works on a 64-bit Windows 7 in your case. Why don't you simply try it? You can downoad it from MS: https://www.microsoft.com/en-in/download/details.aspx?id=8002 Instructions/tutorial: https://www.sevenforums.com/tutorials/8247-windows-xp-mode-install-setup.html It is also possible that you could run a "full" Virtual Machine (running XP) inside Windows 7 64-bit, but then it has to be seen if there is a "pass-through" USB provision and if it works with that scanner (it may work for HID and Masss Storage devices buit not for Scanners/Imaging devices ). jaclaz

Not necessarily Windows 8.1 related, but speculatively .... : https://www.zdnet.com/article/all-intel-chips-open-to-new-spoiler-non-spectre-attack-dont-expect-a-quick-fix/ jaclaz

No actual need of a dial tone (as already stated in one of the given threads). Of course, if you want to dial a number, you need *something* understanding the number(s) and redirecting the "call" to the destination (and powering the - internal only - phone line). And yes that is a (minimal) PBX. You can usually find simple. working ones with 4/6/8 internal extensions for a few tens of bucks or even less if you find a working used one. Or if you have an old PC (with a PCI slot) just get a FXO card and put together an Asterisk system, but it is way overkill. Making a completely DIY one is possible (and not particularly complex, if you want/need just two extensions). Example: https://www.instructables.com/id/Homemade-Intercom-PBX-With-GPIO/ but it makes little sense if not for the fun of soldering together some good ol'school electronics. jaclaz

Are the doctors and nurses actually curing them or only providing compassionate care and euthanasy? jaclaz

Had to happen before or later, magic spells applied to Windows 10 Updates: https://www.theregister.co.uk/2019/03/01/slow_ring_windows_10/ OK, you may not believe El Reg, but here it is the original: https://blogs.windows.com/windowsexperience/2019/02/20/announcing-windows-10-insider-preview-build-18342/ jaclaz

Just in case: jaclaz

Another possibiliy (this can surely be installed/uninstalled) on the fly is to use good ol' MS VSS SDK driver. http://reboot.pro/topic/6492-virtual-storage-driver/ The download is a mass of bloat (around 23 MB) but what you really-really need is just three files: virtualstorage.sys (58 KB, the driver) virtualstorage.inf (2 KB, the install info) vstorcontrol.exe (42 KB the command line tool) In a nutshell (example): C:\VSS\VSS2>vstorcontrol install Removing all virtual drives Installing Virtual Bus Driver... Succeeded C:\VSS\VSS2>vstorcontrol create cd-rom -image C:\downloaded\Ylmf_OS_3.0.iso Virtual Storage v5.2 Build 3790.1208 Creating drive backed by C:\downloaded\Ylmf_OS_3.0.iso ... Waiting for drive initialization............... Drive : \\.\Cdrom4 Drive ID : {5E3FEF3D-3910-11E9-B0E3-001FC6BB76CE} Type : CD-ROM Size : 676MB 1 volume(s) on this drive: \\?\Volume{5e3fef3e-3910-11e9-b0e3-001fc6bb76ce}\ F:\ C:\VSS\VSS2>dir F: Il volume nell'unità F è Ylmf_OS_3.0 Numero di serie del volume: 4095-D7B3 Directory di F:\ 20/04/2010 10.28 <DIR> .disk 31/05/2010 12.05 211 README.diskdefines 31/05/2010 03.48 4.055 Readme_en-US.txt 31/05/2010 03.48 7.558 Readme_zh-CN.txt 31/05/2010 03.46 7.558 Readme_zh-TW.txt 18/05/2010 08.37 144 autorun.inf 31/05/2010 11.54 <DIR> casper 06/04/2010 21.23 <DIR> install 31/05/2010 08.52 <DIR> isolinux 31/05/2010 12.05 4.204 md5sum.txt 06/04/2010 21.23 <DIR> pics 27/05/2010 01.06 <DIR> preseed 22/05/2010 10.23 1.473.629 wubi-hd.exe 17/05/2010 09.50 1.473.237 wubi.exe 8 File 2.970.596 byte 6 Directory 0 byte disponibili C:\VSS\VSS2>vstorcontrol remove F: Virtual Storage v5.2 Build 3790.1208 Removing... Drive : \\.\Cdrom4 Drive ID : {5E3FEF3D-3910-11E9-B0E3-001FC6BB76CE} Type : CD-ROM Size : 676MB C:\VSS\VSS2>vstorcontrol uninstall Removing all virtual drives Uninstalling Virtual Bus Driver... Succeeded but also: C:\VSS\VSS2>vstorcontrol install Installing Virtual Bus Driver... Succeeded C:\VSS\VSS2>vstorcontrol create cd-rom -image C:\downloaded\Ylmf_OS_3.0.iso Virtual Storage v5.2 Build 3790.1208 Creating drive backed by C:\downloaded\Ylmf_OS_3.0.iso ... Waiting for drive initialization............... Drive : \\.\Cdrom7 Drive ID : {5E3FEF3F-3910-11E9-B0E3-001FC6BB76CE} Type : CD-ROM Size : 676MB 1 volume(s) on this drive: \\?\Volume{5e3fef40-3910-11e9-b0e3-001fc6bb76ce}\ F:\ C:\VSS\VSS2>vstorcontrol uninstall Removing all virtual drives Uninstalling Virtual Bus Driver... Succeeded BTW a good thing is that this driver does provide (while mounting the cd-rom) a tooltip on the application bar, like "Found new hardware looking for driver", "Found new hardware CD-ROM", "The new hardware installed correctly and is ready for use" Though when you uninstall/remove the device you have a message "You can now remove the CD-ROM" that may confuse the final user. jaclaz

No. This has seemingly not passed through. If you want to mount a .iso (or any other kind of similar image) you need a driver. The driver needs to be installed. (this is not up to debate). So what is needed is at the very least BOTH the driver file (.sys) and the .exe (command line tool) at the very minimum, then there is generally[1] the need of either a .inf or of a .reg file to actually install the driver. Honestly I cannot remember if a reboot is really-really needed for filedisk (I tend to believe it is not really required for the basic functionality needed but it needs to be checked by experiment), you might need a "helper" to install without rebooting, see the (already given link, where a few examples are posted): https://msfn.org/board/topic/38118-filedisk-virtual-disk-driver-for-windows-nt2kx/ BUT this is still available via Wayback Machine: https://web.archive.org/web/20061026071810/http://www.benlaufer.com/2006/04/24/filedisk-ua/ and it seems to me like it doesn't do anything particular about the install. As well the "complete" package is still available here: http://www.jeffothy.com/weblog/filedisk-iso-mounter/ (of course you will need to strip out the extension .dll) About the 7zip SFX there is no particular issue with setting a path in a SFX, it is a bit of time I don't fiddle with 7zip SFX, but you can use the excellent: https://sourceforge.net/projects/s-zipsfxbuilder/ to easily build a SFX with the modified module by Oleg Shcherbakov (which has a number of handy additions to the "normal" SFX module). In it the same path where the SFX is is simply (no use of "temp" directory): InstallPath="%%S" (of course this needs to be on a read/write location) jaclaz [1] Some drivers need not this as they are (smartly) coded to have these internally to the.exe and also sport "telescopic" commands, a good example is Ken Kato's VDK (which is not suitable for your use as it mounts .img (or .img+.pln) and not .iso

Yes and no. Meaning that you need to install the service anyway. (you will need to modify the .inf file besides the install.cmd) Then you can well start it via command line (and also mount/unmount etc. via command line only without using the control panel app - that you won't install). As well you can avoid installing awealloc as you won't normally use/need it. Still, if all in all you: 1) do not *need* the Control Panel app 2) only use it to mount a CD/ISO image It will be simpler to install Filedisk: http://www.acc.umu.se/~bosse/ you should be good to go with Filedisk 15 or 16 (besides later builds): http://www.acc.umu.se/~bosse/filedisk/ On the other hand, if you want a "portable" GUI tool, get either the original MS Virtual CD Control: https://www.microsoft.com/en-us/download/details.aspx?id=38780 or the portable WinCDEmu: http://wincdemu.sysprogs.org/portable/ jaclaz

You could use XP mode seemingly: https://www.w7forums.com/threads/twain-driver-canoscan-d646u-ex-for-windows-7.8831/ but it has to be seen if that works on a 64 bit OS. There is a Commercial tool, Vuescan, however: https://www.hamrick.com/ there is a free trial, at 40/80 bucks isn't the cheapest software around, but if it works (on the specific scanner) it might still be worth it. jaclaz

Well, your case is border line with the XYZ problem (or the chocolate covered banana ), it happens very often, and to many people don't worry , JFYI it is "coded": https://jdebp.eu/FGA/put-down-the-chocolate-covered-banana.html In this case the original tool did make what was expected but due to a number of other complications the given alternatives ar simply "better", jaclaz

Well, if you like to call that "normal" it's fine, but still it isn't "normal". Is it not that you are in one of the conditions seen here? https://web.archive.org/web/20090331144811/http://support.microsoft.com/kb/831374 Running vrfydsk could be a good idea: https://www.microsoft.com/en-us/download/details.aspx?id=17657 jaclaz

I like "Joe" . It is simple and short enough, a lot less pretentious than "Navigator" or similar, and I cannot remember any other browser with a similar name. To be fair I wouldn't have disliked "Matt", but besides the risk of a legal battle on the property of the name, the double T could cause spelling errors, and the possible interpretation as "not-glossy" wouldn't have been nice . jaclaz

You'll have to concur that "anything else" is easier to make a reference to than: "cf69fed1697d94a058f6074ab55fd6094a200a3ec1af1e806fe537f1d115c2d283f7a083fdcb157a2abe0fda98d74f3b31ca0484aa803e48177dbb53eb1cdd34 or tVnRIF7Nvg4Ywlcv4zUffArn+LyLpeCPezvyqEXTw2RF5gU1skMG87JFy0KiaPVy". And I am not discussing your freedom of naming things , only highlighting the risk of you being sued, from what I understand, the usage of "boc" instead of "BinOC" is seen by the Trademark holder as a problematic misnaming/wrong short naming. jaclaz

Just saying ... https://www.zdnet.com/article/windows-10-new-study-shows-home-edition-users-are-baffled-by-updates/ https://insider.windows.com/en-us/articles/were-listening-to-you/ Mission Status: FAILED jaclaz

How come it is "boc-uxp" (and not "BinOC-uxp")? jaclaz

It must have been a tough life with an OS (or given set of programs) that constantly trash your NTFS. No, it isn't "normal", it happens, but it shouldn't and surely it shouldn't happen often. @luweitest Good. At least now there is (or should be) a "solid base". Let's see what SFC comes out with. jaclaz

Sure, "boc" is the "shorter" (all small letters) form. jaclaz

Then you can use IMDISK just fine: http://reboot.pro/forum/59-imdisk/ http://reboot.pro/topic/2072-imdisk-by-olof-lagerkvist/ Or for XP also good ol' Filedisk would do nicely (as it did since 2005 or so and until IMDISK became prevalent): https://msfn.org/board/topic/38118-filedisk-virtual-disk-driver-for-windows-nt2kx/ jaclaz

Only to play devil's advocate , here it is a practical use: http://reboot.pro/topic/21851-boot-winxp-x64-in-efi-on-thinkpad-x220/ jaclaz