jaclaz

Hmmm. It could be a timing problem, but since after you create the "main" partition and assign to it the "W" drive letter you create another partition that shouldn't be the issue. And after all the gpt.txt seems like being taken (almost verbatim) from the MSDN one: https://msdn.microsoft.com/en-us/library/windows/hardware/dn621890.aspx What happens if you add a check after the gpt.txt is run? Still downright selecting disk 0 may be a risk in some configurations... and there is not much sense in creating the WinRE and Recovery partition if you don't use them. jaclaz

For the moment I just re-ordered/re-compacted your script, this way it should be easier to read (and modify when needed) without (hopefully) changing anything in the commands that are actually executed and in the messages to the user. (BTW isn't it Laufwerk and not Lauferk?) @ECHO OFF SETLOCAL ENABLEEXTENSIONS ENABLEDELAYEDEXPANSION ::Let's check first thing if a volume with label "wim" is found, otherwise there is no sense to go on SET wimdrive= FOR /F "tokens=1,2 " %%A in ('wmic logicaldisk get caption^,VolumeName 2^>NUL') do ( IF /I "%%B"=="wim" SET wimdrive=%%A ) IF DEFINED wimdrive ECHO Lauferk "wim" wurde gefunden: %wimdrive% &&PAUSE&&GOTO :MENU ECHO Lauferk "wim" wurde nicht gefunden :( PAUSE GOTO :EOF :MENU CLS ECHO ============= Bitte auswaehlen ======================= ECHO ----------------- ECHO 1. Windows 7 64bit - 29.08.2016 ECHO ----------------- ECHO 2. Windows 7 64bit - AutoCAD ECHO ---------------- ECHO 3. Windows 10 LTSB - mit BIOS ECHO ---------------- ECHO 4. Windows 10 LTSB - mit UEFI ECHO ---------------- ECHO ==========Bitte druecken Sie Taste-Q zum Abbrechen========== ECHO. :Inputloop SET "Input=" SET /P "Input=Please Enter 1-4 or Q: " IF NOT DEFINED Input ECHO Invalid input & goto :Inputloop ::This limits the input to first character: SET "Input=!Input:~0,1!" ::This limits the input to characters in delims for /f "delims=1234qQ" %%? in ("!Input!") DO ECHO Invalid input & GOTO :Inputloop IF /I "%Input%"=="q" ECHO Batch stopped by user choice&&PAUSE&&GOTO :EOF ECHO Jetzt wird alles automatich gemacht (diskpart, imagex(dism), bcdboot)! CALL :Choice_%Input% ECHO Fertig. Bitte PC neu starten (exit befehl). ECHO ------------------ ECHO =============Druecken Sie belibiege Taste============== ECHO ------------------ GOTO :EOF :Choice_1 Diskpart /s %wimdrive%\mbr.txt %wimdrive%\Imagex.exe /apply %wimdrive%\win7_64bit_2016.wim 1 C: CD /D C:\Windows\SysWow64 bcdboot C:\Windows /s S: GOTO :EOF :Choice_2 Diskpart /s %wimdrive%\mbr.txt %wimdrive%\Imagex.exe /apply %wimdrive%\win7_64_autocad_07092016.wim 1 C: CD /D C:\Windows\SysWow64 bcdboot C:\Windows /s S: GOTO :EOF :Choice_3 Diskpart /s %wimdrive%\mbr.txt dism /Apply-Image /ImageFile:%wimdrive%\win10.wim /Index:1 /ApplyDir:C:\ CD /D C:\Windows\SysWow64 bcdboot C:\Windows /s S: /f ALL GOTO :EOF :Choice_4 Diskpart /s %wimdrive%\gpt.txt dism /Apply-Image /ImageFile:%wimdrive%\win10.wim /Index:1 /ApplyDir:W:\ CD /D W:\Windows\SysWow64 bcdboot W:\Windows /s S: /f ALL GOTO :EOF At first sight, you have seemingly 3 out of the 4 choices working when using the drive letter C: and 1 not working when you use drive letter W:. Now what it seems like missing/wrong/to be understood is how you assign drive letters (I believe that this happens in the Diskpart scripts mbr.txt and gpt.txt, which you should provide, later we will see if it is the case of embedding them in the batch) and how BEFORE running potentially destructive commands such as Diskpart and ImageX or Dism the status of drive letter assignments and of physicaldrives is checked. I mean, are all machines in the same EXACT configuration and do all the BIOSes/UEFIs behave the same? Is actually the internal disk the first disk (PhysicalDrive0) on all machines (even when booted from USB)? Is the disk always either "clean" or "partitioned"? Please post some details and the two diskpart scripts so that we can understand if this can be an issue. jaclaz

This is strange. If you connect the 32 pin cable reversed (it has happened to everyone) what should happen is that the led light on the drive switches on (and remains on), see: http://www.oldskool.org/guides/oldonnew/floppy jaclaz

Yep, it is possible that it is the cable, but that motor is linked to the heads slide assembly (through a worm screw) so if the motor runs, the head slide should also move. If the motor runs and the head slide remain in the same position, it may mean: 1) the head slide is stuck and the motor can't move it (and there is some mechanism, think of a slip clutch, that makes the motor turn anyway "idle" whenever a given excessive force is needed) 2) the head slide is at the end of its intended travel, and *something* (wrong cable, a position sensor/switch. something else, whatever) keeps the motor powered on (and there is some mechanism as above) 3) for *whatever reasons* the motor is disjointed from the worm screw (which doesn't turn) 4) ... jaclaz

