Re: Boot from USB PRM (Partitioned Removable Media ) failed after loading OS2LVM.DMD error: "OS/2 is unable to operate

Better get your blinders on horse, grin. Very long post!

Rainer Stroebel wrote:
Rainer Stroebel schrieb:


Hello Mike,




I will try to reproduce you configuration by doing a test with a "real fixed HDD" at the USB port of my T23.

I have just done the test with a "real fixed HDD" at the USB port

Mod the bios start up list and boot from the USB Mass Storage


--> no success --> "OS/2 is unable to operate...........


What magic do you do ??????????? :-)

kind regards from Germany

Rainer



With a very great deal of thanks to Rodney Almodavar from IBM Austin for
his and IBM's support of my quest here, I suggest you compare your Thinkpad
Utility Diskette Set made from the MCP2 latest fixpack operations with
what IBM suggested below. And you will need the that latest fixpack and
kernel as XRC_05 so noted to me as well. You'll also need at least certain
later of the device driver changes as well. And note, this is for an
IBM Thinkpad with ONLY the OS/2 operating system on the hard disk in it.
No complicated stuff, OK? Grin!

Here is the CONFIG.SYS file on the Disk #01 of the utility floppy disk set
which boots the R40, R51, T42, and T43P units I've tested and enables all
the USB operations we need. Pay particular attention to the lines in the
CONFIG.SYS file for BASEDEV=USBD.SYS /I13 and SET COPYFROMFLOPPY=1. Yes,
that copy from floppy line is there for a reason!


******* Begin CONFIG.SYS file below *******

buffers=32
iopl=yes
memman=swap,delayswap
protshell=sysinst1.exe
set os2_shell=sysinst2.exe
diskcache=D2,LW
protectonly=yes
libpath=.;\;\os2\dll;\os2\install;
ifs=jfs.ifs
ifs=hpfs.ifs /c:64
pauseonerror=no
codepage=850
devinfo=kbd,us,keyboard.dcp
devinfo=scr,ega,vtbl850.dcp
device=\dos.sys
device=\mouse.sys
set path=\;\os2;\os2\system;\os2\install
set dpath=\;\os2;\os2\system;\os2\install
set keys=on
basedev=ibmkbd.sys

basedev=ibm1s506.add /W
basedev=os2dasd.dmd
basedev=os2lvm.dmd
device=\testcfg.sys

basedev=ibmatapi.flt /A:1 /U:0 /TYPES:CLZ

BASEDEV=USBD.SYS /I13
SET COPYFROMFLOPPY=1


BASEDEV=USBUHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBUHCD.SYS
BASEDEV=USBEHCD.SYS
BASEDEV=USBHID.SYS
BASEDEV=USBMSD.ADD /FLOPPIES:1 /REMOVABLES:2

EARLYMEMINIT=TRUE
basedev=xdfloppy.flt

set os2_shell=cdinst.exe
set saveconnect=1
set cdrominst=1
ifs=cdfs.ifs /q
device=\os2cdrom.dmd
device=\refpart.sys
set os2_shell=cmd.exe

******* End CONFIG.SYS file above *******


Now here is the disk directory for the Disk #01 for the Utility Boot disk
set which will boot these same IBM Thinkpads and operate the entire USB
operations as described. It's been alpha sorted for clarity. Please note
the dates of certain of the files below. Note the file dates for:

IBM1S506 ADD 70490 1-03-05 11:43a
IBMATAPI FLT 39568 3-12-04 11:28a
IBMIDECD FLT 39568 3-12-04 11:28a
OS2DASD DMD 40709 7-19-05 12:34p
OS2LVM DMD 32519 10-12-04 1:13p
SCREEN01 SYS 12212 11-18-04 5:39p
SCREEN02 SYS 12174 11-18-04 5:39p
SNOOP LST 603 10-03-05 7:45p
USBD SYS 22988 9-10-04 3:48p
USBEHCD SYS 42112 9-10-04 3:49p
USBHID SYS 13292 9-10-04 3:49p
USBMSD ADD 40612 9-10-04 3:49p
USBUHCD SYS 27814 9-10-04 3:48p

