Easy2Boot v1.07 Video now on YouTube
Steve's blog about RMPrepUSB, Easy2Boot and USB booting and sometimes other stuff too! Don't forget to Subscribe! PDF eBooks here
Visit www.rmprepusb.com for over 140 Tutorials on USB booting or www.easy2boot.xyz for a unique USB multiboot solution.
Sunday, 1 September 2013
Saturday, 24 August 2013
Easy2Boot v1.07 now available
Download Version 1.07 here.
- Latest grldr gives better alphabetical sorting (e.g. _fred.iso now listed in E2B menu before afred.iso).
- .isope file extension support - if WinPE2/3/4 iso then when wpeinit runs, the iso will be loaded as a virtual CD/DVD. See here for more info.
- WinPE ISOs (.isope) can mount the .ISO after booting and user can define any drive letter for the ISO and auto-run a post-cmd batch file once ISO is loaded. See here for more info.
- ISOASK variable supported (is set, will ask user how to run every .iso). See here for more info.
- Can force any .iso to run as if it had a different file extension by creating a .mnu file for the iso file. See here for more details.
Sunday, 18 August 2013
E2B v1.07 Beta5
Another small change for Zalman ZM-VE200/300/400 CD emulator owners! You do not have to change the .iso file extension for E2B now.
This version allows you create a .mnu file for each .iso file that requires a different extension for E2B.
For instance, if you have a Hirens iso file and you want to run it with the .isowinvh file extension in E2B, but leave the hirens iso file with a .iso extension on the Zalman E2B drive, use this .mnu text:
title Hirens ISO\n Boot direct from Hirens ISO\n If running DOS utilities from an NTFS drive you may need to select the NTFS driver when offered a choice instead of AUTO
/%grub%/qrun.g4b force.isowinvh %MFOLDER%/Utility/Hiren's.BootCD.15.2.iso
boot
The force.isowinvh is a dummy filename (any filename will do!) followed by the extension that you want E2B to use. Whatever extension is specified in this first dummy parameter will be used to run the .iso file that is specified in the second parameter. So in this case, the Hirens .iso file will be run by E2B as if it had a .isowinvh file extension.
In the example above, the hirens iso file and .mnu file would be present in the \_ISO\UTILITIES\Utility folder or \_ISO\MAINMENU\Utility folder (i.e. at the \_ISO\xxxx\Utility level).
title Hirens ISO\n Boot direct from Hirens ISO\n If running DOS utilities from an NTFS drive you may need to select the NTFS driver when offered a choice instead of AUTO
/%grub%/qrun.g4b force.isowinvh %MFOLDER%/Utility/Hiren's.BootCD.15.2.iso
boot
The force.isowinvh is a dummy filename (any filename will do!) followed by the extension that you want E2B to use. Whatever extension is specified in this first dummy parameter will be used to run the .iso file that is specified in the second parameter. So in this case, the Hirens .iso file will be run by E2B as if it had a .isowinvh file extension.
In the example above, the hirens iso file and .mnu file would be present in the \_ISO\UTILITIES\Utility folder or \_ISO\MAINMENU\Utility folder (i.e. at the \_ISO\xxxx\Utility level).
Friday, 16 August 2013
E2B v1.07Beta 4 now available - BUGFIX!
bugfix for v 1.00 and all later versions - %MFOLDER% was set to ()/_ISO/xxx instead of /_ISO/xxx by AUTOMN.g4b. This meant that some sample .mnu files that used (bd)%MFOLDER% did not work and you needed to remove the (bd) portion to get them to work.
Beta4 fixes AUTOMN.g4b so that MFOLDER is now /_ISO/xxxx as it was in most previous Beta versions.
If you are having problems getting the sample .mnu files to work, try this new version!
See Easy2Boot V1 Tutorial 72a (bottom of page) for the download.
Beta4 fixes AUTOMN.g4b so that MFOLDER is now /_ISO/xxxx as it was in most previous Beta versions.
If you are having problems getting the sample .mnu files to work, try this new version!
See Easy2Boot V1 Tutorial 72a (bottom of page) for the download.
Thursday, 15 August 2013
E2B v1.07Beta3 now available
If you add the line
set ISOASK=1
to your \_ISO\MyE2B.cfg file, then any ISO file listed in the E2B menus will run as if the extension was .isoask (i.e. it will run the .iso and ask you to choose a way to run it).
This means if you have a Zalman CD/DVD USB HDD caddy, you do not have to have duplicate copies of all the iso files (e.g. have hirens.isowinvH for E2B and hirens.iso for the Zalman). All your files can be .iso but when running E2B, it will ask you how to run them.
set ISOASK=1
to your \_ISO\MyE2B.cfg file, then any ISO file listed in the E2B menus will run as if the extension was .isoask (i.e. it will run the .iso and ask you to choose a way to run it).
This means if you have a Zalman CD/DVD USB HDD caddy, you do not have to have duplicate copies of all the iso files (e.g. have hirens.isowinvH for E2B and hirens.iso for the Zalman). All your files can be .iso but when running E2B, it will ask you how to run them.
Easy2Boot 1.07 Beta 2 now available
This has enhanced WinPE2/3/4 ISO support.
Beta2a has minor change to add double-quotes around the iso filename when ImDisk is called to load the ISO - this should (may) allow filenames with spaces in them to work (e.g. SVR2012).
If you place a file that is the same filename as the ISO in the same folder as the WinPE ISO, e.g.
\_ISO\MAINMENU\WinPEx86ABC.isoPE
\_ISO\MAINMENU\WinPEx86ABC.cmd
WinPEx86ABC.cmd
===============
set ISOLETTER=S:
then if no <isoname>.cmd file exists then Y: is used, otherwise the letter set in your .cmd file is used. If Y: is already used then the next free letter will be used to mount the WinPE ISO.
Now .cmd files as well as .mnu and .txt files will not be listed in the menu.
This version also supports the .isoPE01 extension. This has the same function as .isoPE but swaps hd0 and hd1 over before booting to the ISO. This may be useful for some repair ISOs that expect hd0 to be the primary internal system disk.
Beta2a has minor change to add double-quotes around the iso filename when ImDisk is called to load the ISO - this should (may) allow filenames with spaces in them to work (e.g. SVR2012).
Wednesday, 14 August 2013
Easy2Boot v1.07Beta now available
This version recognises iso's with a .isoPE extension.
This can be used with Vista/7/8 WinPE ISOs. If the extension is .isoPE then when WinPE runs and wpeinit starts, the .ISOPE file will be automatically loaded in WinPE as a virtual CD/DVD drive.
This means that once the WinPE is fully loaded, it will have access to all the files in the ISO as a virtual CD/DVD drive.
Note that this only works if you use an E2B USB flash drive, or use an E2H USB HDD + USB 'Helper' Flash drive, as the \unattend.xml file is required to be on a 'removable' USB drive for this to work.
This version is available from the downloads section of the E2B Tutorial here.
There have also been some minor changes to the LOADISOxx.cmd files used for Vista/7/8 install ISOs but hopefully this should not affect their function at all.
This can be used with Vista/7/8 WinPE ISOs. If the extension is .isoPE then when WinPE runs and wpeinit starts, the .ISOPE file will be automatically loaded in WinPE as a virtual CD/DVD drive.
This means that once the WinPE is fully loaded, it will have access to all the files in the ISO as a virtual CD/DVD drive.
Note that this only works if you use an E2B USB flash drive, or use an E2H USB HDD + USB 'Helper' Flash drive, as the \unattend.xml file is required to be on a 'removable' USB drive for this to work.
This version is available from the downloads section of the E2B Tutorial here.
There have also been some minor changes to the LOADISOxx.cmd files used for Vista/7/8 install ISOs but hopefully this should not affect their function at all.
Monday, 5 August 2013
Easy2Boot v1.06
If you update your current E2B USB drive, it will make quite a few changes and you will need to delete some files from your existing E2B USB drive - otherwise you may get duplicate entries in the menu!
The big change in this version is that ALL files are sorted alphabetically. In previous versions you could either have all .mnu files listed in the menu first and then all payload (e.g. .iso) files OR all payload files first and then all .mnu files.
With version 1.06 .mnu and payload files are enumerated in one go, so the menu will list entries according to the files alphanumeric order. This means you can arrange the menu better (just sort the files by name in Windows Explorer to see what order they will be in). It also means that the boot is quicker as the whole \_ISO folder is only enumerated once instead of twice.
I have had to re-organise some files in the \_ISO\Mainmenu folder. Mainmenu.mnu is gone and so are the SubMenuxxx.mnu files. Instead we have some ZZxxxxx.mnu files. Obviously these will be listed last in the main menu.
Although all menu entries will now be listed in the menu according to their filename, it is important to realise two things:
1. If a .txt file is specified for a payload file, or a .mnu file is found, then the actual text that appears in the menu is that contained in the file.
e.g.
a.mnu (contains 'title X files')
z.iso
z.txt (contains 'title Runs z.iso')
then the menu will look like this
If you want to try the new version, you can download it here.
I recommend you make a new USB E2B drive and re-copy your payload files onto the drive.
If you want to just update your current E2B drive then you will need to delete the following files:
Files in \_ISO\MAINMENU folder
=========================
ZZSubMenuAntiVirus.mnu
ZZSubMenuAuto.mnu
ZZSubMenuBackup.mnu
ZZSubMenuDos.mnu
ZZSubMenuLinux.mnu
ZZSubMenuUtilities.mnu
ZZSubMenuWinPE.mnu
ZZWindowsInstall.mnu
ZZZF7BootHdd.mnu
ZZZF8ReloadMenu.mnu
If you want the sub-menu entries for the sub-folders to be listed first in the main menu, just add $ in front of the first 8 ZZxxxx.mnu files.
Note that ZZZF7BootHdd.mnu and ZZZF8ReloadMenu.mnu must not be deleted and must be alphabetically last so that the F9 and F10 entries, which are automatically added to the end of the menu by E2B, will be listed in order and look nice!
Please add a comment if you have tried this and give me your feedback!
The big change in this version is that ALL files are sorted alphabetically. In previous versions you could either have all .mnu files listed in the menu first and then all payload (e.g. .iso) files OR all payload files first and then all .mnu files.
With version 1.06 .mnu and payload files are enumerated in one go, so the menu will list entries according to the files alphanumeric order. This means you can arrange the menu better (just sort the files by name in Windows Explorer to see what order they will be in). It also means that the boot is quicker as the whole \_ISO folder is only enumerated once instead of twice.
I have had to re-organise some files in the \_ISO\Mainmenu folder. Mainmenu.mnu is gone and so are the SubMenuxxx.mnu files. Instead we have some ZZxxxxx.mnu files. Obviously these will be listed last in the main menu.
Although all menu entries will now be listed in the menu according to their filename, it is important to realise two things:
1. If a .txt file is specified for a payload file, or a .mnu file is found, then the actual text that appears in the menu is that contained in the file.
e.g.
a.mnu (contains 'title X files')
z.iso
z.txt (contains 'title Runs z.iso')
then the menu will look like this
X files2. Files in sub-folders will be listed alphabetically as each folder name is discovered. This means that a .mnu file entry from a file at \_ISO\MAINMENU\A\Zlot.mnu will appear in the main menu before a payload file at \_ISO\MAINMENU\backup.iso.
Runs z.iso
If you want to try the new version, you can download it here.
I recommend you make a new USB E2B drive and re-copy your payload files onto the drive.
If you want to just update your current E2B drive then you will need to delete the following files:
All \_ISO\MAINMENU\SubMenuxxxxx.mnu filesNote that you can now control the position of each individual menu entry (except F9 and F10 which will always be last in the menu) by renaming the payload and .mnu files.
\_ISO\MAINMENU\mainmenu.mnu
\_ISO\e2b\grub\adf2mm.g4b (no longer required)
Files in \_ISO\MAINMENU folder
=========================
ZZSubMenuAntiVirus.mnu
ZZSubMenuAuto.mnu
ZZSubMenuBackup.mnu
ZZSubMenuDos.mnu
ZZSubMenuLinux.mnu
ZZSubMenuUtilities.mnu
ZZSubMenuWinPE.mnu
ZZWindowsInstall.mnu
ZZZF7BootHdd.mnu
ZZZF8ReloadMenu.mnu
If you want the sub-menu entries for the sub-folders to be listed first in the main menu, just add $ in front of the first 8 ZZxxxx.mnu files.
Note that ZZZF7BootHdd.mnu and ZZZF8ReloadMenu.mnu must not be deleted and must be alphabetically last so that the F9 and F10 entries, which are automatically added to the end of the menu by E2B, will be listed in order and look nice!
Please add a comment if you have tried this and give me your feedback!
Saturday, 3 August 2013
Easy2Boot v1.05
This version has a few minor changes:
1. Some more sample .mnu files added to the docs folder
2. A new 'Jolene' menu theme added to docs folder (see below) For Star Trek fans!
3. Ability to suppress the E2B file enumeration messages by setting a new grub4dos variable in your MyE2B.cfg file.
set redir=> nul
If you also want to suppress the E2B progress messages (not recommended as they may be useful on systems with bad BIOSes) then add this line:
set redirp=> nul
See the \_ISO\Sample_MyE2B.cfg file (end) for an example of these two lines (note there is a space between the > and nul).
New 'Jolene' sample background and borderless menu (also redir is also set, so silent file enumeration is enabled).
1. Some more sample .mnu files added to the docs folder
2. A new 'Jolene' menu theme added to docs folder (see below) For Star Trek fans!
3. Ability to suppress the E2B file enumeration messages by setting a new grub4dos variable in your MyE2B.cfg file.
set redir=> nul
If you also want to suppress the E2B progress messages (not recommended as they may be useful on systems with bad BIOSes) then add this line:
set redirp=> nul
See the \_ISO\Sample_MyE2B.cfg file (end) for an example of these two lines (note there is a space between the > and nul).
New 'Jolene' sample background and borderless menu (also redir is also set, so silent file enumeration is enabled).
Monday, 22 July 2013
Easy2Boot and XBMCBuntu
I have added a new .mnu file that can be used with an XMBCBuntu 12.2 ISO file to allow you to run XBMCBuntu with persistence. Please read the text in the .mnu file for details. The .mnu file is at the bottom of the Tutorial 72a page.
Friday, 19 July 2013
Puppy linux for E2B with persistence
If you want the 'Save on Exit' feature to work for Puppy Linux ISOs, you will need to add a .mnu file.
I have added two .mnu files to the bottom of the Tutorial 72a E2B page. One is for E2B USB HDDs and the other is for E2B USB Flash drives.
The .mnu file is for Puppy 5.4.3 but you can easily edit it for any other version just by changing the ISO filename.
For USB HDDs the cheat code pmedia=usbhd is required. For USB Flash drives the cheat code pmedia=usbflash is required. These codes are already in the .mnu file.
Puppy seems to work well on my Acer 7741G notebook. Audio, Video, trackpad scroll bar support and WiFi all worked on first boot.
I have added two .mnu files to the bottom of the Tutorial 72a E2B page. One is for E2B USB HDDs and the other is for E2B USB Flash drives.
The .mnu file is for Puppy 5.4.3 but you can easily edit it for any other version just by changing the ISO filename.
For USB HDDs the cheat code pmedia=usbhd is required. For USB Flash drives the cheat code pmedia=usbflash is required. These codes are already in the .mnu file.
Puppy seems to work well on my Acer 7741G notebook. Audio, Video, trackpad scroll bar support and WiFi all worked on first boot.
Wednesday, 17 July 2013
RMPrepUSB v2.1.708 - Change partition type menu option added
V2.1.708 is now available. It has the latest grub4dos version (compatible with E2B v1.04) and also has a new menu option to change the primary partition type number.
This new option was added primarily to allow people to format a USB drive with a FAT32 partition and then use the new menu option to change the type to EEh which is the partition type number for EFI partitions. This means you can now create an EFI FAT32 partition which will boot to grub4dos if you install grub4dos, and boot to an EFI OS or secondary bootloader if you install rEFInd or gummiboot.
This new option was added primarily to allow people to format a USB drive with a FAT32 partition and then use the new menu option to change the type to EEh which is the partition type number for EFI partitions. This means you can now create an EFI FAT32 partition which will boot to grub4dos if you install grub4dos, and boot to an EFI OS or secondary bootloader if you install rEFInd or gummiboot.
Monday, 15 July 2013
Easy2Boot v1.04 (minor changes)
The new version has only minor changes (not worth updating if you already have E2B working OK).
1. DPMS2 - minor changes to fix some issues with some drivers.
2. Improved grldr version warning
3. XP Installs Step 2 now allows user to press D or A to debug or abort
P.S. new version RMPrepUSB 2.1.708 installs the same version of grub4dos as used by E2B.
1. DPMS2 - minor changes to fix some issues with some drivers.
2. Improved grldr version warning
3. XP Installs Step 2 now allows user to press D or A to debug or abort
P.S. new version RMPrepUSB 2.1.708 installs the same version of grub4dos as used by E2B.
Thursday, 11 July 2013
E2B v1.03 available (includes DPMS2)
Easy2Boot v1.03 can now be downloaded here.
It is essentially v1.01 of E2B + DPMS2 + small changes/bugfixes:
1. DPMS2 added (but not the mass storage drivers - you must download and add these files yourself)
2. New grub4dos version - files/folders can now be sorted alphabetically and are NOT case sensitive (bugfix in grub4dos).
3. Bugfix for large HDDs (>1TB) - E2B reported bad BIOS when it wasn't!
4. Change to XP Step 1 install code - now correct choice is automatically made for the user for most questions.
It is essentially v1.01 of E2B + DPMS2 + small changes/bugfixes:
1. DPMS2 added (but not the mass storage drivers - you must download and add these files yourself)
2. New grub4dos version - files/folders can now be sorted alphabetically and are NOT case sensitive (bugfix in grub4dos).
3. Bugfix for large HDDs (>1TB) - E2B reported bad BIOS when it wasn't!
4. Change to XP Step 1 install code - now correct choice is automatically made for the user for most questions.
Friday, 5 July 2013
DPMS 2 Update Package now available!
Update: You can now download Easy2Boot+DPMS2 in one download - see Tutorial 72a for the link.
Using E2B and a vanilla unmodified XP ISO, you can now install to any SATA/RAID/SCSI system without needing to integrate the mass storage drivers into the ISO!
Auto-F6 SRS floppies made. Adds [Config.xxx] sections to txtsetup.oem so should work with scsi drives too.
If using an E2B USB-HDD and FiraDisk then you need to load the ISO into memory (answer Y to the question just after DPMS2 runs).
If using an E2B USB-flash drive and FiraDisk then you don't need to load the ISO into memory (just press Enter or let it timeout).
Includes improved alphabetical menu sort code for E2B.
Instructions on how to use it here.
Using E2B and a vanilla unmodified XP ISO, you can now install to any SATA/RAID/SCSI system without needing to integrate the mass storage drivers into the ISO!
Auto-F6 SRS floppies made. Adds [Config.xxx] sections to txtsetup.oem so should work with scsi drives too.
If using an E2B USB-HDD and FiraDisk then you need to load the ISO into memory (answer Y to the question just after DPMS2 runs).
If using an E2B USB-flash drive and FiraDisk then you don't need to load the ISO into memory (just press Enter or let it timeout).
Includes improved alphabetical menu sort code for E2B.
Instructions on how to use it here.
You can disable alphabetical sorting of menus (if you find it too slow), by adding
set NOSORT=1
to your MyE2B.cfg file.
Sunday, 30 June 2013
DPMS 2 coming soon!
I have heavily modified chenalls DPMS script during the last week and have been testing it on both virtual and real hardware.
In VBOX I have tested in IDE, SATA(AHCI ICH8) and SCSI systems. These all install XP correctly in text-mode and GUI Mode.
I also tested on a real ICH8 notebook in IDE and SATA mode with success.
I have had to test using Firadisk and WinVBlock drivers so this doubled the testing.
I have also added code to copy the PnpInstances section over to the txtsetup.oem file, so it should work with most SCSI systems.
I have got to the stage now where it all works but the code is not pretty!
I should be able to make the early package for E2B available for anyone who has made donations soon.
I will then be making some YouTube videos demonstrating E2B and the DPMS auto-detection feature and after a month or so I will release the DPMS Update package for everyone.
It has been a hard week and there have been lots of frustrations (twice I 'broke' the code without realising it until later and then spent a day on each problem trying to find out what had gone wrong!) - really frustrating!
David B's VM Starter app has certainly helped as I can boot from my USB on VBox and have full read/write access to the USB stick.
The new DPMS 2 batch file also copies the F6 floppy txtsetup.oem's and directory listings to some log files on the USB stick. This will help in the event of any problems found by users as they can just send me these 'log' files.
Here is the DPMS output on a VBOX SCSI system.
In VBOX I have tested in IDE, SATA(AHCI ICH8) and SCSI systems. These all install XP correctly in text-mode and GUI Mode.
I also tested on a real ICH8 notebook in IDE and SATA mode with success.
I have had to test using Firadisk and WinVBlock drivers so this doubled the testing.
I have also added code to copy the PnpInstances section over to the txtsetup.oem file, so it should work with most SCSI systems.
I have got to the stage now where it all works but the code is not pretty!
I should be able to make the early package for E2B available for anyone who has made donations soon.
I will then be making some YouTube videos demonstrating E2B and the DPMS auto-detection feature and after a month or so I will release the DPMS Update package for everyone.
It has been a hard week and there have been lots of frustrations (twice I 'broke' the code without realising it until later and then spent a day on each problem trying to find out what had gone wrong!) - really frustrating!
David B's VM Starter app has certainly helped as I can boot from my USB on VBox and have full read/write access to the USB stick.
The new DPMS 2 batch file also copies the F6 floppy txtsetup.oem's and directory listings to some log files on the USB stick. This will help in the event of any problems found by users as they can just send me these 'log' files.
Here is the DPMS output on a VBOX SCSI system.
Friday, 28 June 2013
Description of txtsetup.oem files for F6 floppy disks for Windows XP Mass Storage drivers
When you make your own txtsetup.oem file, you can just combine several txtsetup.oem files by simply joining them in Notepad.
There are some rules for txtsetup.oem and I will explain the syntax by highlighting the bits that need to match:
KEY
DriverKey - different Config sections can be defined for each driver
Service - matches the driver name (convention that drivers use)
ID - ID of the device which may have more than one PCI ID
So in the txtsetup.oem file below, the keys which are the same colour need to match each other. You may find that in some txtsetup.oem files, both the ID and the DriverKey are the same, but they don't need to be!
[Disks]
d1="DPMS Installation Disk by chenall(diskd)",\disk1,\
[scsi]
iastor7="Intel ICH9/ICH10 SATA AHCI/RAID RST 11.2"
[Files.scsi.iastor7]
inf=d1,iaAHCI.inf
catalog=d1,iaAHCI.cat
driver=d1,iastor.sys,iastor6
[HardwareIds.scsi.iastor7]
id="PCI\VEN_8086&DEV_3B29&CC_0106","iastor"
[Config.iastor6]
value = parameters\PnpInterface,5,REG_DWORD,1
[Defaults]
scsi=iastor7
You can only have one driver= line (any others will be ignored).
The ONLY difference is that in one txtsetup.oem you set the [Defaults] section to your AHCI driver, and on the other txtsetup.oem file you set the [Default] to Firadisk.
(in fact, the txtsetup.oems don't have to have the non-default sections - e.g. on the FiraDisk default txtsetup.oem you can remove all the AHCI driver sections if you want to).
XP text-mode setup will get confused if you don't use the same disk name tag file for both disks and have the same files on both disks, so you need to have all the driver files on both disks so that 'Drive A:' (which is whatever it accessed last just before the 'copyfiles' stage) will always contain the correct files when it tries to copy them from the F6 floppy just after formatting the internal hard disk. (It is just possible to have different disk tag files but you will still need both sets of drivers on each disk and you have to swap over the disk tags (i.e. disk0 oemsetup has 'disk1' as a tag and disk1 oemsetup has 'disk0' as a tag). It is MUCH easier just to use the same tag file and same contents on both disks!
For more details about txtsetup.oem syntax, see here - but it does not mention the fact that the driver.sys name must be the same as the SERVICE name.
I hope this saves someone hours of work!
cheers
Steve
There are some rules for txtsetup.oem and I will explain the syntax by highlighting the bits that need to match:
KEY
DriverKey - different Config sections can be defined for each driver
Service - matches the driver name (convention that drivers use)
ID - ID of the device which may have more than one PCI ID
So in the txtsetup.oem file below, the keys which are the same colour need to match each other. You may find that in some txtsetup.oem files, both the ID and the DriverKey are the same, but they don't need to be!
[Disks]
d1="DPMS Installation Disk by chenall(diskd)",\disk1,\
[scsi]
iastor7="Intel ICH9/ICH10 SATA AHCI/RAID RST 11.2"
[Files.scsi.iastor7]
inf=d1,iaAHCI.inf
catalog=d1,iaAHCI.cat
driver=d1,iastor.sys,iastor6
[HardwareIds.scsi.iastor7]
id="PCI\VEN_8086&DEV_3B29&CC_0106","iastor"
[Config.iastor6]
value = parameters\PnpInterface,5,REG_DWORD,1
[Defaults]
scsi=iastor7
If you want to specify a default driver, just have one entry (as shown) in the [Defaults] section and only have one [Defaults] section in the whole file.
\disk1 is a file that must be on the source F6 floppy disk. XP will identify which floppy the driver is on by looking for this file.
The PCI IDs used in txtsetup.oem is NOT checked by Setup - whatever driver you tell it to load is loaded by Setup - if the driver reports that if failed to load or recognise your hardware, Setup will report a problem.
If you want to add more txtsetup.oem files, just add them on to the existing txtsetup.oem file, one after the other (but just have one [Defaults] section).
Note that the driver.sys name MUST match the 'service' name used in the HardwareID driver line.
Note that the (single) driver.sys file specified in the driver= line will be the one copied over to the hard disk. Therefore, this needs to be the one that is mentioned in the INF file, otherwise XP GUI Mode setup will complain about a driver missing from C:\Windows\OEMDir at about the 34 minute mark!
However, if you want to copy across more driver files than just the one allowed per section (or any type and number of extra files), just add more 'catalog=d1,fred.sys' lines, as many as you like! The files specified will then be copied across to the hard disk C:\Windows\OEMDir folder.
For FiraDisk:
[Disks]
d1="DPMS Installation Disk by chenall(diskf)",\disk1,\
[scsi]
firadisk=FiraDisk_Driver
[HardwareIds.scsi.firadisk]
id="PCI\firadisk","firadisk"
[Files.scsi.firadisk]
inf=d1,firadisk.inf
catalog=d1,firadisk.cat
driver=d1,firadisk.sys,firadisk
[Defaults]
scsi=firadisk
Loading two drivers automatically (without pressing F6)
You can get XP to automatically load by default both an AHCI driver AND FiraDisk by having almost IDENTICAL floppy disks each containing ALL of the files needed by both the AHCI driver and the FiraDisk driver. Both disks should have the same identifying disk tag file (e.g. disk1 in this case).The ONLY difference is that in one txtsetup.oem you set the [Defaults] section to your AHCI driver, and on the other txtsetup.oem file you set the [Default] to Firadisk.
(in fact, the txtsetup.oems don't have to have the non-default sections - e.g. on the FiraDisk default txtsetup.oem you can remove all the AHCI driver sections if you want to).
XP text-mode setup will get confused if you don't use the same disk name tag file for both disks and have the same files on both disks, so you need to have all the driver files on both disks so that 'Drive A:' (which is whatever it accessed last just before the 'copyfiles' stage) will always contain the correct files when it tries to copy them from the F6 floppy just after formatting the internal hard disk. (It is just possible to have different disk tag files but you will still need both sets of drivers on each disk and you have to swap over the disk tags (i.e. disk0 oemsetup has 'disk1' as a tag and disk1 oemsetup has 'disk0' as a tag). It is MUCH easier just to use the same tag file and same contents on both disks!
For more details about txtsetup.oem syntax, see here - but it does not mention the fact that the driver.sys name must be the same as the SERVICE name.
I hope this saves someone hours of work!
cheers
Steve
Tuesday, 25 June 2013
E2B DPMS package available for testing
Easy2Boot Upgrade DPMS package (BETA) now available for BETA testers only!
News - July 2013: New DPMS2 is now integrated in Easy2Boot and it is automatic - no need to press F6!
This enhances the current XP install from ISO menu. If you add the updated E2B files and download and add the DriverPack Mass Storage driver package (approx. 8MB download but 50MB when unzipped) you will have the option to autodetect the correct AHCI/SATA/RAID driver.
The DPMS package from chenall (and heavily modified by me) will auto-generate the F6 floppy disk image with the correct driver files. This MassStorage download seems the most bug free at the moment...
DP_MassStorage_wnt5_x86-32_1306202.7z - 9.18 MB a9922b31453aec34d46bdea5eb5a916f4f03589c
Or try Chenalls latest DPMS and just extract the D folder and DriverPack.ini (not dpms.bat!).
The installation method is still the same - you must manually use F6 and select the AHCI driver + Firadisk driver ( + WinVBlock driver (optional)) - however usually there will only be one AHCI driver present in the F6 list, so you will not have to guess which one to pick! Also, as the DriverPack contains non-Intel drivers, E2B XP installs from ISO should now work on non-Intel AHCI platforms.
Instructions are in the ReadMe.txt file.
News: After hours of hair pulling and midnight oil, I have a DPMS version now which loads firadisk AND the AHCI driver automatically (no F6 press required)! It is integrated in the Easy2Boot v1 download.
cheers
Steve
Friday, 21 June 2013
E2B Upgrade Package available
If anyone has made a PayPal donation to me for E2B or has contributed to its development, I would like to reward them with the E2B Upgrade Package. This is currently at v1.01 and the idea is that any further developments of E2B will go into this Upgrade Package.
The first version is v1.01 and will modify E2B so it lists the menus in alphabetical (alphanumeric) order.
So all you need to do is rename your ISOs to re-arrange the listing order, e.g.
_1fred.iso
_2doris.iso
_3george.iso
_4debian.iso
_5plop.iso
etc.
To have nice titles, just make a .txt file for them, e.g.:
_1fred.txt
=======
If you have any .mnu files, you can also cause their entries to be listed in sequence too, just by changing the name of the .mnu file - e.g. _1Ubuntu_with_Persistence.mnu would be listed before the other .mnu entries. You can even rename the SubMenuxxxxx.mnu files in the MainMenu folder to change the order they are listed in.
Depending on the MNUFIRST setting in your MyE2B.cfg config file, either all payload (ISO) files will be listed alphanumerically first in the main menu or all .mnu file entries will be listed first. You cannot have .iso files interspersed with .mnu files in a menu.
The first version is v1.01 and will modify E2B so it lists the menus in alphabetical (alphanumeric) order.
So all you need to do is rename your ISOs to re-arrange the listing order, e.g.
_1fred.iso
_2doris.iso
_3george.iso
_4debian.iso
_5plop.iso
etc.
To have nice titles, just make a .txt file for them, e.g.:
_1fred.txt
=======
title This runs fred direct from the iso \n This is help text for fred
If you have any .mnu files, you can also cause their entries to be listed in sequence too, just by changing the name of the .mnu file - e.g. _1Ubuntu_with_Persistence.mnu would be listed before the other .mnu entries. You can even rename the SubMenuxxxxx.mnu files in the MainMenu folder to change the order they are listed in.
Depending on the MNUFIRST setting in your MyE2B.cfg config file, either all payload (ISO) files will be listed alphanumerically first in the main menu or all .mnu file entries will be listed first. You cannot have .iso files interspersed with .mnu files in a menu.
Wednesday, 19 June 2013
Easy2Boot v1.00 now 'officially' released!
I have decided to release E2B now as v1.00. It is virtually identical to the last BETA (just a few changes to the colour syntax in E2B.cfg as grub4dos now supports names for the color command - e.g. color normal=blue/light-blue, but I have left the old colour variable definitions in so older MyE2B.cfg files will still work.
Now it is officially released, I suppose I can expect a flood of bug reports (as this always seems to be what happens when people are afraid to try beta s/w)!
Now it is officially released, I suppose I can expect a flood of bug reports (as this always seems to be what happens when people are afraid to try beta s/w)!
Subscribe to:
Posts (Atom)