IBM Info WarpTips: Difference between revisions

From OS2World.Com Wiki
Jump to navigation Jump to search
Jugbogdan (talk | contribs)
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==950118 TIMING HANG ON IBM PC 300 SERIES - 486 SYSTEMS AND ON ALL APTIVA'S FROM THE 310 (2144-22P) THROUGH THE 530 (2144-66P).==
==950118 TIMING HANG ON IBM PC 300 SERIES - 486 SYSTEMS AND ON ALL APTIVA'S FROM THE 310 (2144-22P) THROUGH THE 530 (2144-66P).==
;DESCRIPTION OF SYMPTOMS                                                      
;DESCRIPTION OF SYMPTOMS
When the IBM PC 300 Series - 486 Systems BIOS code switched CMOS banks, OS/2 (and the physical clock Device Driver) did not know that the CMOS bank was switched. If an IRQ 8 (realtime clock interrupt) came in when the CMOS bank was switched, then the system would hang because the clock DD would read the RTC CMOS locations on the 2nd bank when it should have read them on the 1st bank.                
When the IBM PC 300 Series - 486 Systems BIOS code switched CMOS banks, OS/2 (and the physical clock Device Driver) did not know that the CMOS bank was switched. If an IRQ 8 (realtime clock interrupt) came in when the CMOS bank was switched, then the system would hang because the clock DD would read the RTC CMOS locations on the 2nd bank when it should have read them on the 1st bank.
                                                                               
 
The OS/2 virtual DD (VCMOS.SYS) did not allow writes to CMOS with addresses < 0Eh. So, the Rapid Resume data could not be written by a VDM (DOS session or windows). VCMOS.SYS virtualizes ports 70H and 71H.                                                                      
The OS/2 virtual DD (VCMOS.SYS) did not allow writes to CMOS with addresses < 0Eh. So, the Rapid Resume data could not be written by a VDM (DOS session or windows). VCMOS.SYS virtualizes ports 70H and 71H.
                                                                               
 
;RESOLUTION                                                                  
;RESOLUTION
VCMOS.SYS will now virtualize ports 22H and 24H when on IBM PC 300 Series - 486 Systems or Aptiva.                                        
VCMOS.SYS will now virtualize ports 22H and 24H when on IBM PC 300 Series - 486 Systems or Aptiva.
A fix must be applied to the OS/2 system to correct this problem.                                                                      
A fix must be applied to the OS/2 system to correct this problem.
                                                                               
 
How to apply the fix                                                          
How to apply the fix
                                                                               
 
In the fixes sent to you will be a file called VCMOS.SYS. After the install is complete, copy VCMOS.SYS to ?:\OS2\MDOS directory (? is the drive you installed OS/2 into).                                            
In the fixes sent to you will be a file called VCMOS.SYS. After the install is complete, copy VCMOS.SYS to ?:\OS2\MDOS directory (? is the drive you installed OS/2 into).


;NOTE: Please refer to PDDB Item FFZTV title APTIVA UPDATE. It has information on how to get the fix.
;NOTE: Please refer to PDDB Item FFZTV title APTIVA UPDATE. It has information on how to get the fix.


==TITLE: 950123 INSTALLATION WARP ON A PS/2 8580 WITH A CYRIX UPGRADE CHIP, HANG ON DISK #1 WITH BLINKING CURSOR WITH THE DRIVE LIGHT ON.==                                          
==950123 INSTALLATION WARP ON A PS/2 8580 WITH A CYRIX UPGRADE CHIP, HANG ON DISK #1 WITH BLINKING CURSOR WITH THE DRIVE LIGHT ON.==
                                                                               
;DESCRIPTION OF SYMPTOMS:
;DESCRIPTION OF SYMPTOMS:                                                      
Goes thru installation disk and prompts for disk #1 as normal.
    Goes thru installation disk and prompts for disk #1 as normal.            
Goes thru OS/2 logo, "loading please wait" panel and then screen turns blank, cursor goes in top left, floppy light stays on and system appears to be hung. Ctrl+Alt+Del does not work at this point and a hard reset has to be performed.
    Goes thru OS/2 logo, "loading please wait" panel and then                  
 
    screen turns blank, cursor goes in top left, floppy light stays on        
;RESOLUTION:
    and system appears to be hung. Ctrl+Alt+Del does not work                
This system is a PS/2 8580 with a Cyrix 486dx 20/40 Mhz, 16mb RAM, 4mb on the system board, and two memory cards consists of 4mb installed and one with 8mb. Both cards had 85NS simms on them.
    at this point and a hard reset has to be performed.                        
ALT+F2 routine showed that all the drivers were loading and installion OS2DASD.DMD was last one to load and install, then the cursor went to    
                                                                               
upper left corner and the system locked (cold boot needed).  
;RESOLUTION:                                                                    
From problem determination, user has taken out the 4mb card and then the 8mb card, user has find out that with the 8mb card out, the system was able to install and pass the problem. This is a hardware problem.
  This system is a PS/2 8580 with a Cyrix 486dx 20/40 Mhz, 16mb                
 
  RAM, 4mb on the system board, and two memory cards consists of              
;Note: Tried PJ16077 workaround, but was unsuccessful.
  4mb installed and one with 8mb. Both cards had 85NS simms on them.          
 
  ALT+F2 routine showed that all the drivers were loading and installion      