******* Begin DISK #01 DIRECTORY below *******

AHA6360 SNP 27383 5-21-02 4:21p
AIC7770 ADD 42574 5-21-02 3:49p
AIC7770 SNP 17456 4-15-02 3:07p
AIC7870 ADD 154140 4-24-02 2:30p
AIC7870 SNP 9104 5-21-02 4:22p
AIC78U2 ADD 156412 1-18-02 12:45p
CLOCK01 SYS 4552 4-15-02 3:16p
CLOCK02 SYS 4318 4-15-02 3:16p
CONFIG SYS 970 10-04-05 10:08p
CONFIG X 627 4-17-01 10:08a
DELIVERY SYS 3806 10-25-01 4:40p
DPT20XX ADD 24700 5-21-02 3:50p
DPT20XX SNP 6700 4-15-02 3:03p
IBM1FLPY ADD 35418 10-08-02 12:02p
IBM1FLPY SNP 2393 4-15-02 3:04p
IBM1S506 ADD 70490 1-03-05 11:43a
IBM1S506 SNP 9160 4-15-02 3:03p
IBM2FLPY ADD 14424 5-21-02 3:45p
IBM2SCSI ADD 33115 5-21-02 3:46p
IBMATAPI FLT 39568 3-12-04 11:28a
IBMIDECD FLT 39568 3-12-04 11:28a
IBMINT13 I13 11522 5-21-02 3:46p
IBMKBD SNP 1404 4-15-02 2:59p
IBMKBD SYS 8714 5-21-02 4:03p
IPSRAID ADD 22310 4-24-02 6:47p
IPSRAID SNP 2624 4-15-02 3:09p
ISAPNP SNP 21374 4-15-02 3:01p
KBDBASE SYS 24989 5-21-02 4:05p
MOUSE SNP 3744 4-15-02 3:00p
NETDET1 SNP 11270 4-15-02 3:05p
NETDET2 SNP 14410 4-15-02 3:05p
OS2DASD DMD 40709 7-19-05 12:34p
OS2LOGO 60979 4-19-00 4:17p
OS2LVM DMD 32519 10-12-04 1:13p
PARALLEL SNP 3032 10-25-01 5:50p
PCIBUS SNP 2496 4-15-02 3:00p
PCMCIA SNP 3912 4-15-02 3:09p
PNP SYS 2152 4-15-02 3:01p
QL10OS2 ADD 37420 9-21-01 3:46p
QL10OS2 SNP 6516 4-15-02 3:08p
RESERVE SYS 5704 5-21-02 3:37p
RESOURCE SYS 55402 5-21-02 3:36p
RESRV SNP 5257 4-15-02 3:05p
SCREEN01 SYS 12212 11-18-04 5:39p
SCREEN02 SYS 12174 11-18-04 5:39p
SERIAL SNP 3280 4-15-02 2:59p
SNOOP LST 603 10-03-05 7:45p
SYM8XX ADD 63580 1-18-02 12:59p
SYM_HI ADD 67140 1-18-02 12:59p
USBD SYS 22988 9-10-04 3:48p
USBEHCD SYS 42112 9-10-04 3:49p
USBHID SYS 13292 9-10-04 3:49p
USBMSD ADD 40612 9-10-04 3:49p
USBUHCD SYS 27814 9-10-04 3:48p
XDFLOPPY FLT 15060 4-15-02 2:27p

******* End DISK #01 DIRECTORY above *******


Next, here is what is in the SNOOP.LST above for checking;

