jaclaz

Just to point out the obvious, before the $ 5 rebate the PNY one is listed as being $ 12.99 on the Amazon page you found, this should tell people something about the "Regular $ 24.98" on the WalMart ad: ... and here: http://www.bhphotovideo.com/c/product/715546-REG/PNY_Technologies_P_FD32GATT03_EF_32GB_Attache_Flash_Drive.html is again 7.99, Staples has it at 6.99: http://www.staples.com/PNY-Attache-3-32GB-USB-20-USB-Flash-Drive-Black/product_917069 Maybe - just maybe - when you can have something from several vendors for between 7 and 9 bucks, its actual market value is between 7 and 9 bucks. jaclaz

So your policy is "Someone got it, so I must get it too" ? Naah, personally my policy is to stay waaaaay clear of any OS that is actually supported by any version of Aeroglass (of course not because of Aeroglass, which is IMHO a very nice little tool ) only because those OS's are largely senseless. More generally (and still personally) my policy is "calling things by their name", even when this makes me appear as a grumpy, old, bastard (which - since I actually am an old, grumpy, bastard is NOT a misrepresentation ). jaclaz

You are welcome. I would guess that the point is not really where (or if) it is written but rather if this actually happens (as reported here by n users who have donated). You could (temporarily, just as an experiment) try leaving the watermark (in a "non-experimental" release) even if a donation key is found and see how much gratitude people that actually donated would show on MSFN..... In any case, without deleting anything, you should be able to move all the "license related" posts from this thread to a new, separate one. jaclaz

Hmmm. All these years using Opera and User Mode vs. Author Mode does not make that particularly "new". jaclaz

Actually it *somewhat* does: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/netsh_int_ip.mspx?mfr=true though not in an extremely "clear" manner. AFAIK gateways are in a given order and the first one is what is used, the second is is a "fallback" device that only is used if the first fails and so on.... The routing table (if any) is what is otherwise used for choosing the gateway to be used, and here comes (again) into play the metric: http://serverfault.com/questions/59442/routing-decision-when-there-are-two-default-gateways-on-windows https://technet.microsoft.com/en-us/library/cc779696(WS.10).aspx http://blog.palehorse.net/2009/08/24/using-windows-7-with-multiple-gateways-and-dhcp/ jaclaz

Well, let's say that if someone actually READs what has been written on MSFN, he/she might get that impression , I mean : http://www.msfn.org/board/topic/173139-read-first/?p=1090811 About adacom I completely disagree with dhjohns and Kel , there is not (yet) a Law or board Rule preventing people from expressing their own opinion on something, the point here (as bigmuscle stated) is that adacom's opinion has been already expressed several times and going over it again again and again is a bit tiring. But by the same token, bigmuscle's obsession about insisting to call NOT things with their name is tiring, but all in all the good thing is that it creates a nice, symmetrical situation. More or less it goes like: It's nagware.No it is not, it is donationware.No, it is nagware.No you are free to donate.No I am not as I want to get rid of the watermark.But you donate to support the development, not to remove the watermark.But since when I donate I get rid of the watermark, I am not donating but buying the privilege of removing the watermark.No, you are donating because you want to support the development of the tool.No, I am donating to get rid of the watermark.That's your problem, donation is for support of development.But it effectively removes the nag.But this happens because you supported the development.Not really, this happens because I payed for a license of it.No, you are not getting a license, you get consideration for having contributed to development.So it's nagware.No, it is not, it is donationware. jaclaz

The topic (or something very close to it) has been discussed extensively here: http://reboot.pro/topic/20240-how-to-get-partitions-path-in-command-prompt/ http://reboot.pro/topic/20476-retrieving-devicedrive-information/ Maybe you can find something of interest in the above, but more specifically if I get it right your question revolves around "On which \\.\PhysicalDrive# is the current partition/volume residing?" IF this is the case, I believe this would do nicely: @echo offecho This cmd has been run from LogicalDrive %~d0\FOR /F "tokens=2 delims=#," %%? IN ('WMIC Path Win32_LogicalDiskToPartition Get Antecedent^, Dependent ^|FIND "%~d0"') DO (echo LogicalDrive %~d0\ is residing on \\.\Physicaldrive%%?)pause(slightly longer than a one-liner in batch) jaclaz

gwmetric? jaclaz