==950124 Trap 000D with CS:EIP = 1000 : 00002eb6 on Final Reboot==
  OS2DASD.DMD was last one to load and install, then the cursor went to        
;DESCRIPTION OF SYMPTOMS:
  upper left corner and the system locked (cold boot needed).                  
:Trap on Final Reboot and every subsequent boot with above CS:EIP value.
  From problem determination, user has taken out the 4mb card and then        
 
  the 8mb card, user has find out that with the 8mb card out, the system      
;SUMMARY OF RESOLUTION:
  was able to install and pass the problem.                                    
:Incorrect statements in CONFIG.SYS results in Trap and it is resolved by copying the generic CONFIG.SYS to the root drive.
  This is a hardware problem.                                                  
  Note: Tried PJ16077 workaround, but was unsuccessful.                      
                                                                             


==950124 Trap 000D with CS:EIP = 1000 : 00002eb6 on Final Reboot==     
;DETAILS OF RESOLUTION:
;DESCRIPTION OF SYMPTOMS:                                                       
:Trap on Final Reboot and every subsequent boot with above CS:EIP value.                                                                         
                                                                               
;SUMMARY OF RESOLUTION:                                                         
:Incorrect statements in CONFIG.SYS results in Trap and it is resolved by copying the generic CONFIG.SYS to the root drive.                 
                                                                               
;DETAILS OF RESOLUTION:                                                        
:Follow procedure " Recovering the CONFIG.SYS File " on page 220 of Warp User's Guide to recover the original CONFIG.SYS.
:Follow procedure " Recovering the CONFIG.SYS File " on page 220 of Warp User's Guide to recover the original CONFIG.SYS.


==950125 INSTALL PCMCIA ON IBM THINKPAD 755CD FROM WARP, UNABLE TO ACCESS THE INTERNAL IDE CDROM==            
==950125 INSTALL PCMCIA ON IBM THINKPAD 755CD FROM WARP, UNABLE TO ACCESS THE INTERNAL IDE CDROM==
                                                                               
;DESCRIPTION OF SYMPTOMS:
DESCRIPTION OF SYMPTOMS:                                                      
IBM ThinkPad 755CD which has an IDE CDROM. User loaded the PCMCIA drivers from OS/2 WARP. Afterwarp, shutdown and reboot the system, user is unable to access the internal IDE CDROM device.
IBM ThinkPad 755CD which has an IDE CDROM. User loaded the                  
 
PCMCIA drivers from OS/2 WARP. Afterwarp, shutdown and reboot the            
;RESOLUTION:
system, user is unable to access the internal IDE CDROM device.              
From the problem determination, this is an IRQ conflict.
                                                                               
Change the PCMCIA IRQ setting. To do this, add the following parameters to BASEDEV=IBM2SS01.SYS:
RESOLUTION:                                                                    
" BASEDEV=IBM2SS01.SYS /S0=1 /C0=11 "
From the problem determination, this is an IRQ conflict.                      
Use IRQ 11 because it was an open IRQ.
Change the PCMCIA IRQ setting. To do this, add the following                
Shutdown and reboot and the user should be able to access both the PCMCIA and the internal IDE CDROM device.
parameters to BASEDEV=IBM2SS01.SYS:                                          
  " BASEDEV=IBM2SS01.SYS /S0=1 /C0=11 "                                        
Use IRQ 11 because it was an open IRQ.                                        
Shutdown and reboot and the user should be able to access both                
the PCMCIA and the internal IDE CDROM device.                                
                                                                               
Note above that it is not neccessary to use IRQ 11.  User should             
be able to find an IRQ that is available.     


Note above that it is not necessary to use IRQ 11. User should be able to find an IRQ that is available.


==950126 ERROR " NOT ENOUGH SPACE ON HARD DISK " WITH 8590 WITH NEC CDROM CONNECTED ( SCSI I )==
==950126 ERROR " NOT ENOUGH SPACE ON HARD DISK " WITH 8590 WITH NEC CDROM CONNECTED (SCSI I)==
;SYMPTOMS:
;SYMPTOMS:
On disk #1, error msg " Not Enough Hard Disk Space to
On disk #1, error msg " Not Enough Hard Disk Space to Install ... "
    Install ... "


Note: This is a CD-ROM installation. User boots up on the Installation disk and when prompt, puts in the disk #1 of the cdrom.
;Note: This is a CD-ROM installation. User boots up on the Installation disk and when prompt, puts in the disk #1 of the cdrom.
No doublespace on the harddrive. Only DOS/Windows. FDISK did not see any "strange partitions", if it shows, this indicates that there is a "monkeys" virus.
No doublespace on the harddrive. Only DOS/Windows. FDISK did not see any "strange partitions", if it shows, this indicates that there is a "monkeys" virus.


;RESOLUTION:
;RESOLUTION:
Line 103: Line 85:
==950128 DMA TIMEOUT ERROR OR HANG WHEN STARTING WINOS2 FULL SCREEN SESSION UNDER WARP 3.0 WHEN USING CRYSTAL SEMI CHIP (CS4231) ON IBM THINKPADS.==
==950128 DMA TIMEOUT ERROR OR HANG WHEN STARTING WINOS2 FULL SCREEN SESSION UNDER WARP 3.0 WHEN USING CRYSTAL SEMI CHIP (CS4231) ON IBM THINKPADS.==


DESCRIPTION OF SYMPTOMS:
;DESCRIPTION OF SYMPTOMS:
    Symptom 1.
