jaclaz

Actually you don't want a " too soft" eraser. You want a (very mildly) abrasive one, the best being one of those (that you can find not easily anymore anywhere ) round "wheel" ones once used for typewriters. This sort: https://contrapuntalism.blog/2016/01/21/faber-circular-erasers/ traditionally the white ones are softer/intended for pencils, whilst the red and blue ones are a bit stiffer and more abrasive (intended for ink/typewriter), Nowadays the more suitable ones are this kind of bicolour ones: http://www.foxystudio.com/wp-content/uploads/2013/09/187040_1.jpg and you want to use first the blue side and then the softer pink/red side. jaclaz

Or, in nutshell, how can we turn the good ol' Windows 7 into a SAAS ? Let me think ... jaclaz

I don't get it. It is not a "blank embed", it is the SAME link (and it is clickable), that the stupid board software insists on automagically transform into the stupid preview unless you are fast enough to tell it explicitly to "display as link instead", here are two times the same link: The above has been magically transformed, the below one is the same copy/paste BUT clicking on "display as link instead": https://msfn.org/board/topic/137714-install-xp-from-a-ram-loaded-iso-image/?page=8&tab=comments#comment-895119 It is entirely possible that some of the XP updates post 2009/2010 fixed the issue, good to know that it works on your machine/OS , as said it depends on OS (and possibly also on the specific devices, I remember the behaviour to be faulty also with USB ZIP disks besides my multimedia card reader). jaclaz

@jumper The given example: https://msfn.org/board/topic/137714-install-xp-from-a-ram-loaded-iso-image/?page=8&tab=comments#comment-895119 is EXACTLY about that FOR loop, BUT (again it depends on the OS) that (the IF EXIST) might fail if some devices (that get a drive letter even if "empty") are on the machine. jaclaz

It depends on the environment. The easiest would be to use a "tag" file of sort, Then you simply find the volume which contains this "tag" file, let's say it is a 0 byte file named thisisit.tag. The problem might be that in order to find the volume you need to list or check the contents of all volumes, and depending on the speciific OS there may be issues with devices that have been assigned a drive letter but that do not really "exist", a classic example is (again it depends on OS) those "media" readers (internal but USB connected) that sport a couple USB ports, a SD and a CF reader, etc. and with volumes with thousands of files there could be time issues. See starting from here for a few posts: Here is another approach (due to some issues in the nth board update the formatting of CODE contents has been ruined, so you will need some patience, after having done copy and paste to rebuild the actual batches proposed): In your specific case, I would rather check the Registry and get the drive letter associated to the Disk Signature and Offset of your USB stick, however (assuming that you are not going to change either). But this depends again on the environment and the device, you cannot use this method if the device is removable (or you can use it only to exclude non-removable devices). jaclaz

Then, welc jaclaz

JFYI: Why You Shouldn’t Use Firefox Forks Like Waterfox, Pale Moon, or Basilisk https://www.howtogeek.com/335712/update-why-you-shouldnt-use-waterfox-pale-moon-or-basilisk/ Brought to you by this guy: https://www.howtogeek.com/author/chrishoffman/ jaclaz

http://chomikuj.pl/Kot_Maciek/Programy/Hmonitor+4.1.4.5 Not the best possible source (site Is in Polish, and downloading the whole archive seems like needing to download a specific program, though single files seemingly work fine), still ... jaclaz

If you want something that ONLY works on Windows 10 ... So, no, at face value it is terrible, possibly the worse idea that a developer could come up with (IMNSHO). When (if) it will be compatible - at the very least - with Windows 7 (better if with Vista AND XP), then we may start talking about it ... ... and you really needed to revive a 13 (thirteen) years old thread? jaclaz

Gratuitious note at best. jaclaz

Not what you asked, still ...: https://openmeetings.apache.org/ jaclaz

You posed the question in what appears (to me) a strange way , it is not a double or nothing (Acrobat Reader DC - IMHO a stupidly large mass of bloat- or Sumatra - IMHO the most minimalistic reader) game, there are many free readers besides them, apart the ones embedded in Chrome or Mozilla. Only to give you an example, I normally use on XP the Foxit one (in a rather oldish version, 2.3 that however fits my needs just fine), but I am pretty sure that there are a number of other suitable softwares around. jaclaz

Quick recap: 1) if it is "LBA0", it is bricked 2) if it is "BUSY", it is bricked 3) if the BIOS sees it, possibly with its full capacity, then it is NOT bricked (anymore) The state in which it is is definitely "NOT bricked", but this doesn't mean that there is not some other issue (hopefully a small corruption that can be sometimes - but not alwasy - fixed ). See an example of success: and one of failure: In case, start a NEW thread asking for help to attempt recovering the partition(s) on the disk. jaclaz

From the link just posted to MDGX: Which makes a lot of sense, it is faster to load a single file (not compressed archive) than a number of files and the overhead of uncompressing on-the-fly the archive (single file) may make things slower, particularly with the limited amount of memory and CPU that was available at the time. But no, there is no particularly bad consequence, though "mixed mode" is risky, as a newer driver may be automatically replaced by an older version in some cases: jaclaz

Advised by whom? jaclaz

