Mr. Know-It-All has the answers to even the really tough questions.
I've got a BackAgain 2000 problem. When I try to restore a single file to
the root of my boot drive, BA2K complains that it can not write the file.
Full restores work fine. I've got v4.10. What's going on?
The programmers goofed. Let's say your boot drive is C: and you try to
restore CONFIG.SYS using the default options. BA2K tries to write to
which OS/2 will not allow. The workaround is to use
Options -> Restore Path -> Restore to specified location
and specify C:\ as the location.
Hi, me again. I cannot get BAIICR to run from my BOOTOS2 maintenance
partition. The partition boots fine, but when I try to start BAIICR, the
disk LED flashes a couple of times and then the command line prompt returns.
Popuplog.os2 reports a trap at BAIIOM3.DLL 0001:00000071. I tried to run
BAIICR from my emergency restore diskettes and they have the same problem.
The programmers goofed again. The version of BAIICR delivered by CDS (now
Intradyn) requires an installed TCP/IP stack to run.
To get BAIICR to run, you will need to install a minimal TCP/IP stack on your
maintenance partition. This is not difficult. If you really need to, you
can install the minimal TCP/IP stack to your emergency boot diskettes, but
getting the right files on the right diskette will take a bit of work. If
possible, Mr. KIA recommends that you build a bootable CD. Otherwise,
contact Mr. KIA for assistance.
To add the required TCP/IP stack to your maintenance partition, create a
directory to hold the TCP/IP files. Mr. KIA suggests
Copy the following files to this directory from your boot partition:
These files are in subdirectories of \IBMCOM and \MPTN on your boot drive.
Edit protocol.ini to read:
DRIVERNAME = PROTMAN$
tcpip_nif = tcpip.nif
nulndis = nulndis.nif
DriverName = TCPIP$
Bindings = nulndis
DriverName = NULLNDS$
Edit CONFIG.SYS and add references to \OS2\TCPIP to PATH, DPATH and LIBPATH.
Add the following to the end of CONFIG.SYS:
rem *** Start of Thinlaps for BAIICR ***
run = \os2\tcpip\lanmsgex.exe
device = \os2\\tcpip\lanmsgdd.os2
device = \os2\tcpip\protman.os2 /I:\os2\tcpip
device = \os2\tcpip\sockets.sys
device = \os2\tcpip\afinet.sys
run = \os2\tcpip\cntrl.exe
device = \os2\tcpip\nullndis.os2
rem *** End of ThinLAPS for BAIICR ***
Reboot and try to run BAIICR now. It should start up and run correctly.
If this seems like too much work, you might want to consider using
Hayo Baan's bootAble
to rebuild your maintainance partition with TCP/IP support.
Curious or in doubt, you can ask
OS/2 is his specialty and sharing solutions is his passion
Mr. Know-It-All lives in Southern California.
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2004 the Southern California OS/2 User Group. ALL RIGHTS
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.