Symptom 1.
:When users install the Crystal Semi (cs4231) Winos2 drivers according to the Multimedia On Line Help a DMA Timeout error
is produced when a Winos2 Fullscreen is started. The session may also hang even though the drivers have been installed properly.


      When users install the Crystal Semi (cs4231) Winos2 drivers
;SUMMARY OF RESOLUTION:
      according to the Multimedia On Line Help a DMA Timeout error
See details of resolution.
      is produced when a Winos2 Fullscreen is started. The session
      may also hang even though the drivers have been installed
      properly.


SUMMARY OF RESOLUTION:
;DETAILS OF RESOLUTION:
    See details of resolution.
The native Windows drivers for the Crystal Semi chip (cs4231) have to be removed since they are VXD's. They are not supported under OS/2 WARP 3.0. The Multimedia On Line help does not refer to these drivers and their removal prior to installing the Winos2 Crystal Semi Drivers. Please follow the steps below to remove:
 
DETAILS OF RESOLUTION:
    The native Windows drivers for the Crystal Semi chip (cs4231)
    have to be removed since they are VXD's. They are not supported
    under OS/2 WARP 3.0. The Multimedia On Line help does not refer
    to these drivers and their removal prior to installing the Winos2
    Crystal Semi Drivers. Please follow the steps below to remove:
 
    1. Locate and EDIT the Windows SYSTEM.INI file.
 
      a. Locate TPAUDVXD.386 in the 386ehn section.
        Remove this statement:


        Drivers=TPAUDVXD.DRV
1. Locate and EDIT the Windows SYSTEM.INI file.
:a. Locate TPAUDVXD.386 in the 386ehn section.
:Remove this statement:
  Drivers=TPAUDVXD.DRV
:b. Locate IBMMME.DRV in the DRIVERS section.
:Remove these statements:
Aux=IBMMME.DRV
WAVE=IBMMME.DRV
MIDI=IBMMME.DRV
2. Save and exit out of the Editor.


      b. Locate IBMMME.DRV in the DRIVERS section.
You will now be able to start the Winos2 Fullscreen session
        Remove these statements:
 
        Aux=IBMMME.DRV
        WAVE=IBMMME.DRV
        MIDI=IBMMME.DRV
 
    2.  Save and exit out of the Editor.
 
    You will now be able to start the Winos2 Fullscreen session


==950130 Installing from CDROM, using device drivers other than IBM supplied drivers. (WARP)==
==950130 Installing from CDROM, using device drivers other than IBM supplied drivers. (WARP)==
;DESCRIPTION OF SYMPTOMS:
;DESCRIPTION OF SYMPTOMS:
    If the user is installing from a drive other
If the user is installing from a drive other than A: (e.g. CDROM), and a device driver that does not exist on DISK #1 (note: user has the device driver file from the vendor), the install process will not copy this file onto the hardfile after the installation is complete. The
    than A: (e.g. CDROM), and a device driver
cause of this problem is because if the user could not boot with the drivers that are present on the hardfile, then he will have to boot from
    that does not exist on DISK #1 (note: user has
diskettes or another partition, then copy the device driver file over.
    the device driver file from the vendor), the install
    process will not copy this file onto the
    hardfile after the installation is complete. The
    cause of this problem is because if the user could
    not boot with the drivers that are present on the
    hardfile, then he will have to boot from
    diskettes or another partition, then copy the device
    driver file over.


;RESOLUTION:
;RESOLUTION:
    Development has added an environment variable called
Development has added an environment variable called copyfromfloppy that the installation program will read from CONFIG.SYS on diskette #1. If the CONFIG.SYS has the statement "set copyfromfloppy=1", then the installation program will copy files from disk #1 if the diskette is in the drive, and the installation is from a drive other than A:.
    copyfromfloppy that the installation program will
    read from CONFIG.SYS on diskette #1. If the
    CONFIG.SYS has the statement " set copyfromfloppy=1 ", then
    the installation program will copy files from
    disk #1 if the diskette is in the drive, and the
    installation is from a drive other than A:.
 


==950131 WARP AND OS/2 2.1 SE FOR WINDOWS CANNOT INSTALL ON APTIVA SYSTEMS WHICH ARE PRE-LOADED WITH DOS/WINDOWS==
==950131 WARP AND OS/2 2.1 SE FOR WINDOWS CANNOT INSTALL ON APTIVA SYSTEMS WHICH ARE PRE-LOADED WITH DOS/WINDOWS==
;DESCRIPTION OF SYMPTOMS:
;DESCRIPTION OF SYMPTOMS:
During the installation of WARP and OS/2 2.1 SE for Windows, the user is prompted for WINDOWS diskettes.
During the installation of WARP and OS/2 2.1 SE for Windows, the user is prompted for WINDOWS diskettes.
Line 182: Line 134:


In the .Disks. section the following statements appear:
In the .Disks. section the following statements appear:
        1 =. ,"Microsoft Windows 3.1 Disk #1",disk1
1 =. ,"Microsoft Windows 3.1 Disk #1",disk1
        2 =. ,"Microsoft Windows 3.1 Disk #2",disk2
2 =. ,"Microsoft Windows 3.1 Disk #2",disk2
        3 =. ,"Microsoft Windows 3.1 Disk #3",disk3
3 =. ,"Microsoft Windows 3.1 Disk #3",disk3
        4 =. ,"Microsoft Windows 3.1 Disk #4",disk4