The VMM32 can ve unpacked and re-packed, still just in case: http://www.mdgx.com/98-3.htm Scroll down to "WIN98 VXD BUG": jaclaz

Naah, no bazooka, they will use a laser-guided Destructo-Beam, which is one of the best possible uses of .NET: http://www.toodarkpark.org/computers/humor/shoot-self-in-foot.html jaclaz

Usual reference to the "innards" of vmm32.vxd (in case it is useful): http://www.helpwithwindows.com/techfiles/vmm32.html jaclaz

Well, the real issue is that they call the horror they devised as "elegant", the C: (what an actual Microsoft Programmer would properly - please read as "improperly" - call "boot" volume ) is nothing but a conventional way to access a disk extent that they decided to "tag" - in order to keep compatibility with MS-DOS conventions - with a "name" or "drive letter" [1] [2] The whole concept of GUID for volumes (and the assignement through mountvol), set aside the actual way disk signature and offset/length of volume for drive letter assignment work seem like non-existing if you read the post (actually the needed clarification in answer to a very legit question since the actual announcement missed any of the details). jaclaz [1] And yes, besides multi-hard disks system they seemingly ignore also the concept of multi-partitioning/multi-volumes, for these new guys you seemingly should have only one accessible volume, called "C:", which BTW is also the negation of the ONLY (IMHO) real advantage of GPT style disks (apart the 4 TiB size limit that is a non-problem since SSD became common and it won't be one until commonly used SSD's will go beyond 4 TiB) which is that of having the possibiliy of having a virtually endless number primary partitions (i.e. without the risks connected with the EMBR chain neded for logical volumes inside extended) [2] only for the record, since NT 4.00 NO install of NT based system I ever did ever used C:\ as the drive letter for the actual "system" volume (the one that MS call backwards "boot").

Yep, that's a serious mis-representation, FranceBB has ONLY two machines with PosReady 2009 running. jaclaz

It's queer. Do check (with a magnifying glass) that the inside of the slot is clean, that pins are not bent and that the lever is not damaged. It is similar to this kind of lever/slot: https://www.compuram.de/blog/en/installing-new-memory-modules-a-short-guide/ right? The lever is self-locking, i.e. when you insert the stick, it makes pressure on the lower part of the lever and makes it close, it is possible that something prevents the stick from going "full in" (and thus locking the lever) or the lever (or the hole on which the lever pivots) is damaged. In theory the lever is more an "extraction" lever, i.e. the RAM stick should stay in place even if the lever is broken, but it is entirely possible that the slot pins are not (anymore) as "springy" as they should be. You can replace the lever (taking one from a dead motherboard), but of course you cannot easily replace the connector. The poor man solution is to wrap an elastic band around the slot, keeping the levers closed, but it is only temporary, as the rubber will soon "cook" itself and break. A more proper solution is (it depends on the specific slot, thickness of the ram module, etc. ) to build an external clamp of sorts. jaclaz

Wait a minute, The LoneCrusader/rloew patch linked to by dencorso: is intended to be run (among other options) from a bootable floppy, if getting the hard disk out of the laptop is complicated, why doing it that way? It would probably be possible to run it now or - even if it doesn't work - restart the install from fresh and install the patch during this new install. jaclaz

There has been a post today on blogs technet that could have been posted on April 1: https://blogs.technet.microsoft.com/filecab/2019/01/07/windows-10-and-reserved-storage/ In a nutshell, not happy enough with totally ruining Windows, in order to fix one of the issues/shortcoming of Windows 10 (and its stupid updates) they are going to ruin also NTFS: https://blogs.technet.microsoft.com/filecab/2019/01/07/windows-10-and-reserved-storage/ Besides the forced requisition of 7-10 GB of users' storage space (that may be debatable, but surely makes the Windows 10 install footprint some 30%-50% bigger, to the delight of anyone running it on small amount storage devices such as tablets or on devices with no replaceable storage) they are doing it using some form of changes to NTFS: i.e. basically to the only thing that is still (IMHO) "rock solid" and "time proven", with the additional benefit that each and every data recovery tool (and possibly even built-in tools like chkdsk and similar of previous versions of Windows - that may still access the same disk/volumes in multibooting scenario's will likely have issues). jaclaz

Hmmm. Let me see. Under Windows everyone uses Chrome or Chorome/Chromium engine based browser. (exception made for those insisting on using Mozilla Firefox, all in all a small amount of people [1]). Noone uses Edge. Whatever undocumented features of Edge (if any ) *somehow* facilitating MS operations is lost. The whole plan on world domination and stuff through the Windows 10 pushing is likely failing (besides the total defeat on phones) because even those that for one reason or the other are using Windows 10 ar not using Edge and nowadays a large part of the time spent on a computer is through its browser. Idea , let's make a new browser similar to or nearly identical to Chrome (possibly while keeping the same *whatever* undocumented features we like to have). Wait, this would mean actually writing lots of code, why not using the actual same engine as Chrome? jaclaz [1] and with the exception of a few old dinosaurs like yours truly that still use good ol' browsers (with some limitations).

... and remember that in the good ol'times the successor to the Sinclair ZX Spectrum was the QL, i.e. Quantum Leap, and it was actually for the time an incredibly good computer ... jaclaz