resrv.snp
netdet1.snp
ibmkbd.snp
ibm1flpy.snp
ibm1s506.snp
; SCSI Snoopers
aha6360.snp
;aha154x.snp
;aha174x.snp
aic7870.snp
ql10os2.snp
;ql40os2.snp
;ql510.snp
;ipsraid.snp
;btscsi.snp
;fd16-700.snp
;fd8xx.snp
;fd7000ex.snp
;flashpt.snp
;dac960.snp
; Misc. Snoopers
pcmcia.snp
;ir.snp
netdet2.snp
; CDROM Snoopers
;mitfx001.snp
;sbcd2.snp
;sony31a.snp
; Audio Snoopers
;sndgalax.snp
;auddrive.snp
;jazz16.snp
;sndblast.snp
;pas16.snp
;bsaudio.snp
; Misc. Snoopers
parallel.snp
mouse.snp
serial.snp
; Note: Place additional snoopers above this line
pcibus.snp


Next you need to check your Disk #02 to compare it to the below. It's been
alpha sorted for clarity. Please note the dates of certain of the files
below. Note the file date for:

CDFS IFS 45159 1-10-05 1:42p
CMD EXE 100620 1-01-05 6:30a
HPFS IFS 141378 1-10-05 1:41p
OS2CDROM DMD 50098 5-26-05 8:57a

******* Begin DISK #02 DIRECTORY below *******

ANSICALL DLL 512 3-08-02 7:16p
BKSCALLS DLL 512 3-08-02 7:16p
BMSCALLS DLL 512 3-08-02 7:16p
BVHINIT DLL 11158 9-10-01 4:17p
BVSCALLS DLL 512 3-08-02 7:16p
CDBOOT EXE 8903 10-25-01 5:16p
CDFS IFS 45159 1-10-05 1:42p
CMD EXE 100620 1-01-05 6:30a
CONFIG ADD 122 9-05-00 11:56a
COUNTRY SYS 50947 9-24-01 3:46p
DEL LST 51081 5-30-01 8:45a
DIR2 DAT 1824 10-04-05 5:35p
DOS SYS 1142 3-11-02 10:05a
DOSCALL1 DLL 137601 12-29-04 11:15a
HARDERR EXE 14889 12-29-04 11:15a
HPFS IFS 141378 1-10-05 1:41p
INST32 DLL 6688 10-26-01 10:09a
JFS IFS 190349 10-12-04 1:16p
KBDCALLS DLL 1024 3-08-02 7:16p
KEYBOARD DCP 25507 10-03-01 6:35a
MOUCALLS DLL 1024 3-08-02 7:16p
MOUSE SYS 30819 5-21-02 4:02p
MSG DLL 512 3-08-02 7:16p
NAMPIPES DLL 1024 3-08-02 7:16p
NLS DLL 512 3-08-02 7:16p
NPXEMLTR DLL 21812 3-08-02 5:50p
OS2CDROM DMD 50098 5-26-05 8:57a
OS2CHAR DLL 512 3-08-02 7:16p
POINTDD SYS 3846 5-21-02 4:10p
QUECALLS DLL 1024 3-08-02 7:16p
REFPART SYS 6679 9-05-00 11:59a
RMINFO DLL 22847 4-03-02 2:31p
RMVIEW EXE 32885 5-21-02 3:36p
SESMGR DLL 1536 3-08-02 7:16p
SYSINST1 EXE 4240 10-26-01 10:09a
SYSLEVEL OS2 165 3-25-02 3:19p
TESTCFG SYS 9808 5-21-02 4:11p
VCU MSG 1760 10-16-01 1:26p
VIOCALLS DLL 2048 3-08-02 7:16p
VTBL850 DCP 10495 10-03-01 6:36a

******* End DISK #02 DIRECTORY above *******


Lastly, you'll need to check your utility diskette #03. It's been alpha
sorted for clarity. Please note the dates of certain of the files
below. Note the file date for:

LVM DLL 167366 10-12-04 1:12p
LVM EXE 93069 10-12-04 1:37p
UHPFS DLL 105008 1-10-05 1:42p

