jaclaz

It seems like you are in the situation described (and hopefully solved) here: http://social.technet.microsoft.com/Forums/windows/en-US/05c15c0a-0ba0-4c09-8f1d-471352a43a56/windows-7-rc-wpa-and-wpa2-will-not-connect-with-any-router-for-lenovo-t60s?forum=w7itpronetworking i.e. you cannot find where to supply the WPA2-PSK login credentials? Or is the issue something else? Please try to describe your issue in more details.... jaclaz

Have you tried with "%L" instead of %1? I.e.: @="mplayer.exe" "%L" jaclaz

Good, I guess issue is solved. jaclaz

@dencorso To be fair, as-is the title explicitly forbids any reference to good ol' NT (4.00) , my bad jaclaz

What do you mean "mass partition"? You make a USB stick and you connect it to one machine and by sheer magic it partitions all of 250 of them at the same time or you insert the stick 250 times? I mean it is no tlike the USB will wear much, i.e. there is not much difference if it is 1, 2 or many laptops. Seriously , what do you really want to do? Really only partitioning them? Or partitioning the disk and formatting the created volume(s)? Or partitioning the disk and formatting the volume(s) and deploy/install an OS on the volume(s)? Are these laptops all identical? There are several (unofficlal) tools to create PE's, which "base" OS are you willing to use for the PE? Quick summing up: XP/2003-> PE 1.x Vista :ph34r:/2008-> PE 2.x 7/2008 R2-> PE 3.x 8/2012-> PE 4.x 8.1-> PE 5.x For a PE 3.x/4.x simplest/quickest way is to use the QuickPE project: http://reboot.pro/topic/18744-quickpe/ http://reboot.pro/files/file/340-quickpe/ or a MistyPE: http://reboot.pro/topic/18917-mistype/ though your report of issues with DISM may anyway affect it's creation. In it's simplest incarnation the QuickPE project does not make use of DISM, so it may work even in your setup jaclaz

Good. The actual tool can still be found here: http://www.pcwelt.de/downloads/KMCS-Registry-Compressor-Pro-4-5-starten-551580.html the download is actually the "whole" KMCS suite, which includes the Registry Compressor jaclaz

@Tremun, sorry, didn't mean to suggest to "freeze" your thread , only the speculations about what will happen to XP64 once the infamous April 8 will arrive. More in the sense of "whatever will be, will be, the future is not ours to see" than anything else. Back to topic, about chipset drivers, there are IMHO two points to consider: 1) is the chipset compatible with existing (not specific drivers)? 2) even if yes, how good will those non-specific drivers affect performance? If the answer to #1 is no, then you won't be able to even boot on that machine (or have stability issues, possibly even worse ). If the answer to #1 is yes, will the "legacy" (stupid definition, but is what is used - wrongly - in the industry) mode have a serious/noticeable performance drop? It is impossible to say right now. To give you an example, let's take an old OS and SATA drives. Notwithstanding what you may find here and there, when SATA came out (SATA I) the performances of a "new" disk drive on a machine with BIOS set in IDE compatibility mode was not in any noticeable way worse than that of the same machine with BIOS set in SATA mode and the "proper" SATA driver (and for that matter not even noticeably better than a comparable ATA 133/ATAPI 6 IDE disk). But, with faster disks, SATA II (and NCQ) the difference with IDE becomes more noticeable. jaclaz

Why don't you all put this topic in a "suspended" state and see what will happen on April 9th, 2014? I mean, at the time Jody Thornton started panicking/whining about the end of support of XP 64 bit the deadline was far in the future, but now it is just a coupe of weeks away. @Jody In any case, should the more optimist 5eraph's take on the matter be verified, you should know that support will end (for real) on 14/07/2015, and need not to make the same amount of posts revolving around this issue . jaclaz

Maybe it was added in XP (for folders) . I haven't a suitable 2K machine handy to check , in XP the setting should be: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\ Explorer\Advanced] "FolderContentsInfoTip"=dword:00000000 to disable and 1 to enable. jaclaz

Are you sure-sure it is a good idea to use a 9x driver on NT 4.00 Reverse translation of the quoted pseudo Italian (into pseudo English ) jaclaz

You see , I had told you. Seriously, now , it is a lot of time I didn't actually use filezilla, but I remember previous versions worked fine, maybe the good guys are - like a lot of other people - somehow forcing upon the users unneeded "betterings" that result in needlessly losing users. jaclaz

It is very possible that it just scans the "executables" or "apps". jaclaz

The question: comes to mind At first sight the "script" is at the moment a wordy way to run unconditionally just: SET _ScriptDir=%~dp0SET _ScriptDir=%_ScriptDir:~0,-1%START "Install" /WAIT "%_ScriptDir%\SRC\x86\pd_core_160.exe" /s /v"/qb /QUIET /NORESTARTwhich can been however simplified to: START "Install" /WAIT "%~dp0%SRC\x86\pd_core_160.exe" /s /v"/qb /QUIET /NORESTARTbut the script has nothing to do with the question asked, and without some info on this 2nd .exe, guessing it will be tough .jaclaz

