Wikis USB-Boot (en) 
Howto Boot OS/2 - eCS from USB Mass Storage Devices ( MSD ) - English Version - Wiki
Version 0.7.3 Last Update: 2008-06-19
1 Introduction
1.1 About the Document and its Authors
- Cooperative Work based on the Wiki method
- Coauthors (In alphabetic order by first name):
- Bob Eager
(http://www.tavi.co.uk/os2pages/index.html),Doug Bissett, Ed Durrant, Jan van Wijk (http://www.dfsee.com), Juergen Ulbts (http://www.juergen-ulbts.de/), Lothar Joeger, Martin Kiewitz, Mike Luther,
Oliver Rick, Peter Brown, Peter Rehfisch, Rainer D. Stroebel, Sigurd Fastenrath (http://www.sigurd-fastenrath.de), Steven Levine, William L. Hartzell
Initial author and moderator/editor: Rainer D. Stroebel(mailto:RainerStroebelxyz@xyzt-online.de) The Coauthors of the initial document have provided most of there input in newsgroups of comp.os.os2... and DFSee support forums and eMails, and some of it directly to this Wiki. Thanks to Roland Schmalenberg and the Team OS/2 Köln/Bonn e.V for hosting and technical support / administration of the Wiki
1.2 History ( Logical View / not the version control of the Wiki )
0.0 2006-08-11 Thread:
"Boot from USB PRM (Partitioned Removable Media ) failed
after loading OS2LVM.DMD error:
OS/2 is unable to operate your hard disk or diskette drive"
on comp.os.os2.bugs . Actually there are 2 threads,
one starting 11. Aug 2006 with 62 messages
and an follow up starting at xx jan, 2007 with 2 messages.
( Printout of the Thread about 60 pages!! )
0.4 2007-01-xx eMail Dialog with Jan van Wijk,
Jan does a great job with evolutions in DFSee 8.11
0.5 2007-01-25 Start production of the Initial Document for the Wiki
copy the existing texts to the Wiki, structuring and editing
0.6 2007-02-09 Chapter: Problem reports / Found Defects in the Research
done documentation and research on problems
Thanks to Jan for the participation
moved topics to sub wikis
0.6.1 2007-02-15 Add config.sys code: Case: Boot Large Floppy LVM
detected Wiki Edit Problem with backslash in config.sys code
0.6.2 2007-02-19 new functions of DFSee V8-11 integrated to the Wiki
0.6.3 2007-02-20 add test result usage of the IBM BMGR,
Raw ideas for PRM LVM booting
hardware and software compatibility stuff
0.6.4 2007-02-25 Add picture and some text
0.6.5 2007-02-28 new text has been added, new chapter: The Warp Boot Sequence,
new paragraphs/SubWiki about compatibility
0.6.5 2007-03-01 Alternate Bootmanager GRUB text add
0.6.6 2007-03-08 OS/2 Boot sequence / problem with GRUB BMR Code
0.6.7 2007-03-14 add case Boot PRM non LVM to WPS thanks to Peter Rehfisch
0.6.8 2007-07-19 add Problem Dummy disk with 0 Cylinders resulting a size of 0 MB
0.6.9 2008-01-12 add facts /ref about Windows Vista MBR
0.7.0 2008-01-19 add eSATA / SATA HW to Test Environment
0.7.1 2008-01-27 add Chapters about the EeePC - Info from ED Durrant
0.7.2 2008-01-28 add screen shots eCS Log and Desktop of the ASUS EeePC
0.7.3 2008-01-30 add EeePC text and T41 BIOS problem: no SATA HDD in boot startup menu
The physical view of the changes is automatical maintained by the system.
You can find the list in the SubWiki: Wiki eCS OS/2 USB Boot en Last-Changes
1.3 to do
a lot -:)
Currently the main focus is to document the positive result and the problem descriptions of the detected problems / bugs.
By authoring a comprehensive problem documentation we structure, verify and rethink the nature of the problem.
Good, exact, detailed, verified problem description is 50% of the solution :-)
Present the solution and problems as input to the readers works.
The introduction chapters currently are rudimentary. Here is more time and effort required.
The main focus is to produce solutions. If we have solutions, we can go to the next step to present the solutions for early adapter. The Feedback improves the solution and the presentation of it.
1.4 Usage of SubWiki's
The main purpose of the usage of SubWiki in this document is to keep the main Wiki at a manageable size for the reader and for the authors! The table of contents should contain / display all of the structure. Problem Descriptions are good candidates for SubWiki's. If the description is stored in an SubWiki, you can print the problem description by printing the SubWiki.
An other reason is a technical one: Currenty the size of the main wiki is limited by program restrictions and the wiki has grown to bounce up to this limit :-)
1.5 Terminology
BMGR Bootmanager
BR Boot Record - VBR Volume Boot Record - PBR Partition Boot Record - Definition / Description by Wikipedia (http://en.wikipedia.org/wiki/Volume_Boot_Record)
CF CompactFlash Cards
eCS eComStation
INT 13, INT 13X - Definition / Description by Wikipedia (http://en.wikipedia.org/wiki/INT_13)
Large Floppy ( BigFloppy , USBZip, Superfloppy )
LILO LInux LOader - Definition / Description by Wikipedia - en (http://en.wikipedia.org/wiki/LILO_%28boot_loader%29) - de (http://de.wikipedia.org/wiki/LILO)
LVM Logical Volume Manager
MBR Master Boot Record - Definition / Description by Wikipedia (http://en.wikipedia.org/wiki/Master_Boot_Record)
PBP BIOS Parameter Block - Definition / Description by Wikipedia (http://en.wikipedia.org/wiki/BIOS_parameter_block)
PRM Partitioned Removable Media
USB Universal Serial Bus
USBMSD USB Mass Storage Device
USB Stick, USB Key, USB Flash Drive, USB Hard Disk, external HHD s, USB Pendrive, USB Thumb Drive (TM) etc.
USB Flash Drive - Definition / Description by Wikipedia English (http://en.wikipedia.org/wiki/USB_flash_drive)
USB Stick - Definition / Description by Wikipedia German (http://de.wikipedia.org/wiki/USB-Stick)
2 The Warp Boot Sequence
Basic knowledge about the Warp boot sequence are required. You should know, what your system and you do :-)
Here are some sources to the knowledge:
The warp boot seQunce
2.1 Booting from Large Floppy
- Turning on the computer - power good signal from power-supply
- Power On Self Test ( POST ) by the BIOS
- Loading the Bootstrap program in the BR - OS/2 !! SYS01475
- OS2BOOT Loads the operating system loader (skipped with Veits OS2LDR.SEK)
- OS2LDR loads the operating system (kernel)
- Processing the CONFIG.SYS file
- the system is in real mode and process the BASEDEV statements
- After processing the last Basedev= *.DMD statement, the system switch to protected mode
- START and RUN statements execute from config.sys
- the system is in real mode and process the BASEDEV statements
- The main SHELL, either the Workplace Shell + STARTUP.CMD or just CMD.EXE are started
- The Boot process is complete
2.2 Booting from Partitioned Media - Primary Partition - without IBM BMGR Support
- Turning on the computer - power good signal from power-supply
- Power On Self Test ( POST ) by the BIOS
- Loading the Bootstrap program in the MBR - OS/2 !! SYS01475
Looking for the active flag in the Partition Table PT for a flaged primary partition
Load the Volume Boot Record ( Partition Boot Record )
Pass control to the boot code of the loaded record
load OS2BOOT and pass control to it - OS2BOOT Loads the operating system loader OS2LDR
- OS2LDR loads the operating system (kernel)
- Processing the CONFIG.SYS file
- the system is in real mode and process the BASEDEV statements
- After processing the last Basedev= *.DMD statement, the system switch to protected mode
- START and RUN statements execute from config.sys
- the system is in real mode and process the BASEDEV statements
- The main SHELL, either the Workplace Shell + STARTUP.CMD or just CMD.EXE are started
- The Boot process is complete
2.3 Booting from Partitioned Media - Primary / Logical Partition with IBM BMGR Support
- Turning on the computer - power good signal from power-supply
- Power On Self Test ( POST ) by the BIOS
- Loading the Bootstrap program in the MBR - OS/2 !! SYS01475
Looking for the active flag in the Partition Table PT for a flaged primary partition
Load the Volume Boot Record ( Partition Boot Record )
Pass control to the boot code of the loaded record
load the IBM OS/2 Boot Manager and pass control to it - execute the Boot manager code / logic
- built the boot manager menu base on the input from the HDD s partiton information, file system type, boot mananger flag in DLAT
- execute logic to determine the boot drive letter for each menu entry
- display the menu and wait for user entry / decision witch entry to boot
- Load the Volume Boot Record ( Partition Boot Record ) for / from the selected entry
Pass control to the boot code of the loaded record
load OS2BOOT and pass control to it
- OS2BOOT Loads the operating system loader OS2LDR
- OS2LDR loads the operating system (kernel)
- Processing the CONFIG.SYS file
- the system is in real mode and process the BASEDEV statements
- After processing the last Basedev= *.DMD statement, the system switch to protected mode
- START and RUN statements execute from config.sys
- the system is in real mode and process the BASEDEV statements
- The main SHELL, either the Workplace Shell + STARTUP.CMD or just CMD.EXE are started
- The Boot process is complete
2.4 The OS/2 Master Boot Record - I13 I13X Test and Flag
The code in the MBR establishes (by calling INT 13H) whether the INT 13H extensions are present. It then leaves a flag in low memory to indicate the presence or absence of support. This flag is used by BM, and by the various boot sectors, to save them doing the same test.
Unless the bootmanager GRUB actually sets that flag (which is, I believe, an OS/2 'thing') then the BM and boot sectors will assume INT 13H extensions are not present...
The actual test is in the MBR:
; Check for presence of INT 13H extensions; if present, set flag at
; 0030:0000 to 'I13X', otherwise set it to 0.
;
SETI13X PROC NEAR
;
MOV AH,41H ; see if INT 13H extensions present
MOV BX,MAGIC2 ; needed too - also DL = drive
INT 13H ; do it
JC SHORT SETI10 ; j if not supported at all
CMP BX,MAGIC ; double check
JNE SHORT SETI10 ; j if not supported
CMP AH,21H ; EDD 1.1 supported?
JB SHORT SETI10 ; j if not
TEST CL,1 ; packet structure device access?
JZ SHORT SETI10 ; j if not supported
MOV EAX,58333149H ; 'I13X'
JMP SHORT SETI20 ; set up for exit
;
SETI10: XOR AX,AX ; store zero for no support
;
SETI20: PUSH INFOSEG ; store at segment 3000:0000 (0030:0000)
POP FS
MOV FS:INF_FLG,EAX ; store it
Author of text snippet is Bob Eager (http://www.tavi.co.uk/os2pages/index.html) in Thread: "Is grub on MBR OK for Linux/OS/2 dual boot" on comp.os.os2.setup.misc 2003-03-30
and author of the DOS Utility EXTDISK (http://www.tavi.co.uk/os2pages/extdisk.html) to display presence of INT 13H extensions
An other interressting snippet from the same tread:
> Trevor Hemsley, Brighton, UK > > How utterly stupid. So if I install something after OS/2 that rewrites > the MBR gratuitously with a copy of its own then my >8GB OS/2 > partition magically stops booting. Sounds like a bug to me. Doesn't > that mean that installing *any* MS o/s post-OS/2 will break it? I > think they _all_ rewrite the MBR on install to one of their choosing. Yes. The silly thing is the code isn't that much smaller anyway. The one place it needs to be small is in the MBR, where there's least room. I wonder if there was some other agenda....like remote booting - that started it. Bob Eager
The test system with Bootmanager Grand Unified Bootloader (GRUB) V 0.97 in BMR behave exactly as Bob predicts.
With GRUB installed in MBR the Bootmanager shows only the systems below the 8 GB limit on the HDD.
see Chapter Bootmanager Grand Unified Bootloader (GRUB) V 0.97
2.5 The IBM OS/2 Bootmanager and the boot drive letter
2.6 The OS/2 Master Boot Record - I13 I13X Test and Flag versus the Windows Vista BMR
Vista need it own BMR code to work
Here is a source about the Vista boot process and BMR usage
Windows Vista no longer starts after you install an earlier version of the Windows operating system in a dual-boot configuration
http://support.microsoft.com/kb/919529/EN-US/
Currently I do not know a source for MBR code, that do the required steps to OS/2 and Vista both.
The only a very, very limited workaround is to install OS/2 within the 1024 Cly limit of the HDD.
3 BIOS Requirements
well, you need a
- Computer with USB BIOS Boot support
This is the BIOS configuration screen of the ThinkPad T23
Bild: USB-Boot-BIOS-Configuration-USB-Support-enable
- An USB MSD device with USB boot support
A hight number of USB sticks does not have this.
See USB Sticks test article in the ref of the Wiki
The CF Card is clearly specified.
So the safest way to boot from USBMSD ( to prevent hardware incompatibility problems )is to use CF Cards and a one slot USB CF Card Reader.
3.1 USB BIOS Boot Support Compatibility - Motherboards / Notebooks
I have done some research on this subject and found
a kind of compatibility list on the net
Forum: USB Booting - Topic: USB Boot Compatibility List (http://damnsmalllinux.org/cgi-bin/forums/ikonboard.cgi?act=Print;f=17;t=2925)
To collect compatibility information about Notebook / Motherboard and there BIOS release pleas
enter your test result to the SubWiki's at the next paragraphs.
3.1.1 Collecting Compatibility Information about Motherboard/Notebook BIOS USB Boot Support via SubWiki
Please see SubWiki: USB BIOS Boot support Compatibility List
3.2 USB Mass Storage Devices ( MSD ) Boot Support Compatibility
Son of the USB 2.0 Hi-speed Flash drive roundup - April 13, 2005 By Matt Woodward (http://arstechnica.com/reviews/hardware/flash2005.ars)
==> Conclusio: Not all USB Stick are bootable
3.2.1 Collecting compatibility information about USB Mass Storage Devices ( MSD ) Boot Support via SubWiki
Please see SubWiki: Collecting Information about USB Mass Storage Device Boot Support Compatibility
4 Hardware Requirement
Computer with USB port and USB boot BIOS support USBMSD with USB Boot Support
5 Software Requirements
OS/2 or eCS with the latest USB version of the USB drivers
5.1 Check the buildlevel of the key components of your system
Copy and paste the text from the SubWiki into a new File and save as "bld-dis.cmd" and run from boot drive
bld-dis.cmd > bld-dis.txt
Please see SubWiki: Command File to display the build level of the key components
The check the output of the command in file bld-dis.txt. Does your system use the current drivers?
These are the current buildlevel ( state: 2007-08-10 ) of the key components
os2krnl 14.103 or better IBM1FLPY.ADD 10.85 IBM2FLPY.ADD 10.57 IBM1S506.ADD 10.161 IBMIDECD.FLT 10.134 IBMIDECD.FLT 10.134 DANIS506.ADD 1.8.5 ---> new 2008-05-12 !! previous 1.7.10, 1.8.0, 1.8.1, 1.8.2, 1.8.4 DANIATAP.FLT 0.4.0 ---> new 2007-08-03 !! previous 0.3.19 USBUHCD.SYS 10.162 USBOHCD.SYS 10.162 USBEHCD.SYS 10.162 USBD.SYS 10.162 USBHID.SYS 10.162 USBMSD.ADD 10.162 OS2DASD.DMD 14.104 OS2LVM.DMD 14.105
6 Hard- and Software of the initial test environment
6.1 Hardware test environment
The Chapter " Hardware test Environment" and subchapers has been moved to an SubWiki. The header lines are conserve in place for the table of contents of the Main Wiki !! Please see SubWiki: Chapter 6.1: Hardware Test Environment
6.1.1 IBM Thinkpad T23
6.1.1.1 PCI Test Output of the T23 without Dock II
6.1.1.2 PCI Test Output of the T23 with Dock II
6.1.1.3 PCI Test Output of the T23 with Dock II and DC-150 RAID Controller
6.1.2 USB CF Card Reader One Slot
6.1.3 ThinkPad Ultra Bay 2nd HDD Adapter with CF-to-IDE Adapter
6.1.4 ThinkPad Dock II with eSATA / SATA Controller in PCI Slot of the Dock II
6.1.4.1 DC-150 RAID from Dawicontrol GmbH
6.1.4.1.1 Howto flash a DC-150 Raid Card in a ThinkPad Dock II PCI slot from factory to latest Firmware
6.1.4.2 SATA300 TX4302 from Promise
6.1.4.3 PCI -> Serial ATA RAID controller 2 int. / 2 ext. ports von Vivanco
6.1.5 CF to SATA Adapter
6.1.6 external Boxes with PATA / SATA HDD and USB, Firewire and eSATA Interface
6.1.6.1 KC31-CS from Mapower Electronics
6.1.6.2 Pleiades Super S-Combo from Macpower
6.1.7 eSATA to USB Adapter
The above paragraphs of the Chapter "Hardware Test Environment" has been moved to an SubWiki. The header lines are conserve in place for the table of contents of the Main Wiki !! Please see SubWiki: Chapter 6.1: Hardware Test Environment
6.2 Software Test Environment
OS/2 MCP2 with current Fixpak and driver level DFSEE version 8.11 or better DANIS506 package R 1.7.10 with Diskinfo UBS Resource Manager
6.3 Basic step to create a testsuite
1. create a maintenance partition on my primary HDD with BootAble 4.3
minimum features: only boot to cmd prompt, no wps support
USB Support basic and USBMSD.ADD
System is on Boot Manager Menu
Test the system (drive letter Y:)
2. take a CF Card and create a partition on the medium
How to do it:
data structure of the MSD: Large Floppy or PRM
For the case Large Floppy LVM System see at the step by step instructions in the paragraph
See Wiki Warum erkennt / arbeitet OS/2-eCS nicht mit meinem USB-Speichermedium? (http://os4you.org/wiki-usb-tricks-de.html)
This is the German version of the Wiki.
The English version will follow in the next weeks with the VOICE article
3. There is no drive letter C:, D:, E: on my fixed HDD
The PRM partition has a drive letter of C: in my configuration
The Large Floppy have no assigned drive letter by LVM, no DLAT data structure !
4. Prepare the drive for boot
PRM: Sysinstx C:
Large Floppy: DFSee Version 8.11 or higher
5. xcopy y:*.* c:*.* /H /O /T /S /E /R /V
y: is the drive letter of the mini maintenance system
6. modify the config.sys
7. boot from USB MSD
7.1 Activate USB BIOS support
7.2 change the startup / boot sequence in BIOS
The PRM / Large Floppy is an hard drive for the BIOS
Set the primary hdd to the T23 inactive in boot menu - not in the boot sequence
Bild: USB-Boot-BIOS-Startup-Sequence
7 Booting from USB Mass Storage Devices ( MSD )
7.1 Booting from USB Diskette
modifying the Service diskettes
Config.sys modifications:
1. rem Floppy
2. set CopyFromFloppy=1
3. Add USB Device drivers
4. special sequence for booting
USBDB.sys must be the first USB statement in config.sys
5. Require options USBDB statement
5.1 /I13 in USBDB.SYS
5.2 no parm /REQ for the driver ....
The set CopyFromFloppy=1
Environment variable must be used for special boot logic in the usb boot process
Without the the SET COPYFROMFLOPPY=1
==> MSG: "OS2 cannot access ..." occurs
Dirty hack?
7.1.1 Config.sys for boot from Diskette LVM System
config.sys booting to command prompt ( with only a little cleanup, just from the test bench -:)
Please see SubWiki: Detail Listing config.sys
set bootdrive to usbfloppy with drive letter a: ??????
Who is handling the drive letter a: and B: not DASD / LVM ??
/usage does not work in USB Boot process ???
Drive letters with two legacy floppy drive and 2 USB Floppy
how does this Hardware configuration work ??
Usage of drive letters? only a and b available for floppy devices?
====> Only two floppies per system allowed?
I do see no use of this configuration, but it should work in theory. I have not seen any documented restrictions!
7.2 Booting from USB CD-ROM
Currently not test, no USB CD-ROM aviabale
7.3 Booting from Large Floppy
7.3.1 non LVM Systems
7.3.2 LVM Systems
The USB Mass Storage device can be formatted as Large Floppy or as PRM ( Partitioned Removable Media ).
This is the case with formated as Large Floppy and a system with LVM support
Restriction: It implies FAT16 and Size of MSD less 2 GB.
The basics of the detailed step by step instructions in the following paragraphs are:
1. Wipe the bootsector for a clean, new initialization
2. Write a special boot record to the media
3. Format the media as FAT16 Large Floppy
4. Xcopy of the mini OS/2 system via xcopy /h /o /t /s /e /r /v to the prepared Large Floppy
Now your USB MSD is ready for the test!
Next steps:
1. enable BIOS USB support
2. modify BIOS startup sequence
Now your system is ready for the test, are you ready? :-)
7.3.2.1 Prepare USB MSD as Large Floppy for boot
1. Are you sure you can wipe your USB Mass Storage Device?
2. use DFSee Version 8.11 or higher
3. Look at the initial output of DFSee
Do you have the correct USB MSD to wipe?
4. Mode Fdisk
main menu Mode=Fdisk
sub menu MBR area operations
sub menu Wipe Start of disk to Zero
sel menu select line with your USB MSD
conf box Confirmation request
Are you sure the correct Disk to wipe? Check again !!?
conf box It is strongly advised to REBOOT the system now to allow it to determine
the correct disk geometry and size. This may be required to 'see' the
full capacity of the disk.
OK
5. Exit DFSee, shutdown system, reboot
6. Start DFSee again
7. look at the generated list output to check last operation
Check: 1. L-Geo and size of your USB MSD
2. No boot Record !
3. FreeSpace Pri/Log for your USB MSD
8. main menu File
sub menu Open object to work with
sub menu Disk
sel menu select line with your USB MSD
Be aware: DFSee will have selected Mode=FDISK here
because the disk is empty (wiped).
9. main menu Actions
sub menu Format with FAT filesystem
sel menu Current, OS2LDR.SEK bootable
Be aware: DFSee switches from Mode=FDISK to Mode=FAT
just before the confirmation box is displayed
conf box Confirmation request
Are you sure the correct Disk to format ? Check again !!?
YES
10. generate list output to check last operation
command line: map -M -m
F5 (part -r )
===> --r C: Large Floppy Format! FAT OS2LDR.s LargeFlopD2 xx MB for your USB MSD
Drive letter should be C:, if not, your configuration is not fit to boot from USB Large Floppy !!
see paragraph "Restriction: no Drive Letter C: should be used by the LVM Volumes" !!!
11. exit DFSee
Thanks to Veit (http://kannegieser.net/veit/index_e.htm) ( OS2LDR.sec ), to Jan (http://www.dfsee.com) ( new functions in DSFee 8.11 ) for the excellent jobs and
to Jürgen (http://www.juergen-ulbts.de/index.de.html) for the tip to have a look at MEMDISK!
7.3.2.2 Copy your Mini OS/2 - eCS System from Maintenance Partition to prepared USB MSD
XCOPY x:*.* C:*.* /H /O /T /S /E /R /V
7.3.2.3 Config.sys for boot from Large Floppy LVM System
config.sys booting to command prompt ( with only a little cleanup, just from the test bench -:)
Please see SubWiki: Detail Listing config.sys
7.3.2.4 Restriction: no Drive Letter C: should be used by the LVM Volumes
The following system behaviour / logic is the reason for the restriction:
- The system assigns the drive letter C: to the Large Floppy in the first stage of the boot process.
- C: is the boot drive letter for LVM and the boot process after switching from real to protected mode.
- LVM detects a drive letter conflict, same drive letter on the "fixed" volume and on the "removable" volume
- The removable volume with drive letter C: does not have priority higher than the fixed volume with drive letter C:
- LVM resolves the double assignment of drive letter C:
- LVM assign the next free drive letter to the Large Floppy Device. e.g. drive letter D:
- The boot process switch from real mode to protected mode and continue the boot process with device with boot letter C:
If the fixed disk volume C: contains a valid OS/2 boot system,
the boot process continue with the config.sys from the fixed volume C:
else the boot process failed with message ?????. - If the boot process is successful ( sort of fake success )
the Large Floppy Drive can be accessed at command prompt with the new assigned drive letter.
- First command for the Large Floppy Drive has to be a dir or a chkdsk d: /F command
7.3.2.5 Idea for further development - enhancement
- How to give the drive letter C: preference to a drive letter C: on the fixed disks of the configuration?
This is a most desirable feature. It dismissed the current restriction - no LVM drive letter C: on the fixed disks!
- Can we choose / assign a different / other drive letter to the Large Floppy Device to the default assignment of C:
This is a nice to have feature.
Solution: Filter Driver ?
7.4 Booting from Partitioned Removable Media ( PRM )
7.4.1 non LVM Systems
The problem is to pass the boot drive letter during the boot process from the Partitioned Removable Media.
Boot Manager does not support PRM.
Howto supply a boot drive letter by booting from PRM.
Well, Danidasd.dmd does have an option for the boot drive.
There are some restrictions of danidasd:
1. Danidasd does not support the LVM info on the HDD.
2. The drive letter for the PRM is assigned by the "old" drive letter assignment method:
first assign a drive letter to all the "fixed" partitions (drives) and than to the "removable" partitions (drive)
the drive letter assigned to the PRM drive is depended from the layout of the HDD of the system to boot
The following system / config.sys on CF Card boots from USB card reader on my T23 system
It is on a FAT file system to keep it simple :-)
7.4.1.1 Config.sys for boot from PRM non LVM System to command prompt
Please see SubWiki: Detail Listing config.sys
The version with the DANIDASD boot to the command prompt!!!!
Proof of Concpet !!!!!!!!!
7.4.1.2 Config.sys for boot from PRM non LVM System to WPS
Please see SubWiki: Detail Listing config.sys
7.4.2 LVM Systems
In the thread on comp...bugs Mike reported success. He cloned a system ( a system with volume C without boot manager ) to an USB MSD external disk. This cloned system does boot from USB.
This message has been a great motivation to go on with the project. On the other hand I have not been is able to reproduce the reported boot.
Finally I had success. The system boots from the USB drive at the first stage of the USB drive. When switching from real mode to protected mode during the startup, the system does not only switch the mode, it does switch the boot device too! It switches from the cloned USB system to the source system on the fixes hard drive. Both systems are similar / equal, so the switch was not detected during the test.
The case has been detailed documented in the following SubWiki
Please see SubWiki: Detail Case Boot from PRM LVM System Case Fake Success
This case show the feasibility to boot from USB PRM. To understand the nature of the problem it does help a lot.
Two problems has been identified:
1. Tell the system the boot drive letter. For systems without BMGR, if assumes letter c for the primary boot partition. For systems with BMGR, the BMGR assigns a drive letter to each OS/2 boot system on the boot menu. For LVM systems the DLAT info on every bootable partition is evaluated. For non LMV system the drive letter are assign by chronological order of the partition starting with drive letter c.
2. pass the attribute boot drive with the boot drive letter to the LVM / DASD logic.
Currently the boot drive letter does have the attribute "fixed drive". LVM does not except / handle correctly boot drive letters with the attribute "removable".
raw ideas ( as of 2007-02-20 Rainer ):
1. USBMSD.ADD new pram. Handle_First_Removable_as_Fixed_Device
==> Source Code of USBMSD.ADD needed
alternative: CWUSBMSD.ADD
==> ask Chis about modification / development
2. Special patched version of USBMSD.ADD ?
Robert Lalla does a quick first try to patch. Here are the patch and the test results.
Please see SubWiki: Detail Case Boot from PRM LVM System Case USBMSD Patch
3. OS2DASD.DMD New Parm: Handle_First_Removable_as_Fixed_Device
==> Source Code of OS2DASD.DMD needed
4. Filter driver to change type of first removable device to fixed disk
developer with filter drive skill - daniatap.flt as model ?
==> ask Daniela
How to pass the boot drive letter of an USB MSD boot partition to the system?
Solution: Use ( Alternate ) Boot Managers
1. IBM OS/2 Boot Manager
2. AiR-BOOT
3. VPART
4. XFDISK
5. GRUB
6. LiLo
7. GAG
7.4.2.1 IBM OS/2 Boot Manager
Does not install on PRM by LVM or LVM GUI
Workaround: use DFSee to install primary partition with boot manager on the PRM
Test results:
Boot Manager is loaded by the I13 access from PRM. Now the program logic of the BMGR is processed. Look for an other boot manager partition on the hdds of the system. Found one on the first internal hdd. This one get priority. Look for bootable partitions on the hdd (drive 0 ) to build the list of the boot menu. Look on the second drive ( drive 1 ) for bootable partition. Here the logic fail - It does not look at the PRM, the PRM does not have the BIOS type hdd, if look for a second internal hdd, does not find on and display error Message "Drive 1 not ready, system halted"
Internal boot manager program logic is derived knowledge from comp.os.os2.setup.storage Thread:
- "Drive 2 not ready" error - Warp4 - Dell XPS P200s - Boot Manager (http://groups.google.com/group/comp.os.os2.setup.storage/browse_frm/thread/c889979f273ec13c/42b16149e501cce2?lnk=st&q=os2+boot+manager+drive+not+ready&rnum=2&hl=de#42b16149e501cce2)
This sounds like Boot Manager getting confused by the Bootable
CD support on this machine..
BM asks bios for the drives 80-97, looking for
disk devices, then ready devices..
Apparently the bios answers that the CD is disk and
ready, and then we try to read it and get the not ready error...
Sam Detweiler
IBM OS/2 Device Driver development
Conclusion: Do we have a chance to let the BIOS handle the PRM USB boot device like a HDD?
Question to the experts!!
7.4.2.2 Bootmanager AiR-BOOT
The current version is 1.5. The OS/2 installation program AirBoot2.exe is designed to load the manager into the first tack of your primary hard disk, not to the first track of an PRM.
Workaround: Prepare the CF Card with partition loaded with the mini OS/2 test systems and the an directory with the AiR-BOOT program package. Insert the CF card into an IBM Thin Client 8373-S20, boot the system from CF Card and execute the installation program Airboot2 and configure AiR-BOOT. Do test boot on the Thin Client. Shutdown and move the CF Card to the test computer.
AiRBOOT require sector 2 to 60 of the first track of the boot device ( AiRBOOT documentation: developer.txt ).
AiR-BOOT consists of several parts:
- AiR-BOOT MBR Code (sector 1)
- AiR-BOOT Code (starting at sector 2)
- AiR-BOOT configuration (sector 55-59)
- AiR-BOOT MBR backup (sector 60)
Conclusion: MSD devices with tack GEO less than 63 sectors could not be used. CF Card up to 256 MB are of no use. We have to check the GEO before usage.
Next problem: DFSee does not show P-GEO values for PRM, just value zero. This problem is investigated. ==> "CF and GEO Problem"
Work around: Use the ThinkPad UltraBay 2nd HDD Adapter and an CF-to-IDE Adapter
Test results:
1. Feature: does not install on USB MSD
2. AirBoot2 - Installation process, no waring by disk with less than 63 sectors
3. IBM Thin Client 8364S20 and DANIS506.ADD R 1.7.9 does not work -- pip pip pip pip ...
needs special parms or this version is broken for Thin Client chip set
Workaround: Use IBM1S505.ADD
Status as of 2007-02-22: IBM Thin Client 8364S20 and DANIS506.ADD R 1.7.10 works
without any special prams !!
4. IBM Thin Client does not work with CF 1 GB 120x - Hang up in OS2DASD.DMD
Workaround: Use 1 GB CF Card with lower speed
5. AiR-BOOT works on ThinClient !!
6. Test via USB Card Reader and ThinkPad T23
6.1 First boot with AiR-BOOT: Warning Message BIOS changed, Virus?
6.2 Select System to boot, I/O activity on USB MSB, blink of cursor, no OS/2 blob
6.3 Modifies primary system boot sector of internal HDD!
This program feature / behaviour we do not need for our purpose!
A rescue task for DFSee :-)
6. e-mail to developer
Conclusion: The current version ( 1.5 ) of AiR-BOOT is not usable for the task
7.4.2.3 Bootmanager VPART
The current version is from 2001-11-08 . The OS/2 installation program VPARTOS2.exe is designed to load the manager into the first tack of your primary hard disk, not to the first track of an PRM.
Workaround: Prepare the CF Card with partition loaded with the mini OS/2 test systems and the an directory with the VPART program package. Insert the CF card into an IBM Thin Client 8373-S20, boot the system from CF Card and execute the installation program VPARTOS2 and configure VPART. Do test boot on the Thin Client. Shutdown and move the CF Card to the test computer.
VAPRT require own code in boot record and sector 11 to 45 of the first track of the boot device ( VPRAT documentation: VPART.DEU ).
The install program VPARTOS2 asks very polite: "May i now write 1 sector in sector 1 and 35 in sectors 11 to 45 ?" :-)
Conclusion: MSD devices with tack GEO less than 63 sectors could not be used. CF Card up to 256 MB are of no use. We have to check the GEO before usage.
Next problem: DFSee does not show P-GEO values for PRM, just value zero. This problem is investigated. ==> "CF and GEO Problem"
Work around: Use the ThinkPad UltraBay 2nd HDD Adapter and an CF-to-IDE Adapter
Test results:
to be continued
7.4.2.4 Bootmanager XFDISK
Excerpt from History File (http://www.mecronome.de/xfdisk/files/history_en.txt)
XFDisk I Version 0.9.3 Beta EN
==============================================================================
History
Legend:
------------------------------------------------------------------------------
+ Feature added
- Feature removed
* Bugfix
! Known Bug
# Internal change
XFDisk I Version 0.9.3 Beta EN
------------------------------------------------------------------------------
* reduced Boot Manager size and moved to end of first head (n sectores/head ->
CHS 0/0/n-13 upto 0/0/n). This should solve the problem with HighPoint/Abit
IDE adapter cards
This usage of the last sector of the first tack is in conflict with LVM DLAT.
This has to be changed, so no further activities at present. Rainer 2007-03-22
7.4.2.5 Bootmanager Grand Unified Bootloader (GRUB) V 0.97
7.4.2.5.1 Howto install GRUB V 0.97 on an USB MSD PRM with LiveCD Knoppix 5.1
7.4.2.5.2 Test results menu.lst 1. Version
7.4.2.5.3 Test results menu.lst 2. Version
7.4.2.5.4 Conclusio
The above paragraphs are moved to an SubWiki The header lines are conserve in place for the table of contents of the Main Wiki !!
Please see SubWiki: Bootmanager GRUB V 0.97
7.4.2.6 Bootmanager LILO
Install the LILO Bootmanager on the CF-Card with Knoppix 5.1.1 Live-CD.
This CD contains LILO version 22.6.1-9.
The current version ( 2007-03-28 ) of LILO on the project home page is 22.8 / 2007-02-19.
List of LILO configuration file c:\ETC\LILO.CNF
#map = /media/sda1/ETC/MAP map = /ETC/MAP lba32 boot = /dev/sda default = OS2 prompt timeout = 80 #image = /boot/vmlinuz #label = linux #root = /dev/hda2 #vga = 0x31a other = /dev/sda1 label = OS2 other = /dev/hda label = MBR HDD1
Test results:
to be continued
7.4.2.7 Bootmanager GAG the Graphical Boot Manager
From the documentation FAQ Question 10
I can't boot OS/2 with GAG. What do I have to do?
GAG can boot OS/2 only if it is installed in a primary partition. If your OS/2 is installed in an extended partition and you want to have the benefits of GAG, you must still use the IBM Boot Manager. To do this, just put the IBM BM timer to zero seconds, and configure the icon of OS/2 to boot the partition where the Boot Manager is stored.
Another problem is when OS/2 is installed in a primary partition in a hard disk that is not the first hard disk. In this case, you must say YES to the option 'Exchange drive letters' when you add the OS/2 partition to GAG. In this case you don't need to use the IBM Boot Manager.
Conclusio:
The IBM Boot Manager does not work from USBMSB, so GAG does not do the job!
7.4.2.8 under construction
Well, the results show, booting from Alternate Bootmanager is a possible solution. GRUB demonstrates: The boot from USB MSB via Alternate Bootmanager is possible, AirBoot and VPART does not load from USB, but process the drive letter and LVM stuff correctly under "normal" confidions.
We are working on the case: Boot from USB PRM - LVM System !!
No succes to report - jet :-)
===> *"OS/2 is unable to operate your hard disk or diskette drive"*
Only a some encouraging failures. We learn a lot about the internals!
8 Conclusio
1. The booting from USB Diskette LVM System - tested and works
2. The booting from USB CD-ROM - Currently not test, no USB CD-ROM aviabale
3. The booting from Large Floppy non LVM System - not tested, no software configuration aviabale
( should work no difference to LVM system )
4. The booting from Large Floppy LVM System - tested and works
5. The booting from USB PRM non LVM System - tested and works
( Prove of Concept based on DANIDASD.DMD for booting from USB MSD PRM ) !!!
6. The booting from USB PRM LVM System
under development / construction
9 Application of Booting OS/2 - eCs from USB Mass Storage Devices ( MSD )
9.1 Emergence / Recovery / Maintenance System with DFSee on the USB Media
Base on the currently working case: USB MSD Large Floppy Format and an LVM System Jan has published a condensed instruction set and download at his side (http://www.dfsee.com/dfsee/howto.htm#usbootlf).
Be aware of the prerequisites:
- OS/2 eCS installation with no drive letter C: in use
- Computer with compatible hardware and BIOS
- Compatible USB Mass Storage Devices ( MSD )
Some Words of Wisdom
If you buy new hardware for this application,buy a
- Compatible USB one slot CF Card Reader and CF Memory Cards
The probability to buy a working compatible USB Stick out of the shelf is currently about 50%.
9.2 The Asus EeePC - HowTo Boot an OS/2 - eCS System
9.2.1 Disk layout of the Internal Solid Disk - Xandros Linux Preload
9.2.2 Xandros Linux Preload GRUB File menu.lst
Please see SubWiki: EeePC Xandros Linux Preload GRUB File menu.lst
9.2.3 The Hardware of the EeePC - as PCI Test sees the System
Please see SubWiki: The Hardware of the EeePC - defined by PCI Test Output
Das Feintuning kann beginnen. - für welche Komponeten haben wir Treiber, - für welche Komponenten können existierende Treiber angepasst werden - wo ist Treiber Neuentwicklung erforderlich?
The consol output of the program HCIMONIT - part of the "Universal Serial Bus Base Stack" package:
You have 4 PCI USB UHCI host controller(s) You have 1 PCI USB EHCI host controller(s)
This is conform with the PCI test results.
9.2.4 Boot without Modification of Preload - the installed Xandros Linux on the Internal Solid Disk
Currently ED Durrant is implementing a system base on the solution from
Chapter 7.4 Booting from Partitioned Removable Media ( PRM ) / 7.4.1 non LVM Systems.
The Mapping definition by the parameter of the DANIDASD.DMD statement is the key to the solution.
BASEDEV=DANIDASD.DMD /BD:D /MT:Aa
Without definition of addional partition types by the /AT parameter, DANIADASD sees / accepts partioniton of following types. The seen (acceptable) partitioned can be mapped to drive letters by the /MT parameter. You can find detail information at the DANIDASD.Doc file of the DANIDASD package found on Hobbes.
DASD manager partition types supported
extended regular
DaniDASD: 05, 0F, 8F 01, 04, 06, 07, 0B, 0C, 0E, [+ other]
Of the 4 partitions (by type ) 83 83 0C ef of the preload, only one partition -the 0C - is accepted and can be mapped to the driver letter C:
So the first primary partition on the SD, the OS/2 Boot partition, is mapped to the drive letter D:
A picture is worth a thousand words
From the Shop of Ed Durrnat :-)
If you do not want to access the primary HDD, just do not map a drive letter to the seen / accepted partition of the HDD
( Has to be tested by ED - Rainer 2008-01-27 )
BASEDEV=DANIDASD.DMD /BD:C /MT:Ba
or
BASEDEV=DANIDASD.DMD /BD:C
Tested by Ed - does not work - "OS/2 cannot ...."
Test variant documented and not deleted - to learn from the failed test :-) Rainer 2008-02-03
9.2.5 Howto Install a eCS System on an SD Card at the Internal Reader of the ASUS EeePC without deleting / changing the Preinstalled System
The last, stable version HowTo s V1.0 (PDF files) can be found on Hobbes:
Files names are: EeePC-HowTo-install-eCS-to-SD-deu_v1.zip German Version
EeePC-HowTo-install-eCS-to-SD-eng_v1.zip English Version
http://hobbes.nmsu.edu/cgi-bin/h-search?key=eeepc+&pushbutton=Search
Many thanks to Ed for authoring and to Gabriele Durrant for the German translation!
The current, developing version of the HowTo can be found at the above Wikis:
English: Howto Install a eCS System on an SD Card at the Internal Reader of the ASUS EeePC
without deleting / changing the Preinstalled System Deutsch: Howto Installation eines eCs Systems auf einer SD Karte im SD Schacht
des ASUS EeePc ohne das vorinstallierte System zu modifizieren?
9.2.6 Howto Install a eCS System on the ASUS EeePC internal HDD with Deletion of the Preinstalled System - Wiki
Howto Install a eCS System on the ASUS EeePC internal HDD with Deletion of the Preinstalled System - Wiki
9.2.7 Howto Install Video Support on the ASUS EeePC running OS/2 - eCS
9.2.7.1 Video support by the SNAP drivers
9.2.7.2 Video support by the Panorama Drivers
Please see SubWiki: Howto Install Video Support on the ASUS EeePC running OS/2 - eCS - Wiki
9.2.8 Howto Install Audio Support on the ASUS EeePC running OS/2 - eCS
9.2.9 Howto Install LAN and WLAN Support on the ASUS EeePC running OS/2 - eCS
9.2.10 EeePC running with OS/2 eCS - Video Presentations - First Draft
Here are the links to the Video on YouTube - Production, Director, Camera and Speaker - Sigurd Fastenrath (http://www.sigurd-fastenrath.de)
Part I and II show eComstation 2.0 RC 4 with OS/2 Warp 4 skin and
Part III show eCS RC 4 with the default skin
ASUS EEE PC and OS/2 Warp - eComstation Part I (http://www.youtube.com/watch?v=ge6zgGhI8tA)
ASUS EEE PC and OS/2 Warp - eComstation Part II (http://www.youtube.com/watch?v=WD_lgUbEXNE)
ASUS EEE PC and OS/2 Warp - eComstation Part III (http://www.youtube.com/watch?v=8sGBxhPZReE)
9.2.11 EeePC Model PC 4G 701 Internal SD Card Controller and SD Cards Compatibility Tests
Lothar Joeger has doenn some Compatibility Test with diffent SD Cards Status: 2008-05
Here is the copy of his e-mail with the test results
- translation to english and edit outstanding :-) Rainer
Hier erstmal die Liste der SD-Karten die ich mit dem eeePC erfolgreich getestet habe.
- Transcend 8GB SDHC Flash (Bootet Windows XP und Mac OS X)
- Kingston 1GB SD Card (Datentransfer ok)
- Kingston 2GB SD Card (Datentransfer ok)
- Kingston 4GB SD Card (Bootet Windows XP / OS X nicht getestet)
- SanDisk 512MB SD Card (Datentransfer ok)
- SanDisk 1GB Extreme III (Datentransfer ok)
- SanDisk 2GB Extreme III (Datentransfer ok)
Bei folgenden Karten habe ich Problem gehabt:
- Kingston MMC 1G Mobil RS/MMC (mit SD-Adapter) - Wird vom Bios nicht erkannt,
Windows XP erkennt sie, Mac OS X nicht.
- takeMS SD Karte Hyper Speed 4GB - Wird vom Bios erkannt, Windows XP auch, Mac OS X erkennt sie,
verliert aber alle 5-10 Minuten die Verbindung (Connect/Reconnect)
- PNY SD-Card 1GB - wird nicht erkannt.
- Sharkoon 1GB SD - funktioniert, ist aber extrem langsam.
ED Durrant reports tests okay for the following cards( 2008-06-18 ):
Toshiba 2GB SD (class 4)
Toshiba 4GB SDHC (Class 6)
Fujifilm 1GB SD
Elite Pro 8GB SD
Photofast dual channel 150X SD
10 Problem reports / Found Defects in the Research
10.1 CF and GEO Problem
The displayed GEO values by the IBM1S506.add, the DANIS506.add and GEO values in DFSee output ( here plus USBMSD.add ) differs.
Some values looks buggy!!
Please see SubWiki: Detailed Problem Description
10.2 Large Floppy and SYSINSTX SYS01475
Obviously SYSINSTX does not do the job for the Large Floppy Format correctly!!
10.2.1 Problem Descriptions
10.2.2 Work around: Howto write a correct Boot Record for OS/2 to a Large Floppy
The subparagraphs "Problem Description" and "Work around: Howto write a correct Boot Record for OS/2 to a Large Floppy" has been moved to SubWiki
The Header Lines with empty contents remain in the main Wiki to be shown in the main table of contents!!
Please see SubWiki: Detailed Problem Description and Work Around
10.3 IBM Boot Manager and Wrong Drive Letter - Unable to boot a system from logical partition
The boot manager assigns a wrong drive letter to a bootable partition. Booting this partition via boot menu fails with error "OS/2 is unable to operate your hard disk or diskette drive"
Please see SubWiki: Detailed Problem Description
10.4 MBR with GRUB boot code stage1
10.4.1 CF Card with GRUB MBR in CF-to-IDE Adapter --> kernel exception condition at boot
10.4.2 CF Card in USB Card Reader --> LVM detects no valid file system in partition
10.4.3 Analyze, Result and Work Around
The above paragraphs are moved to an SubWiki
The header lines are conserve in place for the table of contents of the Main Wiki !!
Please see SubWiki: Bootmanager Boot Code Stage 1 Problems
10.5 Bootmanager AirBoot V1.5
10.6 Bootmanager VPART
10.7 Problem Dummy disk with 0 Cylinders resulting a size of 0 MB
10.7.1 Problem Descriptions
DFSee OS/2 9.b3 : executing: map -M -m Command timestamp : Thursday 2007-07-19 08:37:34 Disk DFSee Disk Image filename or id type nr (Unix) device, and optional partitionable media description ==== ===== ==== =========================================================== 1 Phys 1 /dev/hda Physical disk 1 (IDE/SCSI/USB or PCCARD) 2 Phys 2 /dev/hdb Physical disk 2 (IDE/SCSI/USB or PCCARD) 3 Phys 3 /dev/hdc Physical disk 3 (IDE/SCSI/USB or PCCARD) 4 Phys 4 /dev/hdd Physical disk 4 (IDE/SCSI/USB or PCCARD) Number of disks : 4 P-Geo Disk 1 Cyl : 16383 H: 16 S:63 Bps:512 Size : 0x0FFFFFFF = 131071 MiB Geometry D1 from : LVM info (DLAT) sector at 0x3e L-Geo Disk 1 Cyl : 20673 H:240 S:63 Bps:512 Size : 0x12A18710 = 152624 MiB BIOS Int13 limit : 1024, I13X support needed beyond : 7560.0 MiB MBR crc c51e1623 : 0x7ea9d168 = IBM OS/2 LVM, 14.105 May 2006, I13X L-Geo Disk 2 Cyl : 0 H: 64 S:32 Bps:512 Size : 0x00000000 = 0.0 KiB DUMMY, disk 2 seems reserved with no media present (USB/PCCARD etc) L-Geo Disk 3 Cyl : 512 H: 12 S:32 Bps:512 Size : 0x00030000 = 96.0 MiB DUMMY, disk 3 seems reserved with no media present (USB/PCCARD etc) L-Geo Disk 4 Cyl : 512 H: 12 S:32 Bps:512 Size : 0x00030000 = 96.0 MiB DUMMY, disk 4 seems reserved with no media present (USB/PCCARD etc)
Status: Problem is recognized and waiting for analysing as of 2007-07-19 Rainer
10.8 ThinkPad T41 and the Test Environment
10.8.1 Freeze of the System at POST with CF-to-IDE Adapter in 2. HDD Ultra Bay Adapter
10.8.2 SATA Devices connected to the SATA controller in the DOCK II PCI extension Slot does not show up in the BIOS StartUp Selection Menu
An external LCD screen has been connected to the DOCK II VGA Port. The screen shots shows output for the external LCD screen.
10.8.2.1 Good case: T23 SATA HDD is part of the boot startup menu and can be selected
10.8.2.2 Bad case: T41 SATA HDD is not part of the boot startup menu and can not be selected
11 References / Literaturhinweise / Linksammlung
USB Removables Care and Feeding FAQs by Lon Hooker, © June 2006