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

I don't think you are in any way "causing problems". We are here (at least this is the idea) to exchange ideas, opinions and where possible experiences and knowledge About the "suitability" of a sysprep based solution, I will quote the recommended (on the mentioned offline sysprep thread) introduction/documentation to sysprep, that coincidentally states: http://www.vernalex.com/guides/sysprep/introduction.shtml Personally, I tend to count like : one, two, three, many. if I stay within the three i plainly install the OS.if I reach the "many", I take my time to make a valid image and then deploy it. (still personally I was never a fan of "fully unattended" setups ).So, if I were you, unless there some stringent time limits, I would wait until next (last) "patch tuesday", in the meantime prepare the "universal image", install to it all the updates and then deploy it, I would also think about making - like submix8c hinted - an updated/new "recovery partition", either making use of the existing "Dell technology" to access/restore it or using a third party approach (like grub4dos or the Terabyte MBR or MBLDR). jaclaz

Some "sound routers": http://software.muzychenko.net/eng/vac.htm http://trac.jackaudio.org/ Also maybe useful: http://www.kvraudio.com/product/savihost-by-hermann-seib jaclaz

Also it may depend on how URGENT is the request (whining for the scarce help received after a few hours may mean that it is extremely urgent ) Something like these? (these are VST plugins, but there are, I believe sound routers/pipers that allow to use these plugins with *any* audio tool ) http://sirelliot.wordpress.com/2010/12/05/sir-elliot-eighteen-band-graphic-equaliser/ http://sirelliot.wordpress.com/2011/10/05/sir-elliot-21-band-graphic-equaliser/ http://sirelliot.wordpress.com/2013/07/01/sir-elliot-35-band-mastering-vocal-equaliser/ jaclaz

Well, as always I might be wrong, but if the "business purpose" of the hypothetical company is to: some old hardware, I would say that the company will last for a very short time. Thus the question is: can a company have a non-buiness purpose? and if a non-business purpose is carried in a company by a single person in his free time (and the company gets no benefit whatsoever from this) does point #5 above apply? What if the single person gets the hardware as a gift from the company and decides to refurbish it installing the OS and give it away to other friends? Seriously, regardless of whether "giving away for free to friends" entitles or not for the use of nlite, the whole point is that nlite is not really needed at all to integrate just the SP3, and since I believe what JeffA54 has to give away are identical machines, maybe it would be easier/faster to prepare a "sample" machine with all updates (and possibly pre-configured with additional software, settings, etc.) and then sysprep it and replicate it on the other machines. Even if the machines are different, thanks to Offline sysprep there should be no issues: http://www.911cd.net/forums//index.php?showtopic=22064 jaclaz

If I get this right you simply go to the https://f-droid.org/ site with the browser of the smartphone and click on the "Download f-droid" button. https://f-droid.org/forums/topic/how-install-from-f-droid/ Or you can e-mail it to yourself: http://www.brighthub.com/mobile/google-android/articles/107781.aspx jaclaz

Sure, just imagine the popularity of such drivers among the users of gts 250 video cards running NT 4.0, all 1 (one) of them . More seriously, whatever is a gts 250, have you tried the Vbemp drivers with it? http://www.msfn.org/board/topic/171307-video-card-driver-for-windows-nt-40/ jaclaz

Maybe to clarify a part of what has been posted till now. The OEM versions of some XP install (NOT "recovery") CD's from some leading OEM's are often modified. Dell (and to a lesser extent HP) has been reknown for these (often senseless) modifications. Such CD's may "play good" with nlite (and with any other third party tool, including the UDC) or they may cause some issues. Since there is no real "catalog" of such modified OEM CD's (and possibly they exist in a zillion versions) it is possible that a third party tool (that works fine with an "official" MS XP install CD) has some quirks when used on a OEM one. Usually (but not necessarily) a pre-SP3 OEM CD, once successfully updated through integration to SP3 level becomes "good" in - say - 99% of cases, but your specific OEM disc, especially since it's a DELL , may well belong to the remaining 1%. As an example, when these OEM CD's are used to build a PE 1.x, a couple specific DELL fixes are needed, see: http://www.911cd.net/forums/index.php?showtopic=15138 http://www.911cd.net/forums//index.php?showtopic=15138&st=29 jaclaz

From what I understand about UPXed programs (and not necessarily related to the topic at hand or to the specific tools/utilities) is that they use a lot more memory than their "plain" correspondent ones. As such, it is strongly advised to NOT UPX programs when the scope is to have it run on low-memory machines (at least this is what experiments in PE 1.x's led us to believe) Also AFAIK there is not a definite answer about UPX, sometimes the compressed file works sometimes it does not, sometimes it may seem to be working but it doesn't actually work when a particular function is called. As always: jaclaz

Don't want to gatecrash the party , but maybe if we could talk of actual problems (as opposed to non-problems ) we may go further . http://www.mdgx.com/web.htm Unofficial Windows ME Boot Disk Maker v1.2 32-bit</A> [603 KB] creates a startup floppy containing Windows ME boot files. link is broken, but the tool can be found - example - here: http://www.freewareweb.com/cgi-bin/archive.cgi?ID=1130 jaclaz