At the light of this (Mac OsX news): http://applehelpwriter.com/2016/07/28/revealing-dropboxs-dirty-little-security-hack/ http://applehelpwriter.com/2016/08/29/discovering-how-dropbox-hacks-your-mac/ maybe if it is discontinued on XP would not be that bad. jaclaz

That could be the head motor? It is possible that in several years of storage some grease has become "stale" blocking some mechanisms, if it was not a just bought (new) drive it would be the case of (carefully) disassembling it (at least the cover) and manually move the spinner and the heads, but not on something you just paid an awful amount of money for and that should be under warranty. Here is a video representing your floppy drive (or a very similar model): you should be able to see how it works. jaclaz

The GRUB2 has now a "mechanism" that creates grub.cfg (the configuration file for GRUB2) "on-the-fly" and on the actual grub.cfg there is a "warning" against NOT editing the grub.cfg manually. The idea is that this way when GRUB2 is updated there are no (or less) issues (if I get it right) but the practical result is that a number of entries in grub menu are added, and possibly the "auto-magic" mechanism *somehow* mixes up the two Linux distro's. The same kind of "mixed up" may happen due to glitches with the update mechanisms for dist/packages/drivers. Which of the volumes is Ubuntu installed on? Which of the volumes is the Kali installed on? Not on the same volume I hope, anyway I suspect that since you have two distro's using the same GRUB2 mechanisms there may have been a glitch in the grub.cfg making scripts (kernel parameters passed at boot time?) or some form of cross-linking between the two installs in some other configuration or "default" file. Can you try making a bootabe USB stick (or other boot media) with GRUB2 and a "static" (handmade) grub.cfg (with just the two or three boot entries you use) and check if the behaviour is the same? jaclaz

Allow me to doubt they can have blacklisted "Setup.exe" by filename ONLY. jaclaz

You are likely using (and that might explain the "left" and "right" quotes), a "wrong" editor that "mixes" character sets (or possibly uses UNICODE) or you are saving the file in the "wrong" format. It is common enough, especially when copying and pasting from the Internet as a web page (or a forum post) may have "strange" formatting of characters. Open the .cmd in NOTEPAD (and nothing else) and try replacing what you may see as "-" dashes, with actual dashes and make sure to save as ANSI text. The cmd.exe command processor using a given encoding (which is similar to the DOS one, different from the usual Windows one), this is normally not an issue with any character in the ASCII table (i.e. code up to 127) but that has a few incompatibilities with the 128-255 range. jaclaz

It seems like a DS0/DS1 jumper, maybe the drive you have is a "recent" one that has some automagical trick inside that sets all the other options/configurations, the number after the V might be the Version. And yes, the "standard" is DS1 (like it is seemingly set now), but the combination of drive cable and motherboard may need it instead as DS0 This is the V2: http://forum.kryoflux.com/viewtopic.php?t=556 http://embeddedsw.net/EMUFDD_MITSUMI_Jumpers.html and this is a V3: https://gist.github.com/anarchivist/3003928 Cannot find anything specific for the V5, I remember the old ones with several jumpers, so it is likely I am barking up the wrong tree :w00t:. jaclaz

You don't have a set of jumpers like?: http://embeddedsw.net/EMUFDD_MITSUMI_Jumpers.html http://www.cbmstuff.com/downloads/5.25-jumpers.pdf I was thinking of lack of termination (or termination that should not be there) and/or DS0/DS1 etc. https://offog.org/notes/archiving/minifloppies/ Sometimes you just need to try every possible combination It's a lot of years I don't fiddle with those 5.25" floppy drives, but I remember them being - in the good ol' times - a real PITA ... jaclaz

