jaclaz

@drugwash JFYI: http://clickykeyboards.com/ They removed the logo (that is still available through Wayback Machine): NOT cheap, still ... jaclaz

Add a wild card after the hyphen. http://www.msfn.org/board/topic/0-*/?do=findComment&comment=1131594 If only they could stop "improving" the board ... jaclaz

Let's call that voodoo, and let's go on [1]. jaclaz [1] I won't discuss how not only a different southbridge and disk can change results, but also the phase of the moon or a concurring solar storm may have affected the results of the experiment.

Well, jaclaz thinks that the thing the OP is wandering about is not that much "original", and related info (if interested) can be found with very little difficulties, you know, like looking for them. Namely: http://windowsitpro.com/windows/how-do-i-install-disk-larger-8gb The basic issue revolves around the Int13 extension AND there is also a limitation in the NTLDR, so you will need to use a 2K or XP one (coupled with the corresponding NTDETECT.COM), but - as a matter of fact - it is a non-problem, or - if you prefer - we are talking of solutions in search of problems. Ok, this is not-so-trivial to find : https://web.archive.org/web/20121017215600/http://nu2.nu/fixnt4/ Still, a normal install of a FULL NT 4.0 is around 200 Mb. It is STRONGLY advised (by me, but I simply follow the advice by Gilles Vollant and the actual way NT 4.0 was designed) to install the Operating System in a Logical Volume inside Extended and have a small primary partition for just the boot files (and/or DOS/Win9x). In the real world, you won't EVER *need* the OS volume to be bigger than (say) 2 Gb or so, 8 Gb is much, much more than enough for any possible use of NT 4.0 (of course you keep your collection of DVD's and more generally data on a data volume), here is a complete guide, including the use of the UNIATA driver, that will allow to have also larger than 128/137 Gb/Gib disks accessible: http://nt4ref.zcm.com.au/bigdisk.htm jaclaz

Well, but a .SWM opening (or failing to open) in 7-zip is not a real test of *anything*. What happens using normally imagex (which is what is suggested/explained in this thread)? Also, depending on the OS you can use, maybe DISM would be a valid alternative. Or, you could try Wimlib (namely Wimlib-ImageX): https://wimlib.net/man1/wimlib-imagex-export.html to export the split into .swm's image into a "monolithic" .wim, before despairing/panicking. Semi-random thought, what if you make a copy of PREINST.swm and rename it (the copy) to PREINST1.swm? These are multi-part archives and the inbuilt 7-zip naming convention may play a role in this. jaclaz

Yes/No. Be VERY aware of the possible issues with NTFS version in case you are dual booting with (or however accessing the disk through) a newer NT OS, such as 2K or XP: Also (only seemingly unrelated): jaclaz

More than the ostrich algorithm (which is usually a very good approach, BTW), there is here the possibility (at least according to Ockham Razor ) that simply too many observations are changing the data: https://en.wikipedia.org/wiki/Observer_effect_(physics) It is more a state of mind than something objectively measurable, in a nutshell, if it works, it works (and just leave it working as is or "if it ain't broke, don't fix it"). jaclaz

WHICH PE? jaclaz

transmeta.sys? Maybe crusoe.sys (which is alright in WinFlp and is referenced fine in cpu.inf). I suspect that the issue may be connected with /something else* or with the "strange" way WinFlp is installed. jaclaz

Just for the record: http://www.msfn.org/board/topic/175318-new-forum-how-tos/ http://www.msfn.org/board/topic/175318-new-forum-how-tos/?do=findComment&comment=1120559 Grofluigi has a possible explanation (at least limited to Opera) in the following posts. jaclaz

0x00000019 should be "Bad Pool Header", it is usually connected to programs (or drivers) loading into/scanning memory (Mbam, being an antimalware very likely does this) and leaving the system used memory in an inconsistent state (usually this happens because the process conflicts with *something* else, like - say - a newly installed driver), but it can be also due to "strangely faulty" RAM, so it is a good thing that you checked it and it came out as fine . jaclaz

Well, then it is another bug , different from the mentioned one, possibly limited to the install routine, or maybe triggered by having all four MBR partition table slots "full" with primaries . Lots of people dual boot XP and Vista or 7 using two primary partitions (one for each operating system) using the Mb alignment and something similar has never been reported AFAIK, and - on the other hand - MS has a dedicated tool to create a Mb aligned (actually a 4 Kb which is all that is needed, but however non-cylinder aligned) partition: https://technet.microsoft.com/en-us/library/bb643096(v=exchg.80).aspx jaclaz

The "last loaded driver Mup.sys" hang suggests an issue with the install, that error is typycal of issues with the filesystem, but of course it can also be actually a driver issue. Can you boot a PE of some kind on that machine? (or load the recovery console?) The first thing to do in these cases is usually a chkdsk. This is (thanks Wayback Machine) a good page that lists "common" causes: https://web.archive.org/web/20160407090809/http://www.aitechsolutions.net/mupdotsysXPhang.html The processr.sys is anyway not the issue, at least in a backup I have of the Futro it is the same file as the "normal" XP SP2 one, like the one in WinFlp. jaclaz

Naah, it's the same setting, the difference is that knowing directly the involved Registry key allows you to do it also when offline (let's say an unbootable system), by directly editing the Registry from a PE or another bootable instance of the OS. BTW it can also be reached through F8 "advanced settings" when booting. jaclaz

Well, just in case, there is a setting that allows you to have the computer actually STOP on STOP errors, unlike the "Autoreboot (before anyone has time to read the STOP ERROR. let alone take a note of it)" action that the good MS guys in their wisdom set as default in XP and later. http://www.pctools.com/guides/registry/detail/229/ jaclaz