I have still not at all clear the whole thing, but basically this is "wrong": #start WIM10title WIM10find --set-root /SYS.tagpartnew (hd0,2) 0x0B 95674368 29358080partnew (hd0,0) 0x0B 13885440 12580864root (hd0,0)makeactivechainloader /grldrload defaultbootthere is no reason why you would want to chainload from grldr another grldr, you can load in the "same, initially loaded" grldr another menu, using the configfile command and or you can use the default command to change which menu entry is autoselected at boot.There is no "load default" command that I can remember The "normal" way is to use the default (file)and the the default (command) and setdefault (command): http://diddy.boot-land.net/grub4dos/files/menu.htm#default jaclaz

Several articles here: http://wrensound.com/blog/ that you may need to read in order to (hopefully) find an answer to your question(s) or at least be able to ask an understandable question, in any case, if you are going to re-ask a question, you should provide the NEEDED DETAILS, in order to (still hopefully) obtain valid answers. jaclaz

I am not sure to understand the question, however you can load another menu with the configfile command. Do check the guide: http://diddy.boot-land.net/grub4dos/Grub4dos.htm http://diddy.boot-land.net/grub4dos/files/menu.htm#submenu http://diddy.boot-land.net/grub4dos/files/commands.htm#configfile *like* title another menu on hard disk (hd0,1) root (hd0,1) configfile /another.lst You can use more than one menu(s) with a single option or use the "default" mechanism. jaclaz

Good , I guess that which ERRORLEVEL is set should be verified in the two cases (when the FIND actually finds the program.exe and when it doesn't) but the main thing is that it works . jaclaz

But why the two batches? I mean (IF I have understood the issue) wouldn't this single batch do nicely? @echo offcd /d "H:\path"program.execd /d "C:\path":loopxcopy /y "C:\path" "H:\path" /dtimeout /t 20:CHECKTaskList /nh /fi "IMAGENAME eq program.exe" | find "program.exe" 2>&1 > nulIF %ERRORLEVEL% NEQ 0 GOTO :looptaskkill /f /im cmd.exe /tThe ERRORLEVEL syntax has been modified, though the one you used is fine, because of this (it's only a habit, not really-really needed in most cases): http://www.robvanderwoude.com/errorlevel.php jaclaz