4 =. ,"Microsoft Windows 3.1 Disk #4",disk4
        5 =. ,"Microsoft Windows 3.1 Disk #5",disk5
5 =. ,"Microsoft Windows 3.1 Disk #5",disk5
        6 =. ,"Microsoft Windows 3.1 Disk #6",disk6
6 =. ,"Microsoft Windows 3.1 Disk #6",disk6
 
Edit these statements so they appear as follows
Edit these statements so they appear as follows
        1 =X:\windows\drivers,"Microsoft Windows 3.1 Disk #1",disk1
1 =X:\windows\drivers,"Microsoft Windows 3.1 Disk #1",disk1
        2 =X:\windows\drivers,"Microsoft Windows 3.1 Disk #2",disk2
2 =X:\windows\drivers,"Microsoft Windows 3.1 Disk #2",disk2
        3 =X:\windows\drivers,"Microsoft Windows 3.1 Disk #3",disk3
3 =X:\windows\drivers,"Microsoft Windows 3.1 Disk #3",disk3
        4 =X:\windows\drivers,"Microsoft Windows 3.1 Disk #4",disk4
4 =X:\windows\drivers,"Microsoft Windows 3.1 Disk #4",disk4
        5 =X:\windows\drivers,"Microsoft Windows 3.1 Disk #5",disk5
5 =X:\windows\drivers,"Microsoft Windows 3.1 Disk #5",disk5
        6 =X:\windows\drivers,"Microsoft Windows 3.1 Disk #6",disk6
6 =X:\windows\drivers,"Microsoft Windows 3.1 Disk #6",disk6
 
where X= the drive where Windows is installed.
where X= the drive where Windows is installed.


This change should be in place before installation, but can be made after to use with the SELECTIVE INSTALL feature
This change should be in place before installation, but can be made after to use with the SELECTIVE INSTALL feature


==TITLE: 950131 A:\COUNTRY.SYS IS INCORRECT ON DISK #1 WHEN INSTALLING OS/2 WARP.==
==950131 A:\COUNTRY.SYS IS INCORRECT ON DISK #1 WHEN INSTALLING OS/2 WARP.==
;DESCRIPTION OF SYMPTOMS:
Installing OS/2 WARP, on disk #1 encountered " A:\country.sys is incorrect ".


DESCRIPTION OF SYMPTOMS:
;RESOLUTION:
    Installing OS/2 WARP, on disk #1 encountered " A:\country.sys
Check the CMOS. If the user has changed the floppy drives around, make sure the CMOS is setup correctly.
    is incorrect ".
Example, if the user switch 1.44mb drive from B to A, and 1.2mb drive from A to B, CMOS must be setup and change that reflect the A drive as 1.44mb and B drive as 1.2mb.


RESOLUTION:
;Note:
    Check the CMOS.  If the user has changed the floppy drives
Some floppy drives controller has the ability to override the cmos. This means that the card is set for the original setup.
    around, make sure the CMOS is setup correctly.
For example, if the card is setup for 5 1/4" as A: drive and the user switched the 3 1/2" drive to become A: drive and go into
    Example, if the user switch 1.44mb drive from B to A, and 1.2mb
the cmos and change it, when bootup, the card will override the setup on the cmos and still make the 5 1/4" as A:.
    drive from A to B, CMOS must be setup and change that reflect
Advice user to check the controller manual to disable this option on the card. Or refer him/her back to where they bought the controller card.
    the A drive as 1.44mb and B drive as 1.2mb.
 
Note:
;Update: 01/17/1995
    Some floppy drives controller has the ability to override the
Keywords: country sys warp install a:\country.sys country.sys
    cmos. This means that the card is set for the original setup.
    For example, if the card is setup for 5 1/4" as A: drive and
    the user switched the 3 1/2" drive to become A: drive and go into
    the cmos and change it, when bootup, the card will override
    the setup on the cmos and still make the 5 1/4" as A:.
    Advice user to check the controller manual to disable this option
    on the card. Or refer him/her back to where they bought the
    controller card.
    Update: 01/17/1995
    Keywords: country sys warp install a:\country.sys country.sys


==950202 IPE  ## 1000 : 00000DBB - 0002 : 0DBB  60000, 2008 INTERNAL REVISION 8.162 AFTER THE SECOND PHASE OF INSTALLATION OF WARP==
==950202 IPE  ## 1000 : 00000DBB - 0002 : 0DBB  60000, 2008 INTERNAL REVISION 8.162 AFTER THE SECOND PHASE OF INSTALLATION OF WARP==
Line 239: Line 181:
;RESOLUTION:
;RESOLUTION:
A couple of issues user needs to take a look at.
A couple of issues user needs to take a look at.
1. On the root directory, there are many files (excess of 200 plus files) that can cause this IPE.   User's needs to move these files to a temporary directory. Check the WARP user's manual on
 
setting up dualboot for more information.
1. On the root directory, there are many files (excess of 200 plus files) that can cause this IPE. User's needs to move these files to a temporary directory. Check the WARP user's manual on setting up dualboot for more information.
Under dualboot setup, it is suggested to move files from the root that are not needed before installation of OS/2.
Under dualboot setup, it is suggested to move files from the root that are not needed before installation of OS/2.


