hi Olof
i have 1 problem with mounting FAT12 image file
when img file have 129 (0x81) sectors and more - all ok
but when 128 (0x80) and less - driver show error "invalid params"
this error happens in \sys\iodisp.cpp function IOCTL_IMDISK_CREATE_DEVICE
0x80 is 129 sectors with 512 bytes each
file size is 66048
but i was made minimalistic FAT12 img with 1 file (2048bytes) and this file mounting good in program "Gizmo Director/Gizmo Drive"
but ImDisk dont want mount 
my IMG file: http://www37.zippyshare.com/v/8QQaRUzC/file.html
image contain 1 file and 1 FAT
img file only 3584 bytes 
only 7 sectors (1 boot, 1 fat, 1 root, 4 file)
maybe driver have some limits in src? can you helps to find this bug?
I need some help in order to make some batch files for:
Create a RAM Disk b:\ (about 250 MB, NTFS compress), just after boot a PE
Mount PE MEdia (Cd-Usb) to another fix Drive Letter, just after boot a PE from a (Cd-Usb).
%SystemRoot%\System32\rundll32.exe %SystemRoot%\System32\shell32.dll,#61.
Shortcut.exe /A:C /T:"%SystemRoot%\System32\rundll32.exe" /F:"PATH\run.lnk" /P:"%SystemRoot%\System32\shell32.dll,#61" /I:"%SystemRoot%\System32\shell32.dll,-25".
I wanted to know the switches of imdisk, so I just typed (from CMD prompt)
C:\>imdisk
and the output was
Control program for the ImDisk Virtual Disk Driver.
For copyrights and credits, type imdisk --version
Syntax:
imdisk -a -t type -m mountpoint [-n] [-o opt1[,opt2 ...]] [-f|-F file]
[-s size] [-b offset] [-v partition] [-S sectorsize] [-u unit]
[-x sectors/track] [-y tracks/cylinder] [-p "format-parameters"] [-P]
...
so far so good. But when I redirected the output to a file:
C:\>imdisk 2>output.txt
The output has many extra blank lines
Control program for the ImDisk Virtual Disk Driver.
For copyrights and credits, type imdisk --version
Syntax:
imdisk -a -t type -m mountpoint [-n] [-o opt1[,opt2 ...]] [-f|-F file]
[-s size] [-b offset] [-v partition] [-S sectorsize] [-u unit]
[-x sectors/track] [-y tracks/cylinder] [-p "format-parameters"] [-P]
...
when viewed from Command Prompt, Powershell shell or any text editors.
The output happened to be printed from function ImDiskSyntaxHelp(), in file cli/imdisk.c. It has a fputs() statement with '\r\n' all over the place instead of '\n'. Is it necessary? Even on Windows (AFAIK) on almost never needs to bother with a '\r' in front or '\n'. fprintf() and fputs() will smartly write 0x0d 0x0a for a single '\n' so '\r' is almost never needed.
Probably the same thing happens in other source files as well. Please review.
Thanks.
I have figured out how to install Windows 10 directly into iSCSI LUNs for diskless clients. Tiny PXE Server is set up on the iSCSI server. A customized WinPE with iSCSI Initiator enabled, along with Win10 OS installation files, are put into a small (8-10GB) iSCSI LUN to support over-the-network OS installation. iPXE is used on the diskless clients. The high level steps are as follows:
Here's a sample iscsi.ipxe file:
================================================
#!ipxe
This script supports a one-time OS installation into a diskless client, as well as the subsequent OS bootups. The above example has iSCSI LUNs set up for two clients, but can be extended to an arbitrary number of clients. The iSCSI LUNs are set up to match the MAC address of the intended clients, so a given client will always sanboot from its corresponding iSCSI LUN.
By pre-formatting the iSCSI LUN disk partitions (for each client), the first time the client PXE boots, the sanboot command for the iSCSI LUN will fail, since the disk is still blank (though formatted), so the iPXE script falls through to the last line which connects to the "OS install" iSCSI LUN and boots to a WinPE command prompt. After running iSCSI Initiator (iscsicpl) to connect to the iSCSI LUN, OS installation can start in much the same way as for a local physical disk.
I have been successfully using ipxe-undionly.kpxe included in Tiny PXE Server 1.0.0.19.
Following is a batch file used to customize WinPE (64-bit) to add iSCSI Initiator support:
Add_iSCSI.cmd:
===================================
set WindowsPE=C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs
if not exist C:\Mounted_WIM md C:\Mounted_WIM
Dism /Mount-Image /ImageFile:C:\WinPE\media\sources\boot.wim /Index:1 /MountDir:C:\Mounted_WIM
Dism /Add-Package /Image:C:\Mounted_WIM /PackagePath:"%WindowsPE%\WinPE-WMI.cab"
Dism /Add-Package /Image:C:\Mounted_WIM /PackagePath:"%WindowsPE%\en-us\WinPE-WMI_en-us.cab"
Dism /Add-Package /Image:C:\Mounted_WIM /PackagePath:"%WindowsPE%\WinPE-NetFX.cab"
Dism /Add-Package /Image:C:\Mounted_WIM /PackagePath:"%WindowsPE%\en-us\WinPE-NetFX_en-us.cab"
Dism /Add-Package /Image:C:\Mounted_WIM /PackagePath:"%WindowsPE%\WinPE-Scripting.cab"
Dism /Add-Package /Image:C:\Mounted_WIM /PackagePath:"%WindowsPE%\en-us\WinPE-Scripting_en-us.cab"
Dism /Add-Package /Image:C:\Mounted_WIM /PackagePath:"%WindowsPE%\WinPE-PowerShell.cab"
Dism /Add-Package /Image:C:\Mounted_WIM /PackagePath:"%WindowsPE%\en-us\WinPE-PowerSHell_en-us.cab"
Dism /Add-Package /Image:C:\Mounted_WIM /PackagePath:"%WindowsPE%\WinPE-StorageWMI.cab"
Dism /Add-Package /Image:C:\Mounted_WIM /PackagePath:"%WindowsPE%\en-us\WinPE-StorageWMI_en-us.cab"
copy C:\windows\system32\iscsicpl.dll C:\Mounted_WIM\windows\system32
copy C:\windows\system32\iscsicpl.exe C:\Mounted_WIM\windows\system32
copy C:\windows\system32\en-us\iscsicpl.dll.mui C:\Mounted_WIM\windows\system32\en-us
copy C:\windows\system32\en-us\iscsicpl.exe.mui C:\Mounted_WIM\windows\system32\en-us
Dism /Get-Packages /Image:C:\Mounted_WIM
pause
Dism /Unmount-Image /MountDir:C:\Mounted_WIM /commit
===================================
This batch file works with Windows 10 ADK (Assessment and Deployment Kit) which can be downloaded from Microsoft.
A firewall opening for Tiny PXE Server is needed. This type of remote OS booting from iSCSI LUN apparently works only if the network interconnecting the server and clients is set to "private" (instead of "public") at the server. If Windows Server OS see the network as "unidentified", run gpedit.msc to change the network type from "public" to "private".
I'm working on a more detailed step-by-step procedure to be available later.
A big thanks to Erwan for Tiny PXE Server in making this possible.
http://www.rmprepusb.com/tutorials/bios_gpt_boot
I'm following the above tutorial, but currently I'm stuck because Grub4DOS unable to mount boot VHD. How can I create mountable VHD?
This is the VHD I've used to mount
https://drive.google.com/open?id=0B92szf-cumfrMTVuVFNBdGZ3Tm8
Hello all just thought I should say hi after a long nap
sad to see 911 forum go down in flames 
lot's of time spent there, and tons of my work all lost
I miss those days
To protect the data on my disk I am leveraging the self encrypting drive feature available on my SSD. For this I use a tool called sedutil [0]. This allows me to have access to hidden space on my SSD where a small disk image can be stored to unlock the drive. Basically it acts like small unencrypted USB stick that shadows the actual disk while being in a locked state. The drive will stay unlocked while it remains powered, so the machine can reboot without having to unlock the drive again, but once fully powered off, it will have to unlocked again. In its unlocked state it will just show the regular partition table as if the drive was never locked. The default disk image for unlocking the drive will just reboot once the drive has been unlocked, but I would rather not have to go through the BIOS twice, so instead I refresh the partition table in the Linux kernel and use kexec to boot in my actual OS located on the now unlocked drive. I have done this successfully for my Linux installations, but on one SSD I run Windows 10. The only case I have been able to find of being able to boot into Windows from Linux has been by using grub4dos [1]. So that is what I have tried:
kexec --load grub.exe --command-line='--config-file="chainloader (hd0,0)+1"' sync swapoff -a umount -a -r kexec --exec
However I got the following error. The only reference to this error that I could find by Googling was the actual source code, so that did not help much.
GRUB4DOS 0.4.6a 2018-01-10, root is (0x80,0) Processing the preset-menu ... Error: invalid boot indicator(0xC3) for entry 0.
So I did manage to kexec into grub4dos, but it takes a really long time to determine there is an error. I have not timed it, but it felt like at least a minute. The prompt showed up as well, but this took even longer to finally show up. Also, my USB keyboard did not function, but I read this to be quite common. I tried the following configs as well, but all resulted in the same error message as shown above:
kexec --load grub.exe --command-line='--config-file="chainloader (hd0,0)+1"' kexec --load grub.exe --command-line='--config-file="root (hd0,0); chainloader /bootmgr"' kexec --load grub.exe --command-line='--config-file="root (hd0,1); chainloader /bootmgr"'
I installed Windows 10 by letting it handle the partition itself and got the following:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk ├─sda1 8:1 0 549M 0 part └─sda2 8:2 0 465.2G 0 part
I am not quite sure which partition I should be using and if my config formats are correct, but since it took so long to figure out the was an error and since the root depicted in the error message remains the same, I am unsure how to proceed. Right now it is faster to just reboot, but if I would to be able to use grub4dos for this case, it should speed up things and would allow new use cases for kexec.
Does anyone have successfully kexec'ed into Windows 10 using grub4dos? Alternatives would be welcome as well.
Did I get my config correct?
Could the error have to do with the encryption? Something that can only be reset by rebooting, something I just happen to circumvent when kexec'ing into Linux, but is needed for grub4dos to function properly.
The machine on which I am running into this problem is using BIOS. The motherboard is a P6T Deluxe V2, if that is relevant. If any more information is needed, please ask.
[0]: https://github.com/Drive-Trust-Alliance/sedutil/wiki
[1]: http://reboot.pro/topic/7223-how-to-boot-directly-into-windows-from-kexecgrub4dos/
Cannot say (nor I want to check) WHEN it happened, but latest-latest aka:
http://grub4dos.chenall.net/downloads/grub4dos-0.4.6a-2018-03-03/
has this menu.lst embedded 
:
pxe detect
configfile
default 0
timeout 1
title find /menu.lst, /boot/grub/menu.lst, /grub/menu.lst
errorcheck off
configfile /boot/grub/menu.lst
configfile /grub/menu.lst
if "%@root%"=="(ud)" && calc *0x82A0=*0x82b9&0xff
if "%@root:~1,1%"=="f" && find --set-root --devices=f /menu.lst && configfile /menu.lst
find --set-root --ignore-floppies --ignore-cd /menu.lst && configfile /menu.lst
find --set-root --ignore-floppies --ignore-cd /boot/grub/menu.lst && configfile /boot/grub/menu.lst
find --set-root --ignore-floppies --ignore-cd /grub/menu.lst && configfile /grub/menu.lst
configfile http://b.chenall.net/menu.lst
errorcheck on
commandline
title commandline
commandline
title reboot
reboot
title halt
halt
I won't even make a comment on it 
, I respect too much the good grub4dos developers to risk offending them with my bluntness. 
Wonko
Mtools compiled for Windows (small patch applied to avoid crashing of mcopy when doing recursive copies):http://ubcdcreator.s...-crash-patch.7z
Update: mtools 4.0.18 for Windows can now be found in the download section:
http://reboot.pro/files/file/267-mtools/
Mtools 4.0.17 compiled for Windows
http://ubcdcreator.stopspazzing.com/mtools/mtools-4.0.17-win32.7z
Mtools manual page:
http://www.gnu.org/s...ual/mtools.html
Tutorial: Editing a 2880 kb floppy image of UBCD (FDUBCD FreeDOS image):
http://www.ultimateb...php?f=13&t=4077
That tutorial makes use of the more advanced parts of mtools than what is shown below.
mtools can replace the "need" for WinImage in many cases, when working with floppy images.
Easy example:
For example, it could be used to make easily make a F6 floppy image with WinVBlock or Firadisk.
For the WinVBlock working on Windows 7 tutorial, you need to make a F6 floppy image
http://reboot.pro/13738/
Contents of your WinVBlock F6 floppy:
* WinVBlk.cat
* WinVBlk.exe
* WinVBlk.Inf
* WVBlk32.sys
* sc.exe
* txtsetup.oem
Create and format a empty 1440 kb floppy image file with mformat:
mformat -C -f 1440 -v WINVBLOCK -i WinVBlock.img ::
If you already have an 1440k empty floppy image file, you won't need the "-C" switch:
mformat -f 1440 -v WINVBLOCK -i WinVBlock.img ::
Now we can copy the wanted files to the image with mcopy:
mcopy -i WinVBlock.img WinVBlk.cat WinVBlk.exe WinVBlk.Inf WVBlk32.sys sc.exe txtsetup.oem ::
Done 
./configure --enable-preset-menu=../preset_menu.lst
I am wondering what other hard drive image type does grub4dos support that isn't VHD or raw? I have been having lots of issues with those 2 formats. For example any VHD I make seem to give me a total sector warning, that the partition table sectors doesn't seem to match what it calculates, picture below. Also I know that Raw images that I mount , anything I write to it, just disappears and I know the drive is mapped directly and not indirectly using the mem option. I believe that Raw images are better than other disk images, which I want to use but can't seem to support writing to them using direct map? I can direct map a floppy image, any change to it on the a: drive seems to be on the disk image when I reboot. or can someone help me out with my issues?