I used to have a Fujitsu Siemens Futro (220 if I recall correctly) with a Transmeta 5800 and it worked nicely with XP (SP2 for the record). The POSREADY 2009 IS EXACTLY the same as a "normal" XP, so no issues there that I can see, JFYI: WinFLP may be another thing. Which EXACT, SPECIFIC BSOD STOP ERROR do you get with WinFLP? Very likely it is just a matter of a missing driver (that should be possible to "add" to the install). jaclaz

Dibya, you NEVER suggest someone to reinstall the OS, not before having tried ALL the tricks of the trade (+1), unless you are of the Microsoft support line or a MS MVP on the Microsoft board of course . @glnz With all due respect , as often happens you report vaguely a "too wide" issue. WHICH (EXACT, SPECIFIC) BSOD STOP Error(s) did you have? WHICH (EXACT. SPECIFIC) "bunch of files"? WHAT makes you think that "turning off" any .sys file will change the situation? <- to clarify, IF the BSOD's STOP errors mention a specific .sys file, then MAYBE that specific .sys file is connected to the issue (or maybe not). If the disk passes the Seagate test, most probably it is fine and not part of the issue. About your NTboot.log, there is a whole load of third party files in it (that obviously have nothing to do with the POS updates). Now, we could blindly suggest you to uninstall a given third party (and to that you will object "no, that cannot be it, I had it running since xxxx without problems" or "no I cannot do that, as I *need* that software") , but this thread will become very long and probably won't provide a real solution. The alternative being that you stop fiddling with the system (you'll have to take a definite position, you EITHER consider yourself an "advanced enough" techie and then CAN fiddle with the system, OR you consider yourself a "normal real estate lawyer" and refrain from doing that ) and - next time you get a BSOD, you post the SPECIFIC, EXACT information about THAT BSOD, and we will try to find out the cause of THAT one. Once (hopefully) we'll find the cause of that one (and fix it), we'll see, if there are no more BSOD's, or, if there is a new one, we will tackle that one... Unfortunately "magical" solutions (good for all) do not really exist (unless you consider re-installing from scratch a solution) and problems need to be tackled one by one, it takes time, but usually they can be solved. jaclaz

I will try to re-type this very slowly. Primary partitions are NOT affected by the bug with Cylinder vs. Mb alignment, ONLY logical volumes inside extended may be. jaclaz

Well, it's seemingly not a "dongle" it's just a "normal" USB stick, made out of a controller and a flash memory (possibly with very little capacity). Most "normal" USB sticks have controllers capable of making two LUN's (if you remember the good ol'SCSI days), one a CD-Rom like device and the second a "hard disk like device", and of course just the first (your case) or just the second (like 99.99% of USB sticks you can find). You don't need a soldering iron at all, you need to identify the controller make/model AND find the corresponding suitable "Manufacturer's Tool" (which may or may not be available). A good starting point is (Russian, but not bad at all through Google Translate): http://www.usbdev.ru/ jaclaz

Well, unless they are completely demented (in which case you shouldn't allow them physical access to your machine ) they should be able to understand that when they click on something supposed to run a program, and nothing happens, *something* is blocking the execution of the program anyway, what they won't get to know is that this happen because of a set group policy and will be puzzled by the cause. All in all sounds more like a prank than anything else. jaclaz

So, if I get this right, you allow physical access to your computer to other people and when they try to run applications you prevent them from doing that? They will double ckick on links, exe's and shortcuts and nothing will happen? Anyway, clickoff should be able to "catch" that popup window by the text contained in it. jaclaz

Good. I don't know if there is a way (maybe a manufacturer tool/utility) to test the functionality of a SSD (and/or to *somehow* regenerate it). In theory the controller has a map of "defective" sectors and these are re-mapped to good "spare" ones when the SSD is manufactured, but it should be possible to re-test and re-do the mapping also "at home" and there should anyway be a method to verify the functionality of the SSD or it may be hard to get a RMA for it, and it should be around 250 bucks, so not exactly "expendable". jaclaz

You will need a bootable *something*, like a PE, liveCD or bootable stick (it is not a good idea to wipe the base structures of the disk from which you are running the OS), a common way is to use dd (or a port of it) to directly write a file made of 00's to the very beginning and the very end of the disk. There are also usually manufacturer tools that can do the same (like Seagate, Western Digital, etc.). Still, what is perplexing is that you are having some different BSOD Stop Errors, and this would point (also since you said you just built the PC) more to some *random* hardware error. jaclaz

As said there are likely tens of similar programs, but you seem after a totally pointless use, I will repeat myself, if you block something, it will be NOT executed AND the NON-execution will be notified to the user through the popup window, what is the ACTUAL need to hide that notification? Please answer the above question, try to explain the actual use that you have imagined for this feature, as is your question makes very little sense (at least to me). Just for the record (and AFAICT) the clickoff is "better than" or "same as" Buzoff, with a net saving of around 20 bucks and some 3 mb's and it is - to say the least - "queer" that it cannot "catch" that error message, as it can also monitor for text contents of the popup. jaclaz

Looong shot (and not really-really a video player) but what happens with VrtualDub? http://www.virtualdub.org/ More ideas (Real Player 8 shouldn't be too shabby ): http://nt4ref.zcm.com.au/media.htm As per the above the only working VLC version (latest) is 0.8.6h. http://filehippo.com/it/download_vlc_media_player/4246/ jaclaz