******* Begin DISK #03 DIRECTORY below *******

CHKDSK COM 70720 3-11-02 9:58a
CHKDSK32 DLL 147268 1-01-05 6:43a
FORMAT COM 72064 1-01-05 6:31a
JFS MSG 12619 10-16-01 1:28p
LVM DLL 167366 10-12-04 1:12p
LVM EXE 93069 10-12-04 1:37p
LVM MSG 18184 10-16-01 1:26p
LVMH MSG 21126 10-16-01 1:26p
NLS DLL 512 3-08-02 7:16p
ODPANS DLL 21968 10-26-01 12:29p
ODPRTDRV EXE 12023 3-11-02 10:51a
OSDELETE EXE 69124 3-25-02 3:23p
OSO001 MSG 175354 3-08-02 3:56p
SHPIINST DLL 37328 10-16-01 6:52p
TEDIT EXE 9390 9-24-01 3:57p
TEDIT HLP 14596 9-05-00 12:13p
UCONV DLL 23331 9-04-02 5:30p
UHPFS DLL 105008 1-10-05 1:42p
UJFS DLL 286488 10-12-04 1:30p
VIOCALLS DLL 2048 3-08-02 7:16p

******* End DISK #03 DIRECTORY above *******


To use Jan's DFSEE 7.1.5 or later for the clone and back clone operation,
you obviously prepare a floppy diskette with his OS/2 toolset on it. But
to get it to run in a jam in on floppy boot, you will also have to add
certain of the IBM DLL's to that floppy. That's covered in documentation
for his product.

What isn't quite as clear is that after you boot the Thinkpad to a command
line from the diskettes, you will then need to stuff in the utiity diskette
and do a manual command line 'LVM /PRMrediscover' command. If you have
the drivers and all correct in the above, that is when you'll get to see
the USB 2.0 Hard Disk drive show up in Jan's toolset. And a way you go!

Lastly. You simply CLONE your whole Thinkpad to the external USB hard
disk unit. Then, if you wish, you go into the BIOS on the Thinkpad, and
make sure you have enabled USB support for it. Then you move the USB boot
device up to the top position in the boot device list! Poof! At least
here the entire Thinkpad operation will actually boot from the USB 2.0
external hard disk just like it did with the native disk inside.

Provided you have set up the required USB device drivers and so on or later
that are shown in the above explanations for the unit, of course...


Hope this helps!


--


--> Sleep well; OS2's still awake! ;)

Mike Luther
.

Relevant Pages

  • Re: Can we link a windows driver (.sys) with our own code ?...
    ... All dispatch routines in your .sys are called by the I/O manager. ... >Ya sure as long as 'dll' provides all referenced kernel interfaces invoked by 'sys' you are all set. ... Let me know when you have tha kernel emulator complete. ... >Use a filter that uses IOCTLs to directly call entry points in the target driver. ...
    (microsoft.public.development.device.drivers)
  • Re: does it need a new power supply?
    ... it will have a .sys or .dll or .exe extension. ... there are a lot of reasons that could cause that error you're getting. ...
    (alt.sys.pc-clone.dell)
  • Re: Assembly.GetExecutingAssembly
    ... Is it possible to save that to disk as a dll or exe, ... Mattias Sjögren mattias @ mvps.org ...
    (microsoft.public.dotnet.framework)
  • Re: Linking Libraries to Drivers.
    ... Move the C source code from the DLL to SYS, ... The driver has two files - a .sys(written on ... > I have the source code for xyz.lib and so can make changes to it. ...
    (microsoft.public.development.device.drivers)
  • Re: Can we link a windows driver (.sys) with our own code ?...
    ... I dont see which of your .sys functions are called by your .dll. ... dispatch routines in your .sys are called by the I/O manager. ... I don't see any hurdle while linking this way. ...
    (microsoft.public.development.device.drivers)