So does that mean that windows 10 "blacklists" executable based on filename + *something else* (let's say a CRC or similar checksum)? jaclaz

What do you mean "it is not working"? It cannot find the drive or it doesn't accept user input? Or *something* else? I would guess that conditions like this: IF /I ‘%INPUT%’==’1’ GOTO Selection1 will NEVER be true (first quote on the left is ‘ while the one on the right of the equal sign is ’ Use "plain" double quotes or 'straight' single quotes like the rest of the world... IF /I "%INPUT%"=="1" GOTO Selection1 (though I suggested you an input routine which is much "safer") and of course you cannot have TWO labels ":_doit" the batch would be rather confused about them. jaclaz

It is possible, but unlikely (they would have needed to remove part of the BIOS code), it is more likely that there is an issue of some kind between the cable and the jumper settings, can you post exact model of the floppy drive? Maybe we can find some documentation for it. jaclaz

And now, Married to the Sea jaclaz

Just the usual list of semi-random ideas: "straight" or "twisted" cable? any jumper on the actual Floppy drive? does the slot lever close properly? jaclaz

Good, everything is well that ends well . jaclaz

Sure not a problem but surely some redundancy/duplication/waste of storage. jaclaz

Surely it might help the guys that sell PC-unlocker and possibly the "Alfred Smith" that managed to register the domain/site chntpw.com (as well as some 100 other domains more or less related to password recovery), which is clearly made to get hits from people looking for the (Freeware) chntpw, which site is actually here: http://pogostick.net/~pnh/ntpasswd/ and then induce people to go to another site to buy another tool. Curiously enough, in the XML's on the affiliate program for "top-password" the Author of the programs is listed as "Alfred Smith", I like coincidences BTW I have no idea if that "top-password" software generically is worth their price and specifically whether "PC-unlocker" is actually worth 19.95 US$ (maybe it is) but surely it is a sneaky way to get some traffic/download and possibly sell the software. jaclaz

This brings us back to the question about the number of PE's in use. I mean, a boot.wim for the PE is probably something like 200-300 Mb or so and you will have two of them differing between them only by one occurence of "win10.wim" vs. "win7_64bit_2016.wim" in a batch file, and of course (IF you want to be able to install the one or the other OS, 7 or 10) you will need anyway to make a choice (between the first PE that installs the Windows 7 and the second PE that installs the Windows 10) jaclaz

Good jaclaz

Well, the filesize should be fixed to 1048576 bytes, so you can even hexedit/dd the CL50145A.fd over the CL50143A.fd extents on the .iso without need to rebuild it. jaclaz

#2 Why not? After all you are applying a .wim, nothing more, the point might be with the speciific DISM version, I seem to remember that for some operations you need the AIK/WAIK or the 8 version but that won't apply to "apply" (pardon me the pun). You can try using JFX's nice tool to get the various versions and experiment with them: Or you could also try the Wimlib: https://wimlib.net/ jaclaz

I am failing to follow you. You have a single script on a single PE or two different scripts (and two different PE's) for Windows 7 (BIOS/MBR) and Windows 10 (UEFI/GPT)? Is this what you want? @ECHO OFF SETLOCAL ENABLEEXTENSIONS SET wimdrive= FOR /F "tokens=1,2 " %%A in ('wmic logicaldisk get caption^,VolumeName 2^>NUL') do ( ECHO %%A %%B IF /I "%%B"=="wim" SET wimdrive=%%A ) IF DEFINED wimdrive ECHO A drive with label "wim" has been found: %wimdrive% &&PAUSE&&GOTO :_doit ECHO An error occurred can't find wimdrive :( PAUSE GOTO :EOF :_doit ECHO Just doin' it ::insert here diskpart commmands ::insert here imagex or Dism commands using %wimdrive% as the source drive letter ::insert here bcdboot commands ECHO All done PAUSE jaclaz

The fact that it is NOT clicking is actually good news. Opening the drive is about the silliest thing you could have done, however. No matter how "clean" was the environment you actually opened that disk drive, it is doomed. No idea about the "err" noise, but is it in status: 1) LBA0 or BSY <- you are in the right place and it usually can be fixed following instructions 2) Something else <- you are in the wrong place The opening of the drive may have well made it completely unrecoverable, even if it is in one of the two cases this thread is about (LBA0 or BSY). jaclaz