2. On some Thinkpad systems, on the 2nd phase of installation, user has changed the mouse pointer instead of choosing default.
2. On some Thinkpad systems, on the 2nd phase of installation, user has changed the mouse pointer instead of choosing default.
User needs to leave it as default.
User needs to leave it as default.
To correct this problem, use the alt+f1 routine and choose M to the maintenance desktop and make sure the mouse pointer is set correctly for the Thinkpad. Usually, it is set for default.
To correct this problem, use the alt+f1 routine and choose M to the maintenance desktop and make sure the mouse pointer is set correctly for the Thinkpad. Usually, it is set for default.


==950203 THREE IDE 563 PANASONIC CDROM DRIVES WORKING UNDER OS/2 WARP==
==950203 THREE IDE 563 PANASONIC CDROM DRIVES WORKING UNDER OS/2 WARP==
;SYMPTOMS: Multiple cdroms connected to the same IDE adapter (SB16 card) are not recognize.
;SYMPTOMS: Multiple cdroms connected to the same IDE adapter (SB16 card) are not recognize.


Line 255: Line 196:
Contact Creative Labs for more information.
Contact Creative Labs for more information.
Note that at this point, multiple 563 Panasonic IDE CDROM drives are not supported.
Note that at this point, multiple 563 Panasonic IDE CDROM drives are not supported.
==950203 FAILURE TO RECOGNIZE IDE CD-ROM DRIVE==
;USERS
All users of PCs with IDE CD-ROM drives
;DESCRIPTION OF SYMPTOMS:
Failure to recognize CD-ROM drive.
Installing or booting OS/2 Warp on a system with an IDE CD-ROM drive, a red screen appears as the system is initializing the OS2CDROM.DMD device manager. During installation, device managers are initialized during the processing of Disk 1. The message indicates that there is no CD-ROM drive support.
;SUMMARY OF RESOLUTION:
If an IDE CD-ROM drive and an IDE hard drive share a disk controller, then the user should ensure that the hard drive is configured as the master and the CD-ROM drive is configured as the slave.
**BUT** If the CD-ROM drive and the hard drive are on separate disk controllers, then the user should ensure that both drives are configured as masters.
;DETAILS OF RESOLUTION:
Any pair of IDE drives that shares a controller should be setup in a master-slave configuration. There must, however, be one master per
controller in order for the drive on that bus to be recognized. These rules apply for any operating system, but they have only
begun to cause CD-ROM problems for OS/2 as of the Warp release, the first release to include IDE CD-ROM drive support.
For example, if the system has an IDE CD-ROM drive on its PCI bus and an IDE hard drive on its ISA bus, then both the CD-ROM drive and the hard drive should be configured as masters. If the CD-ROM drive is swapped to the ISA bus at a later date, so that it shares a disk controller with the IDE hard drive, then the user must reconfigure the CD-ROM drive as a slave.
Note that any such combination of drives requires both the IBMIDECD.FLT device driver and the IBM1S506.ADD device driver. If two disk controllers are present, the BASEDEV= statement for the IBM1S506.ADD driver needs the parameter /A:0 to indicate the primary controller or /A:1 to indicate the secondary controller. For more information about these and other parameters, enter...
HELP IBM1S506.ADD
...or...
HELP IBMIDECD.FLT
...at an OS/2 command line.
The user should refer to their hardware's documentation or call the manufacturer's tech support line to find out how to reconfigure their drive as a master or slave.
Note: If the user is able to install OS/2 from the CD-ROM drive, then the drive is configured correctly. Therefore, if the CD-ROM drive is not recognized when OS/2 is booted later, then the user may need to simply add the statement...
BASEDEV=x:\OS2\BOOT\IBMIDECD.FLT
...to the CONFIG.SYS file.


==950206 PS/2 9595 PENTIUM WITH 64MB RAM AND DISK ARRAY UNDER WARP==
==950206 PS/2 9595 PENTIUM WITH 64MB RAM AND DISK ARRAY UNDER WARP==
; SYMPTOMS:
; SYMPTOMS:
The DISK ARRAY is at level 5 with 6-2gb SCSI drives. Partitioned the drive C: 150mb and the rest as logical 10gb drive. Under OS/2 WARP, tried to format the logical partition, it reports only 3mb is available. Then FDISK reports the partition is unformatted.
The DISK ARRAY is at level 5 with 6-2gb SCSI drives. Partitioned the drive C: 150mb and the rest as logical 10gb drive. Under OS/2 WARP, tried to format the logical partition, it reports only 3mb is available. Then FDISK reports the partition is unformatted.


Note: This is after user formatted the logical drive which is suppose to be 10gb.
Note: This is after user formatted the logical drive which is suppose to be 10gb.
Line 268: Line 242:


Suggested download the following files/images from IBM BBS at 919/517/0001:
Suggested download the following files/images from IBM BBS at 919/517/0001:
    1. RF90954A.DSK
1. RF90954A.DSK
    2. RD9095A.DSK
2. RD9095A.DSK
    3. LDF.COM
3. LDF.COM
    4. RAID162A.DSK