Yes http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/questions-with-yes-or-no-answers.html More seriously, yes, there are quite a few members running daily NT 4.00 or 2K (besides the ones that spend a lot of time into making unofficial updates/fixes and what not supporting those OS's ) . jaclaz

I don't think that it is a Zalman only issue, it seems to me like falling in the general issue of too tightened screws on PCB's, it is entirely possible that the specific Zalman brackets force the PCB deforming it and that this *somehow* causes issues, but never heard specifically of RAM issues, good to know jaclaz

Beginning. Windows NT systems do not create FAT32 partitions larger than 32 Gb (and this is probably the reason why you ended up with a 32 Gb partition). Windows NT systems do not "see" or "like" (or actually mount/assign a drive letter to) any partition if not the first one (meaning the one which is in first entry of the MBR) on Removable devices.There are workarounds and "tricks" around the two above listed issues/features, but you are probably not (yet) ready[1] for them. Possibilities. RMPREPUSB, EASY2BOOT, RUFUS, UEFI MULTI (google for the above tools, you will find their homesites and - likely - a number of threads discussing them (here or on reboot.pro or on 911cd). The mentioned tools are largely "automated" and might provide just what you need (though there is anyway an initial learning curve to use them). jaclaz [1]You have to understand that you want to go from "basic" or "n00b" (no offence whatever intended ) to "very advanced" and this will imply a lot of reading and learning.

Maybe, or maybe people do not know the answer or maybe the people that know the answer were not logged in in the 6 (six) hours you waited.... However, try to re-read your question faking that it comes from someone else, can you find some information that is obvious to you but that noone else but you can possibly know? You know, like which hardware is involved (what is "Windows 10" running on, which make/model "your stereo"stereo is it, what is "your internet connection" ), what do you expect to use the (supposed/desired) connection for, what is "not detecting" what, etc. jaclaz

I still have no understanding of the final GOAL. I was expecting a description of the expected result or scope and - unless of course it is a trade secret of some kind - the contents of the batch and what is the actual "program.exe" would be another piece of useful info (as I am completely failing to imagine an executable that would not work with "START /W" ). You need to be aware of the risk of (possibly) slipping on a chocolate covered banana or more generally fall in the XYZ problem: http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/put-down-the-chocolate-covered-banana.html jaclaz

There are two .ESD formats, one encrypted and one not. jaclaz

Side notes. Always use a name or just a pair of double quotes when using the START command. http://ss64.com/nt/start.html You cannot really use TASKLIST like that, as it doesn't set an ERRORLEVEL, see: http://stackoverflow.com/questions/4969595/exit-status-of-tasklist-in-batch-file http://stackoverflow.com/questions/162291/how-to-check-if-a-process-is-running-via-a-batch-script I am not sure to understand the original idea, can you provide some details on what you actually *need* or *want* to do? jaclaz

Not really. If you can boot from a CD you don't need the Windows 7 machine at all (if the tool you are using is capable of changing/fixing alignment, many will do). Boot from CD the old machine with the "old" and "temporary" disk drives connected.Clone "old" to "temporary" WITHOUT correcting alignmentDisconnect "old" (after having switched off of course).Check that "temporary" works fine as before (i.e. it is an actual clone) by booting from itConnect the "Momentus" (after having switched off)Boot again from CD and Clone/Copy "temporary" to "Momentus", fixing alignment (again cannot say if any of those tools you mentioned will do and how exactly they work)Disconnect the "temporary" (after having switched off)Boot again this time from the "Momentus" and check that it works.This way if anything works as expected the (supposedly failing) "old" hard disk) is read only once[1], the "temporary" is written and read only once and the "Momentus" is written only once. jaclaz [1] This is the actual main thing, the more you use a disk drive that you suspect is failing the more you risk losing data, cloning a disk takes several hours of continuous use of the disk is likely to increase heat/what not.

Well, then you have a (very small) issue. If you saved just the PBR of the DELL recovery/tool partition it means that you have more than one partition on that disk (and you failed to backup the one of the "main" partition). On a disk there is one (and only one) MBR but as many PBR's (Partition Boot Record) as there are Partitions, so you might want to make a backup of the PBR of the "main" NTFS partition volume as well. In any case it is just a further safety, not really-really needed (but you never know). The fsutil behaviour is "normal", the version in XP simply misses that check (at the time it was released ALL disks had 512 bytes/sector) whilst the 7 one has been upgraded to include that "Physical Sector" stuff. Don't worry , all those devices expose a 512 bytes "Physical" sector size (remember that they are/were intended by the manufacturer as a "normal" device to work with XP also, it is just the good Microsoft that spread some FUD when they decided that AF/512e drives are not supported in XP/2003 family of OS's, all the world runs normally XP/2003 on AF/512e disks without any issues, with the exception of the mentioned one with logical volumes, which is caused by the new alignment approach even on "native 512" anyway). In a nutshell: 512 native: internally use (maybe) 512 bytes sector, externally expose (obviously) 512 bytes/sector. AF (advanced Format) or 512e (and most SSD's): internally use (maybe) 4096 bytes sector, externally usually[1] expose 512 bytes sector. 4k native: internally use (maybe) 4096 bytes sector, externally expose 4096 bytes sector.for your use #1 or #2 doesn't make a difference, while #3 would simply be unbootable on anything before Windows 8. Still, on AF/512e it is strongly recommended to use the "Mb" alignment (the "default" 2048 LBA is not really *needed*, but it is OK), if you create the partition on your Windows 7 system it will be aligned, but as said I don't know how your "tool of election" actually works (in detail), it is very possible (actually probable) that it has an internal feature that creates (and shifts to the "right" alignment the partition when doing the "System Clone/Migration". The essential point of the proposed approach is that if the #5 fails (for *whatever* reasons) you still have a fully working source to try again (with the same tool and different settings or with other tools/methods). jaclaz [1] The AF or 512e is not really a "standard", each manufacturer may have implemented in one model (or the other) different ways to "expose" to the OS *anything* (and the contrary of it), I wouldn't be surprised if in testing a range of different AD/512e disks Windows Vista or later would detect different "physical size" the good news being that XP in it's "ignorance" hasn't read MS KB's or doesn't really know anything about this and just keeps working.

http://reboot.pro/topic/18182-uefi-multi-make-multi-boot-usb-drive/ jaclaz

Nice If I may this is something that you could (of course only if you have the time and dedication for it) check before "going back in time": ideally the modifications to txtsetup.sif (and/or to the other files you mentioned) should be verified to be the bare minimum required (and no more) or if needed trimmed down to only what is actually needed. jaclaz

Does it include a compehensible pospect with a peview of pocedures to poperly add pograms in pactice ? jaclaz