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

The simplified way, single disk partition: A disk normally partitioned with XP or earlier will have 63 sectors before the first partition or if you prefer the partition will start on LBA 63. A disk normally partitioned with Vista or later will have 2048 sectors before the first partition or if you prefer the partition will start on LBA 2048. The old disk has 512 bytes sector. The new disk (or SSD) needs to have 512 bytes sector. (both have, rest assured, "native" 4kb disks are rare the format is limited to very large size ones). Re-aligning the partition from 63 to 2048 will be unnoticeable to you on the hard disk (and it won't make much difference anyway) but on the SSD it might seriously slow it down, so you should actually move the partition (on the new device) to be 4kb aligned. The only issue with XP having non-aligned-to-cylinder/head (i.e. 63 sectors before) may come with logical volumes inside extended partition, and only if you fiddle with the disk in the XP disk manager. I cannot say what exactly (in detail, and when you talk about data details are vital) how the mentioned app behaves in the two different modes, but what I would do would be to use BOTH devices in this case. 1) BEFORE anything else make a copy of the MBR of the disk and of the PBR of the partition there are several ways/tools, but even the simplified HdHacker would do: http://dimio.altervista.org/eng/ (you want to make a copy of first sector of the \\.\PhysicalDrive and a copy of the first 16 sectors of the \\.\LogicqalDrive) Store these two files (only a few kilobytes) on anothe device, let's say a USB stick, this is a sort of "insurance", should something in the following change a few key values, we will have a way back. 2) clone "as is" (with Disk Clone) the "failing" old disk to the new "conventional" disk (possibly on the "other", Windows 7 machine) 3) make sure that the new disk works as the old one on the original XP machine 4) then back on the Windows 7 machine: 5) copy the tested "new" disk contents with System Clone/Migration to the SSD (which will have been partitioned and formatted with the "proper" 4 Kb alignment) 6) if the "automagical" tool works as expected the newly made SSD will be able to boot "as the old disk" on the XP machine 7) if it doesn't a simple set of commands should be able to have it working "manually" but even if this doesn't work, you still have the "original disk" (failing/defective but still somehow working) and an exact copy of it on the "new disk" (fully functional) so that we can loop to #4 and use another tool/another approach Once the "final" SSD (with the new alignment but with the smaller, old size of the partitoin) will have been tested to be working nicely, only then use the tool you mentioned (or a similar one) to extend the size of the partition. Again, should anything go wrong in this latter process, you can always loop to #4 and start again. jaclaz

Well, to be fair to the good Gartner guys , this particular prediction seems as accurate as most of the others they make. jaclaz

Well, to run RunAsTI you need anyway to be Administrator, I would have thought that this was well established: https://github.com/jschicht/RunAsTI You do understand that one thing is giving back to an Authorized user (Administrator or Owner of an OS) some added powers that the good MS guys senselessly removed in some new OS versions and a completely different thing would be giving "full powers" to a "common user", don't you? The latter would be a rather serious "privilege escalation" vulnerability (and RunAsTI the corresponding exploit) jaclaz

Sure the argument(s) will need to be inserted inside the shortcut in the "Command line arguments" field: http://www.howtogeek.com/140737/create-a-shortcut-to-avoid-user-account-control-popups-the-easy-way/ In other words, first your shortcut must work when you double click on it, and only later you try starting it from a batch file (passing NO parameters to it). jaclaz

My guess is that to eliminate the prompt there are only two ways: 1) a shortcut 2) use the schtasks task manager way In your batch to invoke the shortcut you need to use the START command: http://ss64.com/nt/start.html something *like*: START "" "C:\mypath\myshortcut.lnk"might do. jaclaz

Naaah, this is it, it actually almost undetectable: jaclaz

Hmmm not really good news for the IoT guys: http://arstechnica.com/security/2015/11/why-algebraic-eraser-may-be-the-most-risky-cryptosystem-youve-never-heard-of/ jaclaz

Yep , just in case: http://www.msfn.org/board/topic/128807-the-solution-for-seagate-720011-hdds/?p=916757 jaclaz

Well, as always it is not something extremely clear. The point is (or should be) that the actual driver used in the early part of setup only understands a given isolevel (and/or Joliet or not). Files used in the early phases of setup need to be UPPERCASE and 8.3, and there are (were) tools (like toupper.exe or uppercase.exe or filecase.exe or similar) to make sure that this was the condition. Now, for no apparent reason , dashun9.cmd : http://www.msfn.org/board/topic/171435-allow-lowercase-on-multiboot-dvd/ http://www.911cd.net/forums//index.php?showtopic=25612 jaclaz