os/2 warp 3 install - it works, but.
Rick
first impressions are good.
I have a problem, it started ok then I found out it didn't recognise the
cd-rom.
So I went into system install and set it as non-listed IDE CD-ROM.
Rebooted.
Then i got :-
Trap 0003
System detected an internal processing error at location:-
##160:fff5c34c
-000d:a34c.
6000, 9084
048600b4
Internal Revision 8.162, 94/09/19
System is stopped. Record all of the above info and contact service rep.
If I take the cd-rom out of the bay and put a floppy drive in the bay the
computer starts ok. (Actually the config.sys errors it comes up with I can
live with.)
I was wondering if ##160 is the cd-rom memory location, cause when it had
dos7.1 the memory location was#170 for the cd. If so how do I force it to
use #170?
I keyed in help 1933 and got sys1933 a program caused a breakpoint error.
The program was ended.
So I am beginning to suspect a driver error?
Anyone any ideas?
The computer is an Ibm Thinkpad 600 2645-510 and on the web site there is a
set of Warp 4 drivers (but not for the cd) and I wondered if anyone knows if
they will work for Warp 4.
Also anyone know where i can get a (cheap) copy of Warp 4?
Thanks to everyone for their help.
Rick
Trevor Hemsley
<richard.c...@ntlworld.com> wrote:
> It works ok - i just need to get used to it. I've never used os/2 before but
> first impressions are good.
>
> I have a problem, it started ok then I found out it didn't recognise the
> cd-rom.
> So I went into system install and set it as non-listed IDE CD-ROM.
> Rebooted.
>
> Then i got :-
>
> Trap 0003
Warp 3 is now *very* old. Warp 4 came out in 1996 and replaced Warp 3 which came
out in 94 so you're working with something that's 14 years old. If you have just
installed it without doing anything else to it then you won't have any of the
fixes for it at all. Best thing you casn do is to download fixpack 40 from
ftp://ftp.boulder.ibm.com/ps/products/os2/fixes/v3.0warp/english-us/xr_w040 and
put that one using the fixtool which is downloadable from the same ftp site in
/ps/products/os2/fixtool/english-us.
The TRAP 003 you have now when trying to access a CD drive is a known problem
and the solution will be in the fixpack.
--
Trevor Hemsley, Brighton, UK
Trevor dot Hemsley at ntlworld dot com
Rick
everything?
Thanks
Rick
"Trevor Hemsley" <Trevor....@mytrousers.ntlworld.com> wrote in message
news:dLBdR0eR1GujTP...@trevor2.dsl.pipex.com...
Trevor Hemsley
<richard.c...@ntlworld.com> wrote:
> How do I find out what to do with that lot & do I have to download
Start by downloading the readme.1st file which has pretty good instructions in
it. And you'll want all the *.*dk files from the fixpack directory and the
fixtools stuff too.
Actually, thinking about it, it's a lot easier to download the zipped versions
of the files from /ps/products/os2/rsu/xr_w040 and get the csf143.zip file from
the same place too. Still grab the readme.1st file from the other directory as
it tells you more about the fixpack itself. Unzip all the xr_w040*.zip files
into a single subdirectory on your hard disk and the csf143.zip file into a
different one. Open an OS/2 command prompt and cd to the directory you put the
csf files into and type
SET CSFCDROMDIR=x:\fp40
where x:\fp40 is the full directory name of the place where you unzipped the
xr_w040*.zip files. Then run service.exe from the same command prompt and it
should guide you through putting the fixpack on. It'll tell you that it can't
continue because of locked files but there is an option there to do so anyway
and update them after a reboot - take that.
Read all the readme files you can find - fixpack and CSF too. Don't just rely on
my instructions because I'm doing this from memory and I haven't needed to do
this for years!
Dave Yeo
[...]
> Also anyone know where i can get a (cheap) copy of Warp 4?
>
> Thanks to everyone for their help.
>
> Rick
There is a copy here,
http://www.vetusware.com/download/OS/2%20Warp%204/?id=3429. I haven't
actually DLed this and there is a chance that it is a floppy based
install in which case there will be a hell of a lot of floppies.
Dave
Trevor Hemsley
I grabbed it and it is diskette images :-( About 50 of them. Would take forever
to install.
Jack Wise
> On Sat, 15 Mar 2008 18:57:44 UTC in comp.os.os2.setup.misc, Dave Yeo
> <dave....@gmail.com> wrote:
>
>
>>On 03/15/08 04:37 am, Rick wrote:
>>[...]
>>
>>>Also anyone know where i can get a (cheap) copy of Warp 4?
>>>
>>>Thanks to everyone for their help.
>>>
>>>Rick
>>
>>There is a copy here,
>>http://www.vetusware.com/download/OS/2%20Warp%204/?id=3429. I haven't
>>actually DLed this and there is a chance that it is a floppy based
>>install in which case there will be a hell of a lot of floppies.
>
>
> I grabbed it and it is diskette images :-( About 50 of them. Would take forever
> to install.
>
Not Forever! I have done several floppy installations over the years
where the PC did not have a CD as part of the configuration.
You need to allow about 5 hours
--
Jack Wise
Secretary, Oak Wood Lodge No. 1444, AF & AM, The Woodlands, TX
(www.txmason.com) ( Lodge E-Mail: oakwo...@hal-pc.org )
PM, Jacques DeMolay Lodge No. 1390, AF & AM, Houston, TX
( www.jd1390.org/jdmlodge.htm )
TEXAS red wine: renowned for its smoky-mesquite-bbq & jalapeno
overtones, the perfect foil for a meal of tacos and refried beans...
Trevor Hemsley
<jw...@hal-pc.org> wrote:
> I have done several floppy installations over the years
> where the PC did not have a CD as part of the configuration.
>
> You need to allow about 5 hours
I think that would be a massive underestimate - are you including the time it
takes to create the 50 diskettes in that? And to throw out the diskettes that
fail half way through the install and make you restart the install from scratch?
Alex Taylor
> >>http://www.vetusware.com/download/OS/2%20Warp%204/?id=3429. I haven't
> >>actually DLed this and there is a chance that it is a floppy based
> >>install in which case there will be a hell of a lot of floppies.
> >
> > I grabbed it and it is diskette images :-( About 50 of them. Would take
> > forever to install.
>
> Not Forever! I have done several floppy installations over the years
> where the PC did not have a CD as part of the configuration.
>
> You need to allow about 5 hours
Don't EVER do a floppy-based install of a FixPak. Unless you are a
masochist, of course. You are just asking for pain and frustration.
The floppy-based FixPak routine was designed back in the day when most
computers didn't even have CD-ROM drives.
--
Alex Taylor
Fukushima, Japan
http://www.cs-club.org/~alex
Please take off hat when replying.
Trevor Hemsley
<mai...@reply.to.address> wrote:
> Don't EVER do a floppy-based install of a FixPak. Unless you are a
> masochist, of course. You are just asking for pain and frustration.
And this is complete install from diskette!
Alex Taylor
wrote:
> > Best thing you casn do is to download fixpack 40
>
> How do I find out what to do with that lot & do I have to download
> everything?
There are several ways to install a FixPak. Normally, I'd direct you to my
website, which has all the information and links (including web-based
FixPak installation) that you should need.
Unfortunately, my website is down at the moment while my hosting provider
moves everything to a new server (and a new domain). So I'll paste the some
of the information here.
--------------------------------------------------------------------------
How to install a FixPak
There are many different ways to install a FixPak. Unfortunately, the
documentation IBM provides with their OS/2 FixPaks only describes one of these
in detail, and it just happens to be the most painful and error-prone method
possible: installing from diskettes.
It is not necessary to create diskettes to install a FixPak. In fact, you
SHOULD NOT install a FixPak this way except as an absolute last (desperate)
resort. Just one bad sector on one diskette has the potential to cause file
corruption, and considering the generally poor quality of modern floppies, this
is not an idle threat.
The diskette method of FixPak installation is more than ten years old, and was
designed for an era when most systems didn't even have CD-ROM drives. There are
better, faster and more reliable methods available to us now.
The three most common ways of installing a FixPak are:
* Manually, from a hard disk, CD, or LAN drive.
* Using a web browser and the Remote Software Updates facility to install
over the Internet (or other TCP/IP network).
* Using a Software Distribution Manager to perform "push" installations over
a local network.
The first two methods are described below. The third method requires
specialized software, and is not covered here.
Installing manually
To install a FixPak manually, you need three things. First of all, you need the
FixPak files themselves. IBM typically provides these in the form of binary
diskette images, so you'll also need some way to extract them. The recommended
tool for doing this is with the DSKXTRCT utility, which is available on Hobbes:
http://hobbes.nmsu.edu/pub/os2/system/patches/fixpack/dskxtr13.zip
Finally, you need the Corrective Service Facility (CSF), which is the program
that's actually used to install the FixPak. IBM usually includes a copy of the
CSF with each FixPak, but for various reasons, you should download the latest
version from the RSU FTP site:
ftp://ftp.software.ibm.com/ps/products/os2/rsu/csf144.zip
Place DSKXTRCT.EXE somewhere into your system PATH. Unzip CSF144.ZIP into a
directory on your hard disk. This will place three or four files into that
directory, and create a subdirectory called CSF containing many other files.
Next, use DSKXTRCT to unpack the FixPak diskette images. The syntax is:
DSKXTRCT /S:<name of image file(s)> /T:<target directory>
Make sure you unpack all of the diskette images into the same target directory.
Once this is done, you can start the FixPak installation by going to the
directory where you unzipped CSF144.ZIP, and entering the command:
OS2SERV <path to CSF directory> <path to FixPak directory>
(You must specify the paths in fully-qualified form.) This will give you a
guided (GUI) installation, which is fairly easy to follow.
Using Remote Software Updates
Remote Software Updates (RSU) is a special tool which allows FixPaks to be
installed over the Internet using a web browser. Instructions and a set of
links for installing various FixPaks are available -------------.
[Site is down at the moment, if you want I can try and get a temporary
version put up - or maybe my files will be back on-line in a couple of days.]
Committing or backing out a FixPak
Backing out a FixPak means uninstalling it and restoring the system to its
previous (pre-FixPak) state. Depending on which FixPaks have been installed,
you may be able to back out to the Backup level (the system state before the
last FixPak was installed), or the Archive level (the system state before any
FixPaks were installed). Note that not all FixPaks support archiving, so in
some cases only the Backup level may be available.
'Committing' a FixPak means cleaning up the Archive and Backup files so that
you can no longer back it out. Committing is not mandatory, but it can free up
some disk space.
The easiest way to commit or back out a FixPak is using a GUI program called
SERVICE.EXE, which is part of the CSF. This program is located in the CSF
directory (under the path where you unzipped CSF144.ZIP).
To use this program, you must first issue the command:
SET CSFCDROMDIR=<path>
where <path> is the fully-qualified path to a FixPak's installation files. (It
doesn't matter which FixPak, as long as it's a valid one for the version of
OS/2 you are running, because you won't actually be installing it. This is just
a workaround to prevent SERVICE.EXE from demanding floppy diskettes. I
recommend pointing it to the FixPak which you're about to commit or back out,
assuming you still have the files available.)
Then go into the CSF directory where SERVICE.EXE resides, and run the command:
SERVICE
From the graphical interface that comes up, select the button 'Change product
list'.
* To commit a previously installed FixPak, choose 'Uncommitted products'.
Select the FixPak(s) that you want to commit, and click on 'Commit'.
* To back out a previously installed FixPak, choose either 'Archived
products' (to back out to the Archive level of a product) or 'Backed up
products' (to back out to the Backup level of a product). Select the
FixPak(s) that you want to back out, and click on 'Backout'.
Once you've committed or backed out a FixPak, you can go and delete that
FixPak's saved files from wherever they were saved, typically under \ARCHIVE or
\BACKUP. (In some cases, SERVICE.EXE will do this for you; generally, files
under \BACKUP will be cleaned up automatically, but files under \ARCHIVE will
not.)
--------------------------------------------------------------------------
Kelbel
Excuse me to jump in this discussion with -maybe- a *very* basic
question, not related to Warp3..
Can I install OS/2 MCP (V4.52) on a 64bits machine? Is there a patch or
the like to achieve this (so far no success) or is it a definite
'no-go' ?
The PC hardware is as follows:
Motherboard:
CPU Type AMD Athlon 64, 2400 MHz (12 x 200)
3800+
Motherboard Name MSI K8N Neo4 Series (MS-7125)
(4 PCI, 1 PCI-E x1, 1 PCI-E x4, 1
PCI-E x16,
4 DDR DIMM, Audio, Gigabit LAN)
Motherboard Chipset nVIDIA nForce4, AMD Hammer
System Memory 2048 MB (PC3200 DDR SDRAM)
BIOS Type Award (07/21/06)
Communication Port Communications Port (COM1)
Communication Port Printer Port (LPT1)
Display:
Video Adapter NVIDIA GeForce 8400 GS (512 MB)
Monitor IBM 2128 MM75 Multimedia [17" CRT]
(55-49065)
Multimedia:
Audio Adapter nVIDIA MCP04 - Audio Codec Interface
Storage:
IDE Controller Standard Dual Channel PCI IDE
Controller
Floppy Drive Floppy disk drive
Disk Drive Hitachi HDS721680PLAT80 (74 GB, IDE)
Optical Drive CREATIVE DVD-ROM DVD5240E (5x/32x
DVD-ROM)
SMART Hard Disks Status OK
Thks for info
K.
Rick
I am new to os/2 but from what i remember of what i've read os/2 will not
work on a 64 bit machine. The only one that will work is eCom.
Rick
"Kelbel" <Kelbel...@free.fr> wrote in message
news:47dd591c$0$892$ba4a...@news.orange.fr...
Jack Wise
> On Sat, 15 Mar 2008 22:43:20 UTC in comp.os.os2.setup.misc, Jack Wise
> <jw...@hal-pc.org> wrote:
>
>
>>I have done several floppy installations over the years
>>where the PC did not have a CD as part of the configuration.
>>
>>You need to allow about 5 hours
>
>
> I think that would be a massive underestimate - are you including the time it
> takes to create the 50 diskettes in that? And to throw out the diskettes that
> fail half way through the install and make you restart the install from scratch?
>
I did not have that many problems. I know that I have had to do it at
least 6 times. (For 6 different clients at different locations at
different times - otherwise I would have used the same diskettes each
time.)
I did have a previously installed laptop available, so that I was
creating diskettes on the laptop and installing the system on the
desktop machine at the same time. I would get an 'headstart' by making
the first 4 or five diskettes before starting the installation.
If I recall correctly, on the rare occasion that I did create a bad
diskette, I was able to interrupt the create diskette routine and
restart the create diskette program and skip creating the 'OK' diskettes
and resume with creating the bad diskette.
In my case, if a diskette was bad, the installation would not abort, but
simply prompt me for the proper diskette in order to continue.
Alex Taylor
wrote:
> > > Best thing you casn do is to download fixpack 40
> >
> > How do I find out what to do with that lot & do I have to download
> > everything?
>
> There are several ways to install a FixPak. Normally, I'd direct you to my
> website, which has all the information and links (including web-based
> FixPak installation) that you should need.
>
> Unfortunately, my website is down at the moment while my hosting provider
> moves everything to a new server (and a new domain).
OK, my site's back up (mostly) at its new address:
http://www.socis.ca/~ataylo00/os2/fixpaks/index.html
William L. Hartzell
Kelbel wrote:
> Hi,
> Excuse me to jump in this discussion with -maybe- a *very* basic
> question, not related to Warp3..
>
> Can I install OS/2 MCP (V4.52) on a 64bits machine? Is there a patch or
> the like to achieve this (so far no success) or is it a definite
> 'no-go' ?
<snip>
You'll have to replace the kernel that is on the CD with a newer one.
Use the make installation disks process, replace the kernel with 14.103
or later <http://os2site.com/sw/upgrades/kernel/uni20050317.zip> and use
the same copyfromfloppy command that was recommended up thread to Rick
for updated install diskettes. While you are at it, you'll need updated
IDE drivers for newer hardware. The latest Dani drivers can be had from
Hobbes
<http://hobbes.nmsu.edu/pub/os2/system/drivers/storage/danis506r182.zip>.
--
Bill
Thanks a Million!
Dave Yeo
Will the newer kernels work on Warp v4? I was under the impression that
they need v4.5 (fixpak 13+). Of course he would also need the
corresponding os2ldr.
I'd think the simplest would be to install on an old box then move the
HD or clone it.
Dave
Kelbel
Mr. Hartzell
OK thanks for this information (I do have 14.103 krnl & danis506r182 on
another box here..)
K.
Mike Luther
Beginning with Dani's 181 revision level releases, you will also have to move
to her ATAPI driver use as well. And per what I found out the hard way which
produces lockup errors for me, you cannot just rename the DaniS506.ADD driver
to the IBM1S506.ADD device driver like you could do up until the 181 release. I
didn't understand this and got caught in this loop with the arrival of the 181
level code.
--
--> Sleep well; OS2's still awake! ;)
Mike Luther
Kelbel
not having the correct version of the Atapi driver.
However, install does not work.. I have a red screen stating that
Sysinst2.exe did not return the correct drive letter (or the like)
It seems there is a failure in the DOSCALL1 (I tried sysinst2.exe direct
from the cdrom & this is the msg I got). Installation stopped.
My Doscall1.dll is 137445 bytes, dates back 2001-10-29.. maybe there is
an update which I'm missing..
K.
William L. Hartzell
After you get to the first screen, there is down at the bottom an option
to use F3 to get a command prompt. Get and install Dfsee onto an
utility disk (a forth floppy as you will) and take the F3 option. Run
Dfsee and see what it tells you. You may have a too large a disk for
the os2dasd driver. Herbert published yesterday the limits that affect
the various versions.
<http://hobbes.nmsu.edu/pub/os2/util/disk/dfsee907.zip>
Mike Luther
From MCP2 Fix Pack XRC05:
12-29-04 11:15a 137601 0 DOSCALL1.DLL
I haven't looked to make sure, but I think that this is also the one on the
'latest' MCP2 CD install. The installation CD disks were changed a number of
times, per my understanding, right up until the time that the marketing of OS/2
was changed at IBM. No .. that doesn't mean that the whole install is up to
what the XRC05 level is, but particularly in respect to what code would have
changed for what was in the install as well as what would be in the floppy
diskettes that were to by synchronized for an install did change with the later
releases as I think I recall.
I wonder about something else here. In the case of the utility diskettes and
the install floppy diskettes, can you actually use Dani's latest tools complete
with a full needed renamed driver for DaniS506.ADD as well as DaniATAPI as
well? I have had jams when trying to do this with floppy diskettes which were
'modified' to use the DaniS506.ADD which was put on them in that named form for
use with her version 181 and 182 code. In my case, the latest version of here
DaniS506.ADD which I can use is the last release of the 1.7.10 code level which
was still able to be renamed to the IBM1S506.ADD name style for use with the
floppy disks.
For that reason I've been very careful to keep a copy of that level of the code
here as to my understanding it isn't left on the download sources for her work.
That's been my solution to this issue, but in my case, her code works for the
floppy disk use for whatever hardware I still have and work with.
Just thinking here. I may be missing something here and would be glad to learn
more about things, I assure everyone.
Trevor Hemsley
<Kelbel...@free.fr> wrote:
> I have a red screen stating that
> Sysinst2.exe did not return the correct drive letter (or the like)
Boot from the CD and you get an option to go to a command prompt. On one of the
disk image directories there is a copy of chkdsk - run chkdsk /f against your
drives. Then try again.
Kelbel
> On Tue, 18 Mar 2008 09:57:14 UTC in comp.os.os2.setup.misc, Kelbel
> <Kelbel...@free.fr> wrote:
>
>
>>I have a red screen stating that
>>Sysinst2.exe did not return the correct drive letter (or the like)
>
>
> Boot from the CD and you get an option to go to a command prompt. On one of the
> disk image directories there is a copy of chkdsk - run chkdsk /f against your
> drives. Then try again.
>
drive" appears before I select on which partition/volume the
installation is to take place..
Msg is SYS0202: the op system can not run sysints2->doscalls
The physical disk is 80GB. I think os2dasd can take care of that size.
Ram is 2GB (might be a problem). I give up installation as such & will
try cloning an existing OS/2 on that 80GB drive.
K.
Mike Luther
Kelbel wrote:
> No way. the error screen with "sysinst2.exe failed to return the target
> drive" appears before I select on which partition/volume the
> installation is to take place..
> Msg is SYS0202: the op system can not run sysints2->doscalls
> The physical disk is 80GB. I think os2dasd can take care of that size.
> Ram is 2GB (might be a problem). I give up installation as such & will
> try cloning an existing OS/2 on that 80GB drive.
>
> K.
I seem to recall that there is a memory size issue for a lot of this which gets
in trouble at either over 512MB or over 1GB. Can you remove all but 512MB and
try this?
Trevor Hemsley
<Kelbel...@free.fr> wrote:
> No way. the error screen with "sysinst2.exe failed to return the target
> drive" appears before I select on which partition/volume the
> installation is to take place..
I am pretty sure that there is an option to F3 to a command prompt before you
get to that point.
Kelbel
> On Tue, 18 Mar 2008 18:43:19 UTC in comp.os.os2.setup.misc, Kelbel
> <Kelbel...@free.fr> wrote:
>
>
>>No way. the error screen with "sysinst2.exe failed to return the target
>>drive" appears before I select on which partition/volume the
>>installation is to take place..
>
>
> I am pretty sure that there is an option to F3 to a command prompt before you
> get to that point.
>
Yes indeed, there is this F3 option at the blue welcome screen, right
after the 3 diskettes are read. From this command prompt I can access
the cd drive and run chkdsk. However I meant that chkdsk can only
check.. the cdrom. At that time, the disk contains only NTFS partitions.
chkdsk does not know ntfs.
K.
Kelbel
Ok, I'll try that.
K.
William L. Hartzell
I'd believe that this *magic* in excess of 512 MiB memory size was a bug
in early releases of P4 that Scott fixed with a new release of the
OS2loader. However, the error was not the same as he is getting.
Herbert Rosenau
<richard.c...@ntlworld.com> wrote:
> You might have been better to start a new thread.
> I am new to os/2 but from what i remember of what i've read os/2 will not
> work on a 64 bit machine. The only one that will work is eCom.
This is not true. You must install on a 32 bit mainboard at all. Then
move the harddisk onto an 64 bit mainboard and boot up.
True is that installing WARP3 and get it halfways up to date (that
means 1996!) will cost you more than a day to complet only the basic
system with subsystems like tcp/ip.
Installing WARP4 is done some hours quickly but anyway you entds up
with a system that is out of date more than 1/2 decade.
In both cases you ends up with some missing functionality like NO
respective limited USB support.
MCP is not capable to install on 64 bit - and eCS before 1.2R too.
As ownee of a valid CS 1.2 license you can download eCS 1.2R for free.
As 1.2R was released to upgrade something in the OS loader and kernel
and other programs and libraries who had no idea of how to handle the
differences between 32 bit BIOS and 64 bit BIOS to get the installer
working.
--
Tschau/Bye
Herbert
Visit http://www.ecomstation.de the home of german eComStation
eComStation 1.2R Deutsch ist da!
Kelbel
Install of OS/2-V4.52 achieved.. by cloning an exisiting os2 partition
(from another disk) on the 64Bits machine.. I followed in fact what is
mentionned in the article:
http://www.os2voice.org/vnl/past_issues/VNL0403H/vnewsf5.htm
Failure for a fresh install (after kernel & drivers updates, as
recommended erarlier) was that I completely missed the LVMing of the new
80G disk..
K.