The point is that you don't really-really have (anymore) access to the actual internal device on Android, see: http://www.msfn.org/board/topic/159227-does-xp-have-same-usb-mass-storage-driver-as-vista/ (seemingly unrelated) and: http://www.msfn.org/board/topic/162913-portable-devices-via-mtp-driver-in-windows-98/ Look in the linked to pages: http://www.jfdesignnet.com/?p=2291 and (the quintessence of the stupidity of the decision): http://www.androidpolice.com/2011/11/18/impromptu-qa-session-with-android-engineer-dan-morrill-brings-to-light-reasons-behind-galaxy-nexus-lack-of-usb-mass-storage/ Basically in recent Android versions there is not (anymore) the possibility of "exposing" the device as a "Mass Storage Device", but only as MTP/PTP (Media Transfer Protocol/Picture Transfer Protocol) unless you re-activate the feature, like (example): http://forum.xda-developers.com/showthread.php?t=2350542 which may (or may not) work on your particular device/version of Android (and AFAIK there are only ways to restore the Mass Storage accesss to the SD card, not to the internal storage), like (example): http://www.xda-developers.com/android/usb-mass-storage-app-for-recent-samsung-devices/ So, even if it would be possible to scan an "offline" Android system, it is now particularly difficult to have access to it via USB. Of course you could always do a "physical acquisition" of the internal storage (given that you have the appropriate tools and knowledge) and scan that, but it is not something "common" or "easy". jaclaz

I must admit that I cannot imagine this now. It would be good to have screenshots, video or something where I could see it. Possibly useful advice for slipr : http://www.msfn.org/board/topic/171205-licecap-useful-screenshot-to-animated-gif-recorder/ jaclaz

Well, just like there was a SETUPLDR.BIN and a SETUPLDR.EXE, and a NTLDR and a NTLDR.EXE (or OSLOADER.EXE): http://reboot.pro/topic/5900-make-your-own-nt-os-loader-ntldrsetupldr/ http://reboot.pro/topic/9474-busting-the-myth-about-ramdisksys-xp2003/page-2#entry82899 it is possible . But besides the stripping of the extension, the 16 bit stub is added to it (just open bootmgr in a hex editor and search for the PE header "MZ" ). JFYI: http://reboot.pro/topic/16824-how-to-modify-bootmgr-of-windows-8/ http://www.sevenforums.com/customization/106861-how-change-boot-animation-windows-7-a.html http://reboot.pro/files/file/188-bootmgr-recompiler/ jaclaz

And what happens on EFI? http://www.911cd.net/forums//index.php?s=&showtopic=25596&view=findpost&p=175061 And it is NOT bootmgr.exe (on BIOS), only BOOTMGR. The "old" NTLDR was both a bootmanager (rather poor) and a Systemloader (but needed, to boot NT systems, the "side app" NTDETECT.COM). The "new" BOOTMGR is essentially (also rather poor) bootmanager and a system initiator (i.e. it also replaces NTDETECT.COM), but the actual Systemloader is winload.exe. BTW (and just for the record) BOOTMGR also parses the BOOT.INI files and adds any non-Arcpath entries in it): http://www.msfn.org/board/topic/169320-dual-booting-dos-and-win7/?p=1059437 The differences (still on BIOS only) are graphically presented here: http://www.multibooters.co.uk/multiboot.html Loosely, on DOS the actual VBR code was the first (and only) stage systemloader and bootloader (i.e. it directly chainloaded IO:SYS). On NT systems the VBR code chainloads the NTLDR, which then becomes the second stage systemloader and bootloader (the NTLDR, after having used NTDETECT.COM as auxiliary tool, chainloads the actual kernel). Since Vista , BOOTMGR becomes the second stage bootloader, and winload.exe is either the third stage bootloader or the systemloader. jaclaz

Nothing "convoluted" . Try using the English version loblo posted . If it works, good If it doesn't, before giving up , risk using the original Japanese version. jaclaz

Well, since out of your current 10 posts exactly 10 are about or connected to Aeroglass, you should be the one that answers that question. I presume no progresses on your tool : http://www.msfn.org/board/topic/163698-tool-aero-glass/ right? jaclaz

Cannot say, from the good ol' times I have always had it to "1". Check in a command prompt, if also in there something like a DIR C:\P* also gives them in lower case, it should mean that the folder(s) are actually named that way. Of course Virtualbox is "innocent" in that, but it is well possible that some settings in nlite creates that, cannot really say jaclaz

Ummm, sorry. That is most certainly *not* 'taking it like a man'. Listen up fanboy. By bending over, grabbing your ankles with a smile on your face you are doing the exact opposite - taking it like a woman. Try again sweetie.For NO apparent reason (an image is worth a thousand words ): jaclaz

It's called "infotip" and should be in Windows 2000 alright: http://msdn.microsoft.com/en-us/magazine/cc748674.aspx It is possible that some Registry keys have been changed. jaclaz

Is this in Explorer? Check if you have a setting in the Registry for "beautifying filenames", actually "DontPrettyPath": http://ss64.com/nt/syntax-reghacks.html jaclaz

I don't understand the doubt about "it's not immediately clear what information the devices could capture" It's easy, *anything*, it is a cellular "man in the middle" device: http://arstechnica.com/tech-policy/2013/09/meet-the-machines-that-steal-your-phones-data/ Besides the actual hardware, there are "modular" softwares, so not *any* device can do *anything*, most probably the Fishhawk software is the one that, being defined (see the pdf in the above) : but it is optional/a separate buy. And the stingray is not the "only" device: http://www.wired.com/threatlevel/2011/10/datong-surveillance/ JFYI, the technology is not really "news", it is something in use since several years: http://publicintelligence.net/harris-corporations-stingray-used-by-fbi-for-warrantless-mobile-phone-tracking/ Of course the good three letter agency guys try to say the least they can on the capabilities of the device: http://www.wired.com/threatlevel/2013/03/gov-fights-stingray-case/all/ if there is some data, likely it can be found here: http://epic.org/foia/fbi/stingray/ jaclaz

You see, sometimes you need to ask the right questions . jaclaz