4. RAID162A.DSK
    5. NEWRAID.DSK ( newer IBMRAID.ADD
5. NEWRAID.DSK (newer IBMRAID.ADD)
 
[[Category:How To]]

Latest revision as of 00:15, 5 December 2022

950118 TIMING HANG ON IBM PC 300 SERIES - 486 SYSTEMS AND ON ALL APTIVA'S FROM THE 310 (2144-22P) THROUGH THE 530 (2144-66P).

DESCRIPTION OF SYMPTOMS

When the IBM PC 300 Series - 486 Systems BIOS code switched CMOS banks, OS/2 (and the physical clock Device Driver) did not know that the CMOS bank was switched. If an IRQ 8 (realtime clock interrupt) came in when the CMOS bank was switched, then the system would hang because the clock DD would read the RTC CMOS locations on the 2nd bank when it should have read them on the 1st bank.

The OS/2 virtual DD (VCMOS.SYS) did not allow writes to CMOS with addresses < 0Eh. So, the Rapid Resume data could not be written by a VDM (DOS session or windows). VCMOS.SYS virtualizes ports 70H and 71H.

RESOLUTION

VCMOS.SYS will now virtualize ports 22H and 24H when on IBM PC 300 Series - 486 Systems or Aptiva. A fix must be applied to the OS/2 system to correct this problem.

How to apply the fix

In the fixes sent to you will be a file called VCMOS.SYS. After the install is complete, copy VCMOS.SYS to ?:\OS2\MDOS directory (? is the drive you installed OS/2 into).

NOTE
Please refer to PDDB Item FFZTV title APTIVA UPDATE. It has information on how to get the fix.

950123 INSTALLATION WARP ON A PS/2 8580 WITH A CYRIX UPGRADE CHIP, HANG ON DISK #1 WITH BLINKING CURSOR WITH THE DRIVE LIGHT ON.

DESCRIPTION OF SYMPTOMS

Goes thru installation disk and prompts for disk #1 as normal. Goes thru OS/2 logo, "loading please wait" panel and then screen turns blank, cursor goes in top left, floppy light stays on and system appears to be hung. Ctrl+Alt+Del does not work at this point and a hard reset has to be performed.

RESOLUTION

This system is a PS/2 8580 with a Cyrix 486dx 20/40 Mhz, 16mb RAM, 4mb on the system board, and two memory cards consists of 4mb installed and one with 8mb. Both cards had 85NS simms on them. ALT+F2 routine showed that all the drivers were loading and installion OS2DASD.DMD was last one to load and install, then the cursor went to upper left corner and the system locked (cold boot needed). From problem determination, user has taken out the 4mb card and then the 8mb card, user has find out that with the 8mb card out, the system was able to install and pass the problem. This is a hardware problem.

Note
Tried PJ16077 workaround, but was unsuccessful.

950124 Trap 000D with CS:EIP = 1000 : 00002eb6 on Final Reboot

DESCRIPTION OF SYMPTOMS
Trap on Final Reboot and every subsequent boot with above CS:EIP value.
SUMMARY OF RESOLUTION
Incorrect statements in CONFIG.SYS results in Trap and it is resolved by copying the generic CONFIG.SYS to the root drive.
DETAILS OF RESOLUTION
Follow procedure " Recovering the CONFIG.SYS File " on page 220 of Warp User's Guide to recover the original CONFIG.SYS.

950125 INSTALL PCMCIA ON IBM THINKPAD 755CD FROM WARP, UNABLE TO ACCESS THE INTERNAL IDE CDROM

DESCRIPTION OF SYMPTOMS

IBM ThinkPad 755CD which has an IDE CDROM. User loaded the PCMCIA drivers from OS/2 WARP. Afterwarp, shutdown and reboot the system, user is unable to access the internal IDE CDROM device.

RESOLUTION

From the problem determination, this is an IRQ conflict. Change the PCMCIA IRQ setting. To do this, add the following parameters to BASEDEV=IBM2SS01.SYS:

" BASEDEV=IBM2SS01.SYS /S0=1 /C0=11 "

Use IRQ 11 because it was an open IRQ. Shutdown and reboot and the user should be able to access both the PCMCIA and the internal IDE CDROM device.

Note above that it is not necessary to use IRQ 11. User should be able to find an IRQ that is available.

950126 ERROR " NOT ENOUGH SPACE ON HARD DISK " WITH 8590 WITH NEC CDROM CONNECTED (SCSI I)

SYMPTOMS

On disk #1, error msg " Not Enough Hard Disk Space to Install ... "

Note
This is a CD-ROM installation. User boots up on the Installation disk and when prompt, puts in the disk #1 of the cdrom.

No doublespace on the harddrive. Only DOS/Windows. FDISK did not see any "strange partitions", if it shows, this indicates that there is a "monkeys" virus.

RESOLUTION

User has upgraded the EPROM for this 8590 and changed the NEC CDROM to set it SCSI I, since the IBM SCSI controller is SCSI I compliant.

950127 PRINTING ENVELOPES FROM AMIPRO 3.1 UNDER WARP

DESCRIPTION OF SYMPTOMS

When trying to print envelopes from amipro under warp, the envelopes being manually fed, paper is still being fed from the paper tray.

SUMMARY OF RESOLUTION

The paper source may need to be changed

DETAILS OF RESOLUTION

From the amipro main screen, select file , printer setup, choose a printer from the dialogue and select setup. You will see a selection for paper source. If envelopes are being manually fed, this should be set to manual not envelope.

950128 ADD ON DAUGHTER OR WAVE TABLE BOARDS NOT SUPPORTED UNDER OS/2 WARP 3.0

DESCRIPTION OF SYMPTOMS

See details of resolution.

SUMMARY OF RESOLUTION

See details of resolution.

DETAILS OF RESOLUTION

Add on Daughter boards which enable wave table midi support are not supported under any version OS/2 including Warp 3.0.

These boards can be attached to several sound cards available on the market especially Sound Blaster cards. Users need to contact the vendor for proper OS/2 drivers if available. If a user has aquired an OS/2 driver for the Daughter board and is experiencing a problem using the device the vendor needs to be contacted for support

950128 DMA TIMEOUT ERROR OR HANG WHEN STARTING WINOS2 FULL SCREEN SESSION UNDER WARP 3.0 WHEN USING CRYSTAL SEMI CHIP (CS4231) ON IBM THINKPADS.

DESCRIPTION OF SYMPTOMS

Symptom 1.

When users install the Crystal Semi (cs4231) Winos2 drivers according to the Multimedia On Line Help a DMA Timeout error

is produced when a Winos2 Fullscreen is started. The session may also hang even though the drivers have been installed properly.

SUMMARY OF RESOLUTION

See details of resolution.

DETAILS OF RESOLUTION

The native Windows drivers for the Crystal Semi chip (cs4231) have to be removed since they are VXD's. They are not supported under OS/2 WARP 3.0. The Multimedia On Line help does not refer to these drivers and their removal prior to installing the Winos2 Crystal Semi Drivers. Please follow the steps below to remove:

1. Locate and EDIT the Windows SYSTEM.INI file.

a. Locate TPAUDVXD.386 in the 386ehn section.
Remove this statement:
 Drivers=TPAUDVXD.DRV
b. Locate IBMMME.DRV in the DRIVERS section.
Remove these statements:
Aux=IBMMME.DRV
WAVE=IBMMME.DRV
MIDI=IBMMME.DRV

2. Save and exit out of the Editor.

You will now be able to start the Winos2 Fullscreen session

950130 Installing from CDROM, using device drivers other than IBM supplied drivers. (WARP)

DESCRIPTION OF SYMPTOMS

If the user is installing from a drive other than A: (e.g. CDROM), and a device driver that does not exist on DISK #1 (note: user has the device driver file from the vendor), the install process will not copy this file onto the hardfile after the installation is complete. The cause of this problem is because if the user could not boot with the drivers that are present on the hardfile, then he will have to boot from diskettes or another partition, then copy the device driver file over.

RESOLUTION

Development has added an environment variable called copyfromfloppy that the installation program will read from CONFIG.SYS on diskette #1. If the CONFIG.SYS has the statement "set copyfromfloppy=1", then the installation program will copy files from disk #1 if the diskette is in the drive, and the installation is from a drive other than A:.

950131 WARP AND OS/2 2.1 SE FOR WINDOWS CANNOT INSTALL ON APTIVA SYSTEMS WHICH ARE PRE-LOADED WITH DOS/WINDOWS

DESCRIPTION OF SYMPTOMS

During the installation of WARP and OS/2 2.1 SE for Windows, the user is prompted for WINDOWS diskettes. Aptiva systems which are delivered with DOS/WINDOWS pre-installed have no diskettes with which to finish the installation process. The WIN-OS/2 component is unable to install.

SUMMARY OF RESOLUTION
Edit SETUP.INF
DETAILS OF RESOLUTION

Three Files are used during installation of Windows which provide information necessary to properly install and maintain the Windows platform. The key file which Windows Setup uses to install the Windows system and it's application files is SETUP.INF (the other two are CONTROL.INF and APPS.INF).

SETUP.INF by default, has 13 sections, one of which needs to be edited to enable the WIN-OS/2 component to install.

The "DISKS" section describe disks which might be requested during installation and their characteristics. This section needs to be edited as follows to enable WIN-OS/2 support.

In the .Disks. section the following statements appear:

1 =. ,"Microsoft Windows 3.1 Disk #1",disk1
2 =. ,"Microsoft Windows 3.1 Disk #2",disk2
3 =. ,"Microsoft Windows 3.1 Disk #3",disk3
4 =. ,"Microsoft Windows 3.1 Disk #4",disk4
5 =. ,"Microsoft Windows 3.1 Disk #5",disk5
6 =. ,"Microsoft Windows 3.1 Disk #6",disk6

Edit these statements so they appear as follows

1 =X:\windows\drivers,"Microsoft Windows 3.1 Disk #1",disk1
2 =X:\windows\drivers,"Microsoft Windows 3.1 Disk #2",disk2
3 =X:\windows\drivers,"Microsoft Windows 3.1 Disk #3",disk3
4 =X:\windows\drivers,"Microsoft Windows 3.1 Disk #4",disk4
5 =X:\windows\drivers,"Microsoft Windows 3.1 Disk #5",disk5
6 =X:\windows\drivers,"Microsoft Windows 3.1 Disk #6",disk6

where X= the drive where Windows is installed.

This change should be in place before installation, but can be made after to use with the SELECTIVE INSTALL feature

950131 A:\COUNTRY.SYS IS INCORRECT ON DISK #1 WHEN INSTALLING OS/2 WARP.

DESCRIPTION OF SYMPTOMS

Installing OS/2 WARP, on disk #1 encountered " A:\country.sys is incorrect ".

RESOLUTION

Check the CMOS. If the user has changed the floppy drives around, make sure the CMOS is setup correctly. Example, if the user switch 1.44mb drive from B to A, and 1.2mb drive from A to B, CMOS must be setup and change that reflect the A drive as 1.44mb and B drive as 1.2mb.

Note

Some floppy drives controller has the ability to override the cmos. This means that the card is set for the original setup. For example, if the card is setup for 5 1/4" as A: drive and the user switched the 3 1/2" drive to become A: drive and go into the cmos and change it, when bootup, the card will override the setup on the cmos and still make the 5 1/4" as A:. Advice user to check the controller manual to disable this option on the card. Or refer him/her back to where they bought the controller card.

Update
01/17/1995

Keywords: country sys warp install a:\country.sys country.sys

950202 IPE ## 1000 : 00000DBB - 0002 : 0DBB 60000, 2008 INTERNAL REVISION 8.162 AFTER THE SECOND PHASE OF INSTALLATION OF WARP

SYMPTOMS

IPE after the second phase of the installation of WARP.

   *************** IPE 16/32-bit ***************
    THE SYSTEM DETECTED AN INTERNAL PROCESSING
    ERROR AT LOCATION # 1000:00000dbb - 0002:0dbb
    60000, 2008
    048600b4
    INTERNAL REVISION  8.162      94/09/19
   *********** end IPE 16/32-bit ***************
RESOLUTION

A couple of issues user needs to take a look at.

1. On the root directory, there are many files (excess of 200 plus files) that can cause this IPE. User's needs to move these files to a temporary directory. Check the WARP user's manual on setting up dualboot for more information. Under dualboot setup, it is suggested to move files from the root that are not needed before installation of OS/2.

2. On some Thinkpad systems, on the 2nd phase of installation, user has changed the mouse pointer instead of choosing default. User needs to leave it as default. To correct this problem, use the alt+f1 routine and choose M to the maintenance desktop and make sure the mouse pointer is set correctly for the Thinkpad. Usually, it is set for default.

950203 THREE IDE 563 PANASONIC CDROM DRIVES WORKING UNDER OS/2 WARP

SYMPTOMS
Multiple cdroms connected to the same IDE adapter (SB16 card) are not recognize.
RESOLUTION
Creative Labs has a new driver on their BBS called CD_OS2.EXE.

BBS number is (405) 742-6660. Contact Creative Labs for more information. Note that at this point, multiple 563 Panasonic IDE CDROM drives are not supported.

950203 FAILURE TO RECOGNIZE IDE CD-ROM DRIVE

USERS

All users of PCs with IDE CD-ROM drives

DESCRIPTION OF SYMPTOMS

Failure to recognize CD-ROM drive.

Installing or booting OS/2 Warp on a system with an IDE CD-ROM drive, a red screen appears as the system is initializing the OS2CDROM.DMD device manager. During installation, device managers are initialized during the processing of Disk 1. The message indicates that there is no CD-ROM drive support.

SUMMARY OF RESOLUTION

If an IDE CD-ROM drive and an IDE hard drive share a disk controller, then the user should ensure that the hard drive is configured as the master and the CD-ROM drive is configured as the slave.

    • BUT** If the CD-ROM drive and the hard drive are on separate disk controllers, then the user should ensure that both drives are configured as masters.
DETAILS OF RESOLUTION

Any pair of IDE drives that shares a controller should be setup in a master-slave configuration. There must, however, be one master per controller in order for the drive on that bus to be recognized. These rules apply for any operating system, but they have only begun to cause CD-ROM problems for OS/2 as of the Warp release, the first release to include IDE CD-ROM drive support.

For example, if the system has an IDE CD-ROM drive on its PCI bus and an IDE hard drive on its ISA bus, then both the CD-ROM drive and the hard drive should be configured as masters. If the CD-ROM drive is swapped to the ISA bus at a later date, so that it shares a disk controller with the IDE hard drive, then the user must reconfigure the CD-ROM drive as a slave.

Note that any such combination of drives requires both the IBMIDECD.FLT device driver and the IBM1S506.ADD device driver. If two disk controllers are present, the BASEDEV= statement for the IBM1S506.ADD driver needs the parameter /A:0 to indicate the primary controller or /A:1 to indicate the secondary controller. For more information about these and other parameters, enter...

HELP IBM1S506.ADD

...or...

HELP IBMIDECD.FLT

...at an OS/2 command line.

The user should refer to their hardware's documentation or call the manufacturer's tech support line to find out how to reconfigure their drive as a master or slave.

Note: If the user is able to install OS/2 from the CD-ROM drive, then the drive is configured correctly. Therefore, if the CD-ROM drive is not recognized when OS/2 is booted later, then the user may need to simply add the statement...

BASEDEV=x:\OS2\BOOT\IBMIDECD.FLT

...to the CONFIG.SYS file.

950206 PS/2 9595 PENTIUM WITH 64MB RAM AND DISK ARRAY UNDER WARP

SYMPTOMS

The DISK ARRAY is at level 5 with 6-2gb SCSI drives. Partitioned the drive C: 150mb and the rest as logical 10gb drive. Under OS/2 WARP, tried to format the logical partition, it reports only 3mb is available. Then FDISK reports the partition is unformatted.

Note: This is after user formatted the logical drive which is suppose to be 10gb.

RESOLUTION

User needs to upgrade the system Flash ROM and System BIOS level.

Call IBM PC HELP at 919/517/1080 for more information.

Suggested download the following files/images from IBM BBS at 919/517/0001:

1. RF90954A.DSK
2. RD9095A.DSK
3. LDF.COM
4. RAID162A.DSK
5. NEWRAID.DSK (newer IBMRAID.ADD)