I unsuccessfully tried to install fixpack 15 on OS/2 Warp «Canadian
French».
With DSKXTRCT V1.2, I converted the diskette images in a tree whose
root FIX was stored in F:\MISAJOUR,

I used the FSERVICE Correction Service Facility from CSF144.EXE.

Here is the RESPONSE.WP4:
*
* :LOGFILE \OS2\INSTALL\SERVICE.LOG
* :FLAGS REPLACE_PROTECTED REPLACE_NEWER
:FLAGS REPLACE_PROTECTED
* :SOURCE A:\
:SERVICE
:SYSLEVEL \OS2\INSTALL\SYSLEVEL.OS2
:ARCHIVE \ARCHIVE
*

From the F:\MISAJOUR\Outils directory, I launched FSERVICE with the
following command

fservice /r:response.wp4 /s:f:\misajour


FSERVICE stops displaying the message «Erreur fatale lors des
modifications». «Fatal error during modifications» Pressing «Enter»
causes a display of the log. The only way to exit is pressing
Ctrl+Break!

Here is an excerpt from the log:

Lancement des modifications le 2004-12-11 à 21:44:22.
REPLACE_PROTECTED set
Répertoires par défaut utilisés : F:\OS2\INSTALL\SYSLEVEL.OS2
F:\
F:\OS2
....
F:\LANGUAGE\LOCALE
Le produit Système d'exploitation de base OS/2 IBM
(F:\OS2\INSTALL\SYSLEVEL.OS2) va passer du niveau XRC4000_ au niveau
XRCM015_.
Archivage de F:\OS2\INSTALL\SYSLEVEL.OS2.
....
Archivage de F:\OS2LDR.
L'archivage a abouti.
Mise à jour des produits suivants :
F:\OS2\INSTALL\SYSLEVEL.OS2

The archiving was done OK but no updating was done. Why did FSERVICE
stop there?


Several times, I attempted to relaunch FSERVICE: it «remembers» it was
launched before and it does not go any further. What files should I
delete to start anew?

The documentation says that once you use the CSF144, you cannot use an
earlier version...
Should I reinstall OS/2 again and use CSF143?

Did I do something wrong or is there a FSERVICE bug?

Thank you very much for your help.
--
Jean Castonguay
Électrocommande Pascal

On Mon, 13 Dec 2004 13:26:58 UTC "Jean Castonguay"
<jcastong@riq.qc.ca> wrote:

Since you already have the fix pack unpacked onto the hard drive, you
will probably get more meaningful information by running SERVICE.EXE
rather than FSERVICE. Service does an online interactive installation
where Fservice is intended more for unattended installs. The use
service, open a commandline session and change to the directory where
Service.exe is located. Enter "set csfcdromdir=<the directory where
the FIX tree is located> then run service. In your example, that would
be "set csfcdromdir=F:\MISAJOUR" - not the complete path spec.

--
Will Honea

On Tue, 14 Dec 2004 02:20:39 UTC, "Will Honea" <whonea@yahoo.com>
wrote:


It finally worked when I used the CSFDRIVEAPPLY environment variable!

Using SERVICE instead of FSERVICE helped me find the problem. It was
not immediate though!
--
Jean Castonguay
Électrocommande Pascal

On Tue, 14 Dec 2004 18:21:22 UTC "Jean Castonguay"
<jcastong@riq.qc.ca> wrote:

Interesting. I don't think I've seen any reference to CSFDRIVEAPPLY -
maybe a difference in the nls since I only work with us_en. Or it
could be that I simply quit looking when I found a working solution
several years ago. I am a great believer in the "if it ain't broke,
don't fix it" philosophy. <g>

Glad I could help a littel.

--
Will Honea

In <IbxCuxQzw2Ms-pn2-48kSK7gyvkjd@localhost>, on 12/13/2004
at 01:26 PM, "Jean Castonguay" <jcastong@riq.qc.ca> said:

I generally recommend supplying a drive letter with :SYSLEVEL and
:LOGFILE.

Otherwise, fservice will attempt to service all partitions where it finds
a syslevel.os2 file and this usually produces unexpected results.

Using CSFDRIVEAPPLY as you did effectively does the same thing as
supplying at drive letter.

HTH,

Steven


--
--------------------------------------------------------------------------------------------
Steven Levine <steve53@earthlink.bogus.net> MR2/ICE 2.60b #10183
Warp4/FP15/14.100c_W4 www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST)
--------------------------------------------------------------------------------------------