Specialty Forums
Security and Virus
General Hardware
CPUs/Overclocking
Networking
Digital Photo/Video
Office Software
PC Gaming
Console Gaming
Programming
Database
Web Development
Digital Home

General Forums
Windows XP
Windows Vista
Windows 95/98
Windows Me
Windows NT
Windows 2000
Win Server 2008
Win Server 2003
Windows 3.1
Linux
PDAs
BeOS
Novell Netware
OpenVMS
Solaris
Disk Op. System
Unix
Mac
OS/2

Drivers
Driver Scan
Driver Forum

Software
Automatic Updates

BIOS Updates

My Computing.Net

Solution Center

Free IT eBook

Howtos

Site Search

Message Find

RSS Feeds

Install Guides

Data Recovery

About

Home
Reply to Message Icon Go to Main Page Icon

Newly installed Warp3 crashes!

Original Message
Name: Tommy in Scotland
Date: February 13, 2004 at 15:05:49 Pacific
Subject: Newly installed Warp3 crashes!
OS: OS/2 Warp 3.0
CPU/Ram: Pentium-S 166 MHz/ 24MB R
Comment:
I have just installed Warp 3 onto a Pentium 166MHz system. The problem is that when I try to close a OS/2 Command Prompt window or parent window, the system crashes with the message "There was an internal processing error". There is no advice to the user about how to repair the setup, only some glib rubbish about contacting the suppliers. I have not got to the stage of installing any software onto it yet. If I open up the window containing the command prompts, all goes well until I try to close it. Then the desktop disappears to leave a "black screen of death" full of cryptic address codes and useless junk. I originally selected the wrong video driver during installation but I have been through the Alt F1 process during boot-up and changed it. However, it does not seem to have sorted it. Before I reset my video driver I was getting a DOS error... it said "DOS cannot start". Now DOS starts but OS/2 crashes. Should I format and reinstall? Or is there a way to sort this?

Tommy.


Report Offensive Message For Removal


Response Number 1
Name: Hmmm
Date: February 13, 2004 at 20:18:27 Pacific
Subject: Newly installed Warp3 crashes!
Reply: (edit)
Have look in the bios and see if there is secondary cache. Disable it and try again.

Report Offensive Follow Up For Removal

Response Number 2
Name: Sjoerd Visser
Date: February 14, 2004 at 02:55:21 Pacific
Subject: Newly installed Warp3 crashes!
Reply: (edit)
Black screens with programmers info mostly point to buggy drivers, hardware or memory conflicts (dma,irq,io ports):

TRAP 000d ERRCD=0000 ERACC=**** ERLIM=********
EAX=00000000 EBX=ffe30000 ECX=0000000f EDX=00000000
ESI=00007b29 EDI=ffe1cb29 EBP=00004eea FLG=00203246
etc

The IBM Warp 3 COM drivers can be responsible. Applying a fixpack would help. If you don't need them, you can REM them.

Many traps were caused bij buggy videodrivers. If the problem does not occur using the IBM VGA driver (Alt-F1 boot, choose VGA) this could be the case.

Then you have two options: find a better driver or again apply Warp 3 fixpacks, because they can fix third party driver problems to (of cause not all crap).

When changing 3rd party videodrivers it's wise to reboot using VGA first.

For fixpacks I use SimplyFix http://hobbes.nmsu.edu/pub/os2/system/patches/fixpack/sfix41.zip

Fixpacks are on:
ftp://service.boulder.ibm.com/ps/products/os2/fixes/v3.0warp/

You can burn them on CD and using the SimplyFix Wizard and apply them from there.


Report Offensive Follow Up For Removal




Use following form to reply to current message:

   Name: From My Computing.Net Settings
 E-Mail: From My Computing.Net Settings

Subject: Newly installed Warp3 crashes!

Comments:

 
  Homepage URL (*): 
Homepage Title (*): 
         Image URL: 
 


Data Recovery Software




how to setup call of duty to joytok

WindowsME / HotMail Problem

Corrupt memory

Convert fat32 to Ntfs

Best WinMo phone of 2008


The information on Computing.Net is the opinions of its users. Such opinions may not be accurate and they are to be used at your own risk. Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE

All content ©1996-2007 Computing.Net, LLC