jaclaz

There is no script? If a formatting attribute is *somehow* kept, and the hypothetical script is a batch script, the CMD interpreter will remove the attribute. Create a (say) new MS Word document, copy and paste in it: ECHO boot.ini here the BOOT is italics bold, the dot is red, the INI is underlined red. When you paste it in a "rich" text editor these characteristics will be kept. Now open a command prompt and paste again in it, and press ENTER. The CMD strips the attributes (actually it is the clipboard that pastes only the text, I believe) The script, on the other hand needs to be a plain text file, with extension either .BAT (wrong) or .CMD (right) other formats (i.e. those that can keep the formatting) won't be parsed correctly an throw an error jaclaz

Sure, that would be: boot[ color = #000000].[ / color]ini

What jumper posted is actually something like (without the spaces) this: b o o t [ i ] . [ / i ] i n i the part inside the square brackets is what tells the board software that the dot between the two sets of square brackets is to be rendered as italic. Just like you do not see the square brackets, when you copy and paste you do not have them. In any case that is just a string and you cannot execute a string, the file with that name is a plain text configuration file and anyway it is never executed, the lines inside that file are parsed and then IF valid, used as parameters for the use of NTLDR (and the parser is quite strict). A file name is NEVER executed, and even IF it was a file, a .ini file is NOT executed. In DOS/WINDOWS the extension (what is after the dot in file names) is a way to identify a file type and take actions depending on it. jaclaz

Sure, .ini is one of the known excutable extensions by default, together with .txt and .csv. Come on .... jaclaz

Google this: the labgores guide to converting full height pci jaclaz

I was joking, but not much. Seriously, I don't think that such a bracket actually exist as "standard", but essentially it is a small piece of metal sheet that can be fabricated easily with a minimum amount of tools at home, AFAIK half-height brackets are just the sane, the bottom part (and holes for ports) are in the same position, it is the top that is shorter, i.e. - reversed - this non-existing adapter from half height to full: https://linustechtips.com/topic/1108047-low-profile-bracket-adapters/ exemplifies the point. The tricky part is making the holes for the square/rectangular (e-sata in your case) ports, what I do when doing any of my half-@§§ed mods is to cut away the bent part at the top of the original bracket, drill a couple of holes and bolt the bracket to a suitable hand made bracket, with larger (and not-so-accurate) holes for the ports/connectors. Now, only for the fun of it, would you believe that a site: http://www.bracket.com/ exists? jaclaz

Hmmm. Maybe : https://www.ebay.co.uk/itm/395043627656 jaclaz

Many years ago, you couldn't discuss CD-ROM drives Matsushita because it became Matshu****a when posting ( and we all used Panasonic instead). We will need to start talking of the file with name boot and extension ini. jaclaz

My guess is that the one Andalu has is similar to this one: https://www.ebay.co.uk/itm/165040641302 (a tad bit cheaper , if it is the right card ) jaclaz

Naah, you didn't overstep at all, just having a bit of fun at the way you phrased it, don't worry. coot.ini jaclaz

I cannot say what you are assuming , I would hope that Admins have something more interesting/entertaining to do on a saturday evening. It's not (yet) a DEFCON 1 situation. jaclaz

boo

Confirmed, it is b o o t . i n i that cannot be posted, it makes no sense whatsoever.

oot.ini

ot.ini

t.ini

Yep, but in this specific case it seems like it depends on the contents of a post, is almost like there is a word filter gone astray. jaclaz

.ini

boot

b o o t . i n i I cannot post the above without the spaces. Queer.

IF the bootmgr\bcd in Vista is similar enough to ntldr\

test It is a curious case, I cannot post a given sentence. Here it gives On the original thread gave different errors, initially "saving" forever, then attempting to use EDIT, it said that post was too old or had been deleted.

Interesting. There is something preventing me to post some comment. The disk is anyway MBR, isn't it? (or you have some mod to access GPT in Vista?) Or installing the Windows 10 first allows to install Vista on GPT? (i seem to remember there were issues in attempting to install Vista "directly" on GPT). in older XP, setting a BAUDRATE automatically switches DEBUG on: http://smallvoid.com/article/winnt-boot-ini.html it is probable that also expliciting DEBUGPORT has the same effect of enabling DEBUG automaticallly. Cannot say if it applies to the bootmgr version you are using, but have you tried the LOCAL option? jaclaz

I really don't know what is "hip" (or actually any good) these days, in the good ol'days I would have suggested ping: https://ping.windowsdream.com/ but they want the user to register now, and I am not going to do that. There is (free for non-commercial use) the Paragon software: https://www.paragon-software.com/free/br-free/# but it is windows 7 and up only and I don't seem to remember having ever had it working from a PE (which is how these backup/imaging system should run, offline). Something that would be worth a try is redo rescue: http://redorescue.com/ though I have no real experience with it, I have heard good things about it, though the sheer fact that it advices Balena Etcher[1] to make the USB version, it is NOT a good sign IMHO. jaclaz [1] Balena must be connected to the size of the stupid tool, more than 100 MB for what amounts to a fancy looking dd.

Only for the record, Recuva is a software that essentially undeletes files, it won't fix anyhting if the issues are at filesystem or partitioning level, but here the vhd(x) files are seemingly just fine, and the files are as well all here where they should be, this kind of failure is much more likely connected with the restore process, that finds *something* it doesn't like and freaks out, possibly a teeny-tiny setting in the Registry, the BCD, even in the (same) BIOS or *whatever* (there are reports of similar issues that seemingly were due to some "pending update" at the time of the creation of the image) that prevents from booting the restored system. Dave-H report is typical for something that only sometimes fails (or only sometimes works, if you are a pessimist) the kind of errors that are very difficult to pinpoint and hopefully solve. In typical MS approach, instead of looking for the issues, finding and fixing them, they decided to advise to not use the system backup and restore. You go to your car dealer and tell them that your car hand brake doesn't brake properly, i.e. fails to keep the car blocked when parked on a steep road and they tell you that you should buy a third party rope and anchor jaclaz