ThinkPad X21 Recovery Issues

[VintageUniverse]

Since I am unable to source or acquire the original Windows 98SE/2000 Professional Product Recovery CDs for the X21 or the X20/X21/X22/X23 series which should work just fine as well.

I managed to test the T23 Recovery CDs as suggested by a fellow forum member since the machines are similar. However I ran into this issue with some photos linked below:
https://www.dropbox.com/sh/05gbsnuoq600 ... msUka?dl=0

I have not replaced the CMOS battery yet and the BIOS seems to have USB options enabled. The laptop can read from the external USB IOMEGA Predator CD-RW CDRW9602EXT-B Drive as you can see from the photos. However it cannot detect the CD-ROM Drive and says no Recovery CD due to missing drivers? Therefore, I have a couple of questions and want guidance:

Should I try my Pioneer DVR-XD10 (USB) which is newer than the X21 by a long shot and might not have drivers?

Maybe even attempt to use the Sony PCGA-CD5 (PCMCIA Card) Drive from the Sony Vaio PCG-505 Series?

Or do I have to possibly acquire the IBM USB 2.0 Portable CD-ROM/CD-RW/DVD-ROM Drive or the UltraBase possibly to proceed further with the Recovery procedure?

Is there any workarounds?

I found this (basically stating that you have to have the UltraBase:
viewtopic.php?t=7898

Please advise. Thanks

[RealBlackStuff]

Try some other W98/W2K from here: viewtopic.php?f=11&t=128170

[VintageUniverse]

Thanks for the suggestion, but the same issue arises.

[dr_st]

It looks like the installation images lack USB CD-ROM drivers. You either need to modify the image and add those, or get an ATAPI drive, which means - Ultrabase.

[VintageUniverse]

I would like to perform the recovery as it is more convenient than installing all of the drivers and software from other media. I have tried a generic Windows 98SE bootdisk and it does not detect my USB Iomega Predator CD-ROM with the Recovery Disk or the Windows 98SE CD. I have to figure out a way to make the DOS drivers for the USB Iomega Predator CD-ROM to load from floppy to make the Recovery CD work. I did find a generic USB driver by Panasonic to load in DOS to make the USB Iomega Predator CD-ROM, however I am having difficulty configuring the Recovery Floppy and Bootdisk to detect the USB Iomega Predator CD-ROM in lines for the config.sys and autoexec.bat. The ultimate goal is to perform the Recovery procedure without the UltraBase, in my opinion not a useful item. I know this is possible and it has been done before.

[dr_st]

I did find a generic USB driver by Panasonic to load in DOS to make the USB Iomega Predator CD-ROM, however I am having difficulty configuring the Recovery Floppy and Bootdisk to detect the USB Iomega Predator CD-ROM in lines for the config.sys and autoexec.bat.

Assuming that it is the proper driver, once it is loaded via Config.sys, MSCDEX should be loaded normally in Autoexec.bat and should see the drive. The USB driver provides a compatibility layer, and after that it should be transparent for DOS.

Let me know if you need specific help. Generally you can look at the Config/Autoexec samples in the existing boot floppy / CD. There should be several CD drivers it tries to load. You can just add your USB driver there.

[VintageUniverse]

I managed to find the Recovery Boot Floppy for the T23 Recovery CD. I have uploaded it for reference in the link below:
https://www.dropbox.com/sh/ypqsca5kqq8z ... WG0Ja?dl=0


Meanwhile, I have found various USB-CDROM DOS drivers linked below:
http://www.glennmcc.org/download/usb-dos/dosusb1/

https://hddguru.com/software/2006.02.09 ... OS-Driver/

https://www.classic-computers.org.nz/bl ... -Win98.htm

http://www.pcxt-micro.com/dos-usb.html

http://optimizr.dyndns.org/dos/usbdrv.html

https://www.techspot.com/community/topi ... dos.25953/

https://www.bootdisk.com/popfiles.htm

https://www.bootdisk.com/usb.htm


However, I cannot seem to understand how to apply the instructions to the Recovery Boot Floppy for the T23 Recovery CD to make my external USB IOMEGA Predator CD-RW CDRW9602EXT-B Drive be detected in DOS to start the Product Recovery procedure. The files are both different for the most part and my familiarity with DOS is limited. Thanks.

[dr_st]

However, I cannot seem to understand how to apply the instructions to the Recovery Boot Floppy for the T23 Recovery CD to make my external USB IOMEGA Predator CD-RW CDRW9602EXT-B Drive be detected in DOS to start the Product Recovery procedure. The files are both different for the most part and my familiarity with DOS is limited. Thanks.

Maybe "Method 2" in https://www.bootdisk.com/usb.htm will help you. You need to get install the appropriate USBASPI/USBCD driver files onto your floppy, then load them in CONFIG.SYS.

[VintageUniverse]

This is the original CONFIG.SYS for the Recovery Floppy:

REM MSCDEX loaded in Autoexec.bat.

[COMMON]
DEVICE=A:\HIMEM.SYS /TESTMEM:OFF
DOS=HIGH,UMB
SHELL=A:\COMMAND.COM /P /E:512
BUFFERS=20
FILES=40
REM DEVICE=A:\EMM386.EXE ON
DEVICEHIGH=A:\IBMTPCD.SYS /D:IBMCD001
REM DEVICEHIGH=A:\DISPLAY.SYS CON=(EGA,,1)
DEVICEHIGH=A:\RAMDRIVE.SYS /E 4096 512 200

Will this work?:

REM MSCDEX loaded in Autoexec.bat.

[COMMON]
DEVICE=A:\HIMEM.SYS /TESTMEM:OFF
DOS=HIGH,UMB
SHELL=A:\COMMAND.COM /P /E:512
BUFFERS=20
FILES=40
REM DEVICE=A:\EMM386.EXE ON
DEVICEHIGH=A:\USBASPI.sys /w /v
DEVICEHIGH=A:\USBCD.SYS /D:IBMCD001
REM DEVICEHIGH=A:\DISPLAY.SYS CON=(EGA,,1)
DEVICEHIGH=A:\RAMDRIVE.SYS /E 4096 512 200

Also, will I have to make changes to the AUTOEXEC.BAT? This is the original from the Recovery Floppy:
@ECHO OFF

SET DRV=X:
SET PATH=%DRV%\

REM Load Code Page, Keyboard and set CC variable
IF EXIST A:\LOCALE.BAT CALL A:\LOCALE.BAT

REM Load necessary drivers (SMARTDRV, MSCDEX, MOUSE, etc.)
IF EXIST A:\DRIVER.BAT CALL A:\DRIVER.BAT

REM FIND DRIVE WITH RECOVERY CD
FINDCD.EXE
IF ERRORLEVEL 25 IF NOT ERRORLEVEL 26 SET DRV=Z:
IF ERRORLEVEL 24 IF NOT ERRORLEVEL 25 SET DRV=Y:
IF ERRORLEVEL 23 IF NOT ERRORLEVEL 24 SET DRV=X:
IF ERRORLEVEL 22 IF NOT ERRORLEVEL 23 SET DRV=W:
IF ERRORLEVEL 21 IF NOT ERRORLEVEL 22 SET DRV=V:
IF ERRORLEVEL 20 IF NOT ERRORLEVEL 21 SET DRV=U:
IF ERRORLEVEL 19 IF NOT ERRORLEVEL 20 SET DRV=T:
IF ERRORLEVEL 18 IF NOT ERRORLEVEL 17 SET DRV=R:
IF ERRORLEVEL 17 IF NOT ERRORLEVEL 16 SET DRV=Q:
IF ERRORLEVEL 16 IF NOT ERRORLEVEL 15 SET DRV=P:
IF ERRORLEVEL 15 IF NOT ERRORLEVEL 14 SET DRV=O:
IF ERRORLEVEL 14 IF NOT ERRORLEVEL 13 SET DRV=N:
IF ERRORLEVEL 13 IF NOT ERRORLEVEL 12 SET DRV=L:
IF ERRORLEVEL 12 IF NOT ERRORLEVEL 11 SET DRV=L:
IF ERRORLEVEL 11 IF NOT ERRORLEVEL 10 SET DRV=K:
IF ERRORLEVEL 10 IF NOT ERRORLEVEL 9 SET DRV=J:
IF ERRORLEVEL 9 IF NOT ERRORLEVEL 8 SET DRV=I:
IF ERRORLEVEL 8 IF NOT ERRORLEVEL 7 SET DRV=H:
IF ERRORLEVEL 7 IF NOT ERRORLEVEL 6 SET DRV=G:
IF ERRORLEVEL 6 IF NOT ERRORLEVEL 5 SET DRV=F:
IF ERRORLEVEL 5 IF NOT ERRORLEVEL 4 SET DRV=E:
IF ERRORLEVEL 4 IF NOT ERRORLEVEL 3 SET DRV=D:
IF ERRORLEVEL 3 IF NOT ERRORLEVEL 2 SET DRV=C:
IF ERRORLEVEL 2 IF NOT ERRORLEVEL 1 SET DRV=B:
IF ERRORLEVEL 1 IF NOT ERRORLEVEL 0 SET DRV=A:

CALL FINDDRV.BAT
COPY A:\*.* %RAMD%\ > NUL
SET COMSPEC=%RAMD%\COMMAND.COM

ECHO
ECHO -----------------
ECHO Recovery Drive=%DRV%
ECHO RAM Drive =%RAMD%
ECHO -----------------
ECHO
%RAMD%
SUBST A: %RAMD%\

PATH=%RAMD%\;%DRV%\RECOVERY;%DRV%\RECOVERY\%CC%

REM Run Recovery program.
REM If RECOVER.BAT does not exist then we are probably running
REM an older version of the Recovery program use the old method.
IF EXIST %DRV%\RECOVER.BAT GOTO NEWRECOV

call %drive%:\DISKETTE.EXE B >NUL
if errorlevel 1 goto YESdiskette
GOTO START

:YESdiskette
if exist B:\MFGMODE goto MFGmode
if exist B:\ERROR.LOG goto MFGcleanup
GOTO START

:MFGmode
if exist B:\PREDL.bat call B:\PREDL.bat
%DRV%\recovery\recover.exe /AUTO /P:%DRV%\RECOVERY
if exist B:\VEPT.EXE B:\VEPT.EXE /n /c /ww
if exist B:\DEVMODE goto DONE
call a:\veptcrc.bat
if exist B:\ERROR.LOG goto DLerror
if exist B:\POSTDL.bat call B:\POSTDL.bat
%drive%:\set_cmos 0 0x36 xxxx0010

if exist c:\windows\options\oemaudit.inf goto 9XAUDIT
%drive%:\fmodify.exe %drive%:\auditnt.fm
GOTO LASTOFAUDIT
:9XAUDIT
%drive%:\fmodify.exe %drive%:\audit98.fm
c:\windows\regedit /L:C:\WINDOWS\system.dat /R:C:\WINDOWS\user.dat %drive%:\mfgbooti.reg
copy %drive%:\mfgbooti.reg c:\mfgboot.reg /y
copy %drive%:\unaudit.exe c:\
copy %drive%:\MFGRESET.BAT c:\

:LASTOFAUDIT
copy %drive%:\set_cmos.exe c:\
copy %drive%:\ERROR.LOG B:\
%drive%:\REBOOT.EXE
GOTO DONE

:MFGcleanup
if exist B:\POSTAUD.bat call B:\POSTAUD.bat
copy A:\TESTER.CTL B:\
del c:\set_cmos.exe
del c:\unaudit.exe
del c:\MFGRESET.BAT
del b:\error.log
A:\set_cmos 0 0x36 xxxx0000
A:\REBOOT.EXE
GOTO DONE

:DLerror
copy A:\TESTER.CTL B:\
A:\set_cmos 0 0x36 xxxx0000
A:\REBOOT.EXE
GOTO DONE

:START
CLS
%RAMD%\DSKSTATE.EXE
IF ERRORLEVEL 2 GOTO GORECOV
IF ERRORLEVEL 1 GOTO DORECOV
IF ERRORLEVEL 0 GOTO CONTINUE

:DORECOV
IF EXIST C:\$APTINST.DAT GOTO DELFILE

:GORECOV
%DRV%\RECOVERY\RECOVER.EXE %COPYR% /P:%DRV%\RECOVERY
IF ERRORLEVEL 2527 GOTO DIAGDISK
IF ERRORLEVEL 2525 GOTO DIAGNOSTICS
IF ERRORLEVEL 2523 GOTO SYSTEMINFO
GOTO DONE

:DELFILE
ERASE C:\$APTINST.DAT

:CONTINUE
%DRV%\RECOVERY\RECOVER.EXE /Y %COPYR% /P:%DRV%\RECOVERY
IF ERRORLEVEL 2527 GOTO DIAGDISK
IF ERRORLEVEL 2525 GOTO DIAGNOSTICS
IF ERRORLEVEL 2523 GOTO SYSTEMINFO
GOTO DONE

:SYSTEMINFO
SET COPYR=/S
%DRV%\PCDR\PCDR.EXE /SI /PAUSE
GOTO START

:DIAGNOSTICS
SET COPYR=/S
%DRV%
CD \PCDR
%DRV%\PCDR\PCDR.EXE
CD \
GOTO START

:DIAGDISK
SET COPYR=/S
%DRV%\PCDR\MAKEDIAG.EXE B:
PAUSE
GOTO START
GOTO DONE

:NEWRECOV
CALL %DRV%\RECOVER.BAT

:DONE
@ECHO ON

I do not know if I should use the USBASPI or Iomega drivers here:
http://www.glennmcc.org/download/usb-dos/dosusb1/

Thanks.

[dr_st]

It looks like it can work. Is there an MSCDEX line in AUTOEXEC.BAT? It doesn't appear here.

You can try USBCD first, IOMEGA drivers if this method doesn't work.

[VintageUniverse]

I ended up changing CONFIG.SYS to this:

REM MSCDEX loaded in Autoexec.bat.

[COMMON]
DEVICE=A:\HIMEM.SYS /TESTMEM:OFF
DOS=HIGH,UMB
SHELL=A:\COMMAND.COM /P /E:512
BUFFERS=20
FILES=40
REM DEVICE=A:\EMM386.EXE ON
DEVICEHIGH=A:\USBASPI.sys /w /v
DEVICEHIGH=A:\DI1000DD.SYS
DEVICEHIGH=A:\USBCD.SYS /D:USBCD001
REM DEVICEHIGH=A:\DISPLAY.SYS CON=(EGA,,1)
DEVICEHIGH=A:\RAMDRIVE.SYS /E 4096 512 200

I ended up using the files provided from this website:
http://www.pcxt-micro.com/dos-usb.html

This is due to the previous CONFIG.SYS ended up causing issues with the USBCD.SYS causing the Recovery Floppy to hang. These files fixed the issue and allowed me to proceed further. See the photos below:
https://www.dropbox.com/sh/05gbsnuoq600 ... msUka?dl=0

The CD-ROM Device Driver is installed as it says in the DOS prompt. However, I get this error after the RAMDrive saying:
"Device Driver not found: 'IBMCD001'."
"No valid CDROM device drivers selected"
"Number of drives 0 Starting drive A"
"None of the drives contains a recovery CD."

Is this due to the AUTOEXEC.BAT? I do not see anywhere for the mention of MSCDEX and the IBMCD001? How should I proceed from here? Thanks.

[theterminator93]

In your config.sys, it is written so that the name for the USBCD driver once loaded is USBCD001. You will need to update that in autoexec.bat (or, based on what you posted, it may be loaded in driver.bat) to be the same, or you could change it in config.sys to be IBMCD001 which is what the name of the driver is when it's called by the batch process. See if it loads with either change.

[VintageUniverse]

That did the trick! The modded T23 Recovery Floppy was able to install the USB CD-ROM drivers for the external USB IOMEGA Predator CD-RW CDRW9602EXT-B Drive and loaded the Product Recovery procedure from the CD after the change to CONFIG.sys! Successfully done and possible without the UltraBase!

However, I tested the Product Recovery CDs you had sent me via PM multiple times:
T23 2K = recovery procedure does not load at all after the floppy loads the drive into DOS, stuck at a blinking cursor on the top left of the screen and sometimes says "error reading CDR101 abort, retry, fail"?
T22 2K = recovery procedure loads, but gives errors and cuts off to a black screen with a blinking cursor on the top left of the screen and stays there different scenarios sometimes says "can't read file 1.PCM IBM"
T21 98SE = recovery procedure loads, but hangs when it comes to changing structures process in the PowerQuest EasyRestore around 90%

I do not know why this is:
Is it due to the use of the T23 Recovery Floppy?

Should I modify and use the T21 and T22 Recovery Floppies for the appropriate Product Recovery CDs?

Compatibility issues with the X21?

Possibly corrupt images of the original Product Recovery CDs?

The only Product Recovery CD that worked with the modded T23 Recovery Floppy was this one:
https://archive.org/details/23p2972cracked

It worked fine and loaded everything without any errors. Even though my X21 has a 2K COA, the 98SE from the product Recovery CD installed fine without asking for the product key. The default region is UK from what I believe on this Product Recovery CD so maybe a Europe variant and not a US one. Not all of the drivers were properly were installed and there was a lot of IBM features and goodies (IBM ThinkPad software, wallpaper, etc.) that were missing from the restore procedure. More importantly the OS is not the Windows 2000 US variant.

Will a ThinkPad A20 Series Product Recovery CD for Windows 2000 possibly work? Like this one for the A20m:
https://archive.org/details/IBM_ThinkPa ... 1_2000_Eng

Thanks.

[VintageUniverse]

The A20m Product Recovery CD with the modded T23 Recovery Floppy worked perfectly on the machine and I now have a factory install of IBM OEM Windows 2000 for the US Region. Some drivers are shared between the A20m and X21, such as the graphics. Others I have to track down online as well as the IBM programs and Wallpapers. The A2x Series is a closer match to the X2x Series than the T2x Series. Thanks guys!