On Fri, 01 Oct 2004 01:25:47 -0400, Bennett B. Gaston wrote:

kl>Well, I took your advice and sent Peter Weilbacher a quick note.  After a
kl>couple of reply emails, he found the cause of my troubles.  The Innotek
kl>file libc-0.5.1.exe actually contains an installer, a copy of libc05.dll,
kl>and a copy of gcc322.dll!  If you run the file manually, instead using an
kl>archiver to open it (like I did), the built-in installer will extract
kl>libc05.dll and gcc322.dll and place them in your \OS2\DLL subdir.  Hurray,
kl>problem solved!!  Now I can just delete all the other versions of
kl>libc0*.dll and gcc322.dll scattered across my hard drive.


  hi zsolt

please, look carefully on this file:
libc05.dll      356330 04.04.14  16:37

this is "my" version of libc. I think its not from innotek's package.
I think, innotek's is dated by february 2004. I'm not shure!

one thing I know; if I use the febr.edition; I have many trouble on my system.
there I'm using ndfs with
samba. there will be many troubles with febr,2004_file(libc5.dll),
with april.2004(libc5.dll), there are NO troubles.

I was getting in contact with innotek, but no reaction.


sorry, but I can't define, from where or in which package I have found
april_2004(libc5.dll). sorry


yours
klaus

Phil,

Here is the information for both files installed by libc-0.5.1.exe:

02-23-04   3:40p     28718           0  gcc322.dll
04-14-04   4:37p    356330           0  libc05.dll

It's a rather simple installer, and you can specify a different location for it
to put the files.  Hope this helps.

-Bennett

-----Original Message-----
From: Phil Parker <phil@...>
Sent: Oct 1, 2004 1:52 AM
To: updcd@yahoogroups.com
Subject: Re: [updcd] Re: Addons Greyed Out?


On 10/01/2004 at 01:25 AM, "Bennett B. Gaston" <bgaston@...> wrote:

>libc-0.5.1.exe actually contains an installer, a copy of libc05.dll, and a
>copy of gcc322.dll!  If you run the file manually, instead using an archiver
>to open it (like I did), the built-in installer will extract libc05.dll and
>gcc322.dll and place them in your \OS2\DLL subdir.

What is the date/time stamp on that gcc322.dll and what is its exact byte
size? The one I have now is

23:25:06 10/06/03     25721  e:\usr\dll\gcc322.dll

As you may guess, I much prefer to keep such things separate from the boot
drive system tree.

--
     Phil Parker
--------------------------------------------
URL http://www.math.wichita.edu/~pparker/
Random quote:
   Americans detest all lies except lies spoken in public
   or printed lies.---Ed Howe






Yahoo! Groups Links

Hi,

the "April" version you are stating is in libc-0.5.1.exe from the
Innotek website:

http://download.innotek.de/gccos2/runtime/libc-0.5.1.exe

Lars


>  hi zsolt
>
> please, look carefully on this file:
> libc05.dll      356330 04.04.14  16:37
>
> this is "my" version of libc. I think its not from innotek's package.
> I think, innotek's is dated by february 2004. I'm not shure!
>
> one thing I know; if I use the febr.edition; I have many trouble on
my system. there I'm using ndfs with
> samba. there will be many troubles with febr,2004_file(libc5.dll),
> with april.2004(libc5.dll), there are NO troubles.
>
> I was getting in contact with innotek, but no reaction.
>
>
> sorry, but I can't define, from where or in which package I have
found april_2004(libc5.dll). sorry
>
>
> yours
> klaus

Hello Martin,

thanks for your answer. So it looks like tcpcheck.exe and tcpinst.exe
both understand (almost) all parameters understood by the old
install.exe TCPIP installation utility.
Ok, this issue is resolved.

Lars

--- In updcd@yahoogroups.com, "Dr. Martin R. Hadam"
<Hadam.Martin@M...> wrote:
> On Thu, 30 Sep 2004 14:36:05 -0000, barf1234de wrote:
>
>  Hello Lars,
>
>  thank you for your feedback.
>
> >I would really be interested how install.cmd looks like as I am
> >interested how clifi is eventually called.
> >So there seems to be a lot more behind it than just employing feature
> >installer.
>
>  Here it comes:
>
> /*  This file calls the front end to install TCP/IP 4.1 for OS/2 */
>        
>   '@echo off'
>   'setlocal'
>   parse upper arg parms
>   parse source . . procrx .        /* Get  proc names.  */
>   'set beginlibpath=.\;'
>   'set NLSPATH=.\;'
>   exedrive     = FILESPEC("drive",procrx)
>   exepath      = FILESPEC("path",procrx)
>   epath = substr(exepath,1,length(exepath)-1)
>   exedrive
>   'cd 'epath
>   exedrive||exepath||'tcpcheck.EXE' parms
>   exitrc = rc
>   if rc=0 then do
>     exedrive||exepath||'tcpinst.EXE' parms
>     exitrc = rc
>   end
>   'endlocal'
>   Exit exitrc        /* Preserve result contents. */
>
>
>  tcpcheck /? provides all the parameters:
>
> [OS/2] T:\CID\SERVER\TCPAPPS >> tcpcheck /?
> TCP/IP 4.1 for OS/2 Install
> Usage:
> install [/parameters]
> /r:   The fully-qualified filename of the TCP/IP response file.
> /ip:  The internet address of the workstation.
> /nm:  The Subnet mask of the workstation.
> /rt:  The internet address of the default router.
> /h:   The host name of the workstation.
> /t:   The drive to which TCP/IP for OS/2 is to be installed.
> /lp:  The complete path on the code server that contains the MPTS.EXE.
> /lr:  The complete path on the code server that contains the
> LAPSRSP.RSP.
> /tu:  The drive from which your workstation starts; (CONFIG.SYS)
> /srv: Specifies one or more TCP/IP services to be included in
> TCPSTART.CMD.
> /isrv:Specifies one or more TCP/IP services to be included in
> INETD.LST.
> /l1:  The fully-qualified path to write a TCP/IP Install log file.
> /l2:  The fully-qualified path to write a TCP/IP Install log file.
> /c    Causes INSTALL to make configure without installing TCP/IP.
> /a-   Specifies that the install is to be performed on an unattended
> basis.
>
> example:install /r:c:\my.rsp /ip:1.1.1.1 /nm:1.1.1.1 /rt:1.1.1.1
> /h:host /t:d: /
> lp:s:\mpts /lr:s:\mpts\rsp /tu:c /srv:inetd,telnetd /isrv:tftpd
> /l1:d:\my1.log /
> l2:e:\my2.log /c /a-
>
> [OS/2] T:\CID\SERVER\TCPAPPS >>
>
>  Clifi is then called from tcpinst.exe. TCPINST.EXE  itself will not
> reveal any parameters. All you get is a popup "a syntax error has been
> found on the command line - install is terminated"
>
>  Hope this will get you any further.
>
>  Martin
>
>  Martin R. Hadam
>  Kinderklinik - Medizinische Hochschule
>  D-30623 Hannover
>  Germany
>  Email: Hadam.Martin@M...

On 10/01/2004 at 10:59 AM, Bennett Gaston <bgaston@...> wrote:

>Here is the information for both files installed by libc-0.5.1.exe:

>02-23-04   3:40p     28718           0  gcc322.dll
>04-14-04   4:37p    356330           0  libc05.dll

>It's a rather simple installer, and you can specify a different location for
>it to put the files.  Hope this helps.

Yes, thanks.

--
     Phil Parker
--------------------------------------------
URL http://www.math.wichita.edu/~pparker/
Random quote:
   Xerox does it again and again and again and ....

>   Date: Wed, 29 Sep 2004 22:26:28 +0100
>   From: "Dr. Martin R. Hadam" <Hadam.Martin@...>
>
> After the Reboot during MPTS install, entries config.sys are turned
>into  uppercase. Config.MPT and config.EPW are the last ones with
>correct case. While this is no problem with most entries, changing the
>prompt using ANSI sequences is hampered: $e[1;m will turn into $E[1;M
>which leaves an "M" on the beginning of the line. Don't know if there
>is a remedy.

I assume you have installed mpts bundled with tcp/ip 4.21. A newer
version might fix the issue.

>I've tried to install a new printer. While the list is fine during
>install, the printer selection list only features an icon and the
>printer type (pscript, laser,etc) - NO title/description. Selecting an
>entry does indeed work and will even  briefly reveal the name of the
>printed to be installed. However, the printer data are not taken from
>the hard disk (where they should be with an updated install) but from
>the install CDROM. I've noted this with several independent installs; I
>don't think it has to do with Warp3 since printer drivers are the same.
>May there is a pointer going in the wrong direction?

The printer list is in prdesc.lst. The file is located somewhere in
os2\install. Please check the content of it.

> Again due to getting a few errors for image size I've tried to remove
>all stuff that is not needed. As such I noted that the CDROM also
>features Joliet. Is there a specific need for it? Other than that it
>may be needed in an CDROM creation from Windows? I've remove the
>parameter from the lib and noted no problems with the resulting CDROM.

Which parameter did you remove?

Zs

>   Date: Wed, 29 Sep 2004 23:15:54 -0000
>   From: "barf1234de" <lars.erdmann@...>
>
>Still you are right, we should update lcudrvr.fil (in all its
>incarnations like lcudrvr.wp4,lcudrvr.cp etc) to read this way, this
>is true and should work for any version of TCPIP:

If you are sure about it I can replace the parameter.

>(note the additional /a- that will prevent any popup asking for
>whatever install parameters as there are always default values even
>for all parameters that are NOT defined in the RSP file. This is
>necessary as the install dialog window will be hidden behind the
>ISHIELD fullscreen installation window and therefore will NOT be
>accessible ! I have checked with the original Warp4 install Cd-ROM and
>that parameter existed back then).

I believe you are right about TCP/IP 4.0 (Warp 4). But what about older
versions, like 3.0 in Warp Connect? (Warp Server has 3.1).

Zs

>version of Mozilla.  But this still leaves the question of how the runtime
>C-Libraries are handled.  If I rename libc-0.5.1.exe to libc.exe and place
>it in 56_MZILA, will it still require user intervention and thus not be
>automatically installed?  One solution might be to just zip up the new

No, the installation script installs it using the /unattended option,
which means you will not even notice that it has been installed. :-)

Zs

>   Date: Fri, 01 Oct 2004 09:58:00 +0200 (CEST)
>   From: lehmann_klaus@...
>
>please, look carefully on this file:
>libc05.dll      356330 04.04.14  16:37
>
>this is "my" version of libc. I think its not from innotek's package.
>I think, innotek's is dated by february 2004. I'm not shure!

I have just checked the version I have. It is from libc051, and it is
newer, but it has the same size!

02-10-2004  17:55              356.330 libc05.dll

>one thing I know; if I use the febr.edition; I have many trouble on my system.
there I'm using ndfs with
>samba. there will be many troubles with febr,2004_file(libc5.dll),
>with april.2004(libc5.dll), there are NO troubles.

You might want to try libc 0.51.

Zs

On Sat, 02 Oct 2004 17:42:58 +0200, Zsolt Kadar wrote:

>>   Date: Wed, 29 Sep 2004 22:26:28 +0100
>>   From: "Dr. Martin R. Hadam" <Hadam.Martin@...>
>>
>> After the Reboot during MPTS install, entries config.sys are turned
>>into  uppercase. Config.MPT and config.EPW are the last ones with
>>correct case. While this is no problem with most entries, changing the
>>prompt using ANSI sequences is hampered: $e[1;m will turn into $E[1;M
>>which leaves an "M" on the beginning of the line. Don't know if there
>>is a remedy.
>
>I assume you have installed mpts bundled with tcp/ip 4.21. A newer
>version might fix the issue.

  From your wording I assume that this is a "known issue" with that
specific version. Correct? I've noted it after I added my own prompt to
tunecfg.cfg  - but at this point I do not recall if I had moved to
TCPIP 4.21 already or if that was still with v4.1. If NOT a known
problem I'd go back and determine from which version onwards this is
happening.

>>I've tried to install a new printer. While the list is fine during
>>install, the printer selection list only features an icon and the
>>printer type (pscript, laser,etc) - NO title/description. Selecting an
>>entry does indeed work and will even  briefly reveal the name of the
>>printed to be installed. However, the printer data are not taken from
>>the hard disk (where they should be with an updated install) but from
>>the install CDROM. I've noted this with several independent installs; I
>>don't think it has to do with Warp3 since printer drivers are the same.
>>May there is a pointer going in the wrong direction?
>
>The printer list is in prdesc.lst. The file is located somewhere in
>os2\install. Please check the content of it.

  I've checked several installs: all have a "Printer: " preceding every
single line in prdesc.lst. Once removed with an editor, all is fine
with the display. Haven't checked with the updcd code, though to find
out where the "Printer: " gets added in the first place.

  HOWEVER even with this modification, when installing a new printer,
it's still asking for the CDROM instead of going to the boot drive -
which is not working as designed. Since I've done a similar
modification with prdesc.lst on my workstation years ago by hand I know
that all existing printers are taken from the drivers already on the
boot partition.

>> Again due to getting a few errors for image size I've tried to remove
>>all stuff that is not needed. As such I noted that the CDROM also
>>features Joliet. Is there a specific need for it? Other than that it
>>may be needed in an CDROM creation from Windows? I've remove the
>>parameter from the lib and noted no problems with the resulting CDROM.
>
>Which parameter did you remove?

  OK, I took out the "-J" from the mkfs= definition in RECORD.RLB since
"-J" is adding Joliet in mkisofs.exe. Saves about 3MB of space. Since
my image is "net" 649 (something) MBs and ca 679 MB are actually
written to disk according to cdrecord, even this small amout is getting
significant with respect to adding a few more features.

  BTW when changing to cdrecord v2 along my tests I noted that the
continuing update in the window list during actual burning a cdrom did
not function any more. No other changes - just replacing v1.1x (don't
have it at hand) with the last one on Hobbes and putting all exes into
a single directory (not various  subdirectories as with the 'official'
install).  Don't know which software's to blame - but I felt this was a
very handy function....

  Thanks again for looking into it.

  Martin


  Martin R. Hadam
  Kinderklinik - Medizinische Hochschule
  D-30623 Hannover
  Germany
  Email: Hadam.Martin@...

On Sat, 02 Oct 2004 17:48:30 +0200, Zsolt Kadar wrote:

>I believe you are right about TCP/IP 4.0 (Warp 4). But what about older
>versions, like 3.0 in Warp Connect? (Warp Server has 3.1).

  My "original" Warp4 install still features the "install /b-"
(presumably like all other 16Bit versions) in the "x.6.instprog =  "
definition. In contrast, 32Bit TCPIP seems to require (?) the "install
/a-" variant, at least in my hands (whan adding 32bit TCPIP to a
genuine 16Bit TCPIP OS version like Warp Server SMP). Neither parameter
is valid/defined with the respective other version. Don't know, though,
if its use will generate an error (say using something like "install
/b- /a-"  as a "passe-partout"). Will give it a try...

  Martin


  Martin R. Hadam
  Kinderklinik - Medizinische Hochschule
  D-30623 Hannover
  Germany
  Email: Hadam.Martin@...

Hi,

--- In updcd@yahoogroups.com, "Zsolt Kadar" <kadzsol@x> wrote:
> >   Date: Wed, 29 Sep 2004 23:15:54 -0000
> >   From: "barf1234de" <lars.erdmann@a...>
> >
> >Still you are right, we should update lcudrvr.fil (in all its
> >incarnations like lcudrvr.wp4,lcudrvr.cp etc) to read this way, this
> >is true and should work for any version of TCPIP:
>
> If you are sure about it I can replace the parameter.

I am definitely sure about Warp4 as I read the CID documentation that
comes with it.

>
> >(note the additional /a- that will prevent any popup asking for
> >whatever install parameters as there are always default values even
> >for all parameters that are NOT defined in the RSP file. This is
> >necessary as the install dialog window will be hidden behind the
> >ISHIELD fullscreen installation window and therefore will NOT be
> >accessible ! I have checked with the original Warp4 install Cd-ROM and
> >that parameter existed back then).
>
> I believe you are right about TCP/IP 4.0 (Warp 4). But what about older
> versions, like 3.0 in Warp Connect? (Warp Server has 3.1).

I have checked my old Warp3 disk. I couldn't find any CID
documentation, then I looked up install.exe (for the internet
installation) with a hex editor and indeed found a "/a-" with all the
  other parameters that it supports. So it looks like that parameter
has been around for long time.
The GUI looks very familiar and all the other parameters that the
Warp4 install.exe supports also seem to be supported (again, having
taken a look with a hex editor).

Lars

Hi,

using updcd 2. 46 b2.
In \updcd\lib\general.lib , routine "regenerate_cdinst":

After "regenerate_cdinst" has run over the batch files, I get the
following lines:

@SET TARGET=A:
@IF NOT %1.==. SET TARGET=%1
...
\DISKIMGS\LOADDSKF %1\DISKIMGS\OS2\35\DISK1_CD.DSK %TARGET% /Y/Q/F
...
\DISKIMGS\LOADDSKF %1\DISKIMGS\OS2\35\DISK2.DSK %TARGET% /Y/Q/F
...
\DISKIMGS\LOADDSKF %1\DISKIMGS\OS2\35\DISK0.DSK %TARGET% /Y/Q/F

That does not work correctly as some duncehead at IBM has written a
really queer (original) CMD/BAT file in the first place. We have to
kill the extra %1 to get it working correctly:

\DISKIMGS\LOADDSKF \DISKIMGS\OS2\35\DISK1_CD.DSK %TARGET% /Y/Q/F
...
\DISKIMGS\LOADDSKF \DISKIMGS\OS2\35\DISK2.DSK %TARGET% /Y/Q/F
...
\DISKIMGS\LOADDSKF \DISKIMGS\OS2\35\DISK0.DSK %TARGET% /Y/Q/F

Could someone fix this ? Unfortunately I don't have any time at all at
the moment ...

Lars

Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the updcd
group.

   File        : /updcd246b3.zip
   Uploaded by : kadzsol <kadzsol@...>
   Description : UpdCD 2.46 beta 3

You can access this file at the URL:
http://groups.yahoo.com/group/updcd/files/updcd246b3.zip

To learn more about file sharing for your group, please visit:
http://help.yahoo.com/help/us/groups/files

Regards,

kadzsol <kadzsol@...>

changes:

new: added support for xfree86 4.4.0 addon
new: added addon support for security2 icw openssh
new: made openssh/security2 install unattended
fix: made mozilla association default for html files

Enjoy!

Zs

>  From your wording I assume that this is a "known issue" with that
> specific version. Correct?

No, no. I have not noticed it yet. I have looked at my config.sys of
ecs 1.1 and most of it is in capitals. But I still need to test it.

> I've noted it after I added my own prompt to
> tunecfg.cfg  - but at this point I do not recall if I had moved to
> TCPIP 4.21 already or if that was still with v4.1. If NOT a known
> problem I'd go back and determine from which version onwards this is
> happening.

Please try to localize the problem.

>  I've checked several installs: all have a "Printer: " preceding every
> single line in prdesc.lst. Once removed with an editor, all is fine
> with the display. Haven't checked with the updcd code, though to find
> out where the "Printer: " gets added in the first place.

Updcd adds it, but displaying/installing was working ok, as far as I
could see.

>  HOWEVER even with this modification, when installing a new printer,
> it's still asking for the CDROM instead of going to the boot drive -
> which is not working as designed. Since I've done a similar
> modification with prdesc.lst on my workstation years ago by hand I know
> that all existing printers are taken from the drivers already on the
> boot partition.

Will test it next week with Warp 3.

> >Which parameter did you remove?
>  OK, I took out the "-J" from the mkfs= definition in RECORD.RLB since
> "-J" is adding Joliet in mkisofs.exe. Saves about 3MB of space. Since
> my image is "net" 649 (something) MBs and ca 679 MB are actually
> written to disk according to cdrecord, even this small amout is getting
> significant with respect to adding a few more features.

OK, that should not be a problem if you do not use long (addon) file
names on the CD.

> install).  Don't know which software's to blame - but I felt this
was a very handy function....

cdrecord? :-)

Zs

> I have checked my old Warp3 disk. I couldn't find any CID
> documentation, then I looked up install.exe (for the internet
> installation) with a hex editor and indeed found a "/a-" with all the
>  other parameters that it supports. So it looks like that parameter
> has been around for long time.
> The GUI looks very familiar and all the other parameters that the
> Warp4 install.exe supports also seem to be supported (again, having
> taken a look with a hex editor).

OK, I will add the switch in the next beta and we will see if that
breaks something.

Zs

> That does not work correctly as some duncehead at IBM has written a
> really queer (original) CMD/BAT file in the first place. We have to
> kill the extra %1 to get it working correctly:
>
> \DISKIMGS\LOADDSKF \DISKIMGS\OS2\35\DISK1_CD.DSK %TARGET% /Y/Q/F
> ...
> \DISKIMGS\LOADDSKF \DISKIMGS\OS2\35\DISK2.DSK %TARGET% /Y/Q/F
> ...
> \DISKIMGS\LOADDSKF \DISKIMGS\OS2\35\DISK0.DSK %TARGET% /Y/Q/F
>
> Could someone fix this ? Unfortunately I don't have any time at all at
> the moment ...

next beta :-)

Zs

Hi,

using updcd V2.46 beta 2:

1.) Choosing "Add DANI FLT" does (presumably) not what is intended.
DANIATAP.FLT is not renamed to IBMIDECD.FLT in the boot image
disk_0_1.img but in config.sys of disk_0_1.img IBMIDECD.FLT is
supposed to be loaded.

For IBM1S506.ADD /DANIS506.ADD this works correctly.

2.) The same holds true for \DISKIMGS\OS2\35\DISK1_CD.DSK
(IBM1S506.ADD replacement is ok, IBMIDECD.FLT replacement does not work).

Or am I getting something wrong ?

Lars

Hi,

using updcd V2.46 beta 2 together with Warp 4:
I have selected "Add FAT32" so as to have FAT32 already on CD-boot.
But looking into \DISK_0_1.IMG and also into
\DISKIMGS\OS2\35\DISK1_CD.DSK I can see no support for FAT32, neither
the necessary files were added nor was the config.sys updated.

Or is there something special needed to have this work ?

Lars

Hi,

answering myself:

sh.., I have to use floppy emulation for boot method so that's why (I
don't have LVM, poor me).
But why is there this restriction for floppy emulation boot ? Not
enough space on DISK_0_1.IMG and/or DISK1_CD.DSK ?

Lars


--- In updcd@yahoogroups.com, "barf1234de" <lars.erdmann@a...> wrote:
>
> Hi,
>
> using updcd V2.46 beta 2 together with Warp 4:
> I have selected "Add FAT32" so as to have FAT32 already on CD-boot.
> But looking into \DISK_0_1.IMG and also into
> \DISKIMGS\OS2\35\DISK1_CD.DSK I can see no support for FAT32, neither
> the necessary files were added nor was the config.sys updated.
>
> Or is there something special needed to have this work ?
>
> Lars

Hi,

am I right in assuming that the integration of additional MAC and
PROTOCOL drivers is still a problem because of filename extensions ?

Example:
For the KDBNET PROTOCOL driver, I have an update that I would like to
use but the file names are KDBNET.SYS/KDBNET.NIF, instead of
KDBNET.OS2/KDBNET.NIF.

Also for the generic MAC driver by Willibald Meyer the filenames are
GENM32.OS2/NVNETLIB.O/GENM32.NIF, so we have a .O file that is not
treated well by updcd.

As I can see from \updcd\newinst\mkrsp.cp|mkrsp.wp4|mkrsp.wsb, OS/2
first tries to install MAC|PROTOCOL drivers from CD_DRIVE\CID\NIFS
before it tries to install them from BOOT_DRIVE\IBMCOM\MACS or
BOOT_DRIVE\IBMCOM\PROTOCOL (where the files are placed when MPTS is
installed).

So my suggestion is: Could UPDCD just copy the additional files from
the FIXES/MPTSFIXPAK/ADDONS directory to CD_DRIVE\CID\NIFS instead of
trying to pack them into the MPTS zips ? That would be a lot easier
and less hassle and the MAC|PROTOCOL driver installation will in the
course of normal installation copy all associated files to
BOOT_DRIVE\IBMCOM\MACS or BOOT_DRIVE\IBMCOM\PROTOCOL anyway.

There would also be a 3. alternative when we fix
mkrsp.cp|mkrsp.wp4|mkrsp.wsb (we have to rearrange a few code lines,
god these files are a mess):
You can build subdirectories IBMCOM\MACS and IBMCOM\PROTOCOL under the
CD_DRIVE\IBMINST\TABLES directory and place MAC|PROTOCOL files there.
I think that one would even be better. I think IBM intended to do it
this way but the way their code looks like they never really tested
it. I would be willing to fix mkrsp.cp|wp4|wsb if we did that.


P.S.:CD_DRIVE would be the final CD ROM drive. So for the updcd
installation this would mean if you installed updcd to let's say
directory C:\UPDCD then CD_DRIVE would be: C:\UPDCD\BURN.


Zsolt, What do you think ?

Lars

On 10/03/2004 at 07:19 PM, "kadzsol" <kadzsol@...> wrote:

>>  From your wording I assume that this is a "known issue" with that
>> specific version. Correct?

>No, no. I have not noticed it yet. I have looked at my config.sys of ecs 1.1
>and most of it is in capitals. But I still need to test it.

IIRC this is about MPTS install upper-casing config.sys, yes?

At the time I was using WarpUP! to update my 3/Connect installations, Duane
told me that this is a known problem with IDM's MPTS installer, and the only
fix is editing config.sys by hand after MPTS is installed.

For new installs, someone later noted that doing MPTS as early as possible,
before ANY customization is done, is the safest/easiest way.

--
     Phil Parker
--------------------------------------------
URL http://www.math.wichita.edu/~pparker/
Random quote:
   Know thyself. If you need help, call the C.I.A.

In article <cjpir2+s47d@eGroups.com>, "kadzsol" <kadzsol@...> wrote:

> new: added support for xfree86 4.4.0 addon

Have to see about downloading it...

> fix: made mozilla association default for html files

That works well.

A couple of items. I'm still getting UP2TB.FLT in the final CONFIG.SYS,
even though I've got the 'add up2tb' unticked in UpdCD config.

Also, I always seem to end up with a couple of strange files left in
the root directory of the boot drive:

CMD640X.ADD
DETNE2.SYS

plus a basdev statement for LMS206.ADD in the installed CONFIG.SYS (:)
can't even recall what LMS206.ADD is for - a CD driver?).

After loading Mozilla, machine was rebooted, then the various items in
the Multimedia addons were installed. The flash plugin is not being
installed for Mozilla - had to copy npswf2.dll manually to the
\mozilla\plugins directory.

Also, this time round, I created TUNECFG.CFU. Generally, that seems to
have worked ok to override any defaults in TUNECFG.CFG. However, one
item that I had in it has not been implemented - I had this...

<ADD_BOT>
    rem SET MENUSFOLLOWPOINTER=ON

However, in the final CONFIG.SYS, it is not rem'd, but active.

Other than the above, beta 3 is working well here.

paul.

--
paul.marwick@...
Marwick Computer Services - Chipping Norton, Oxfordshire, UK
OS/2, LAN and general Computer Consultants

I've just tried again to build a Warp 4 CD with TCP/IP 4.3 added to the
fixes. Hoping to get round the prroblem of the Shared Resources and
Network Connections object not being created, I only used TCP/IP 4.3
and the MPTS update that comes bundled with it. Thought I could add the
later MPTS fixes and the TCP/IP fixes later if I got the first part to
work. As a result, I didn't have a fixpack directory to put addons and
extra NIC drivers. So I followed (or tried to...) the informaiton in
the FAQ. I rebuilt the MACS.ZIP found in burn\CID\IMG\MPTS\ibmcom\macs,
adding the extra .os2 and .nif files to it. I used ZIP.1 from \bin
(copied to Zip1.exe so I wouldn't use it in the wrong place).

However, when I went through the installation, none of the extra NIC
drivers were listed. Did I miss something in the process?

Its a bit academic - the idea didn't work. As soon as I completed
installation I opened the Connections folder and checked the Network
Services folder - no sign of the Shared Resources object. I wish I knew
what was causing this problem, but it seems quite consistent - I've had
the same thing happen with several different CD builds and on several
different machines.

paul.

--
paul.marwick@...
Marwick Computer Services - Chipping Norton, Oxfordshire, UK
OS/2, LAN and general Computer Consultants

Hi,

Here is what I think you have to do:

1.) Build the UPDCD CD-ROM (but I guess you have already done so)
2.) Open file \updcd\burn\IBMINST\TABLES\ADAPTERS.FIL (assuming your
base dir for UPDCD is \updcd)
3.) The contents of the file are sorted alphabetically. Add a driver
line by adhering to the syntax of the other lines.
4.) Burn your UPDCD CD-ROM
5.) Check if it helped :-)

Lars

--- In updcd@yahoogroups.com, paul.marwick@v... wrote:
> As a result, I didn't have a fixpack directory to put addons and
> extra NIC drivers. So I followed (or tried to...) the informaiton in
> the FAQ. I rebuilt the MACS.ZIP found in burn\CID\IMG\MPTS\ibmcom\macs,
> adding the extra .os2 and .nif files to it. I used ZIP.1 from \bin
> (copied to Zip1.exe so I wouldn't use it in the wrong place).
>
> However, when I went through the installation, none of the extra NIC
> drivers were listed. Did I miss something in the process?
>
> Its a bit academic - the idea didn't work. As soon as I completed
> installation I opened the Connections folder and checked the Network
> Services folder - no sign of the Shared Resources object. I wish I knew
> what was causing this problem, but it seems quite consistent - I've had
> the same thing happen with several different CD builds and on several
> different machines.
>
> paul.
>
> --
> paul.marwick@v...
> Marwick Computer Services - Chipping Norton, Oxfordshire, UK
> OS/2, LAN and general Computer Consultants

Hi,

I reworked the above mentioned files for routine "BuildMPTS".

The following sequence is selected to check for the existence of MAC
driver files (and analog for the PROTOCOL files):

1.) Check in directory ibminstdrive'\IBMINST\TABLES\IBMCOM\MACS'
2.) Check in directory CD_Drive'\CID\NIFS'
3.) Check in directory MPTS_Drive'\IBMCOM\MACS'

where ibminstdrive'\IBMINST\TABLES' is equivalent to tabledir.
Note that I haven't changed any of the code but just reworked the
sections so that it is the same procedure for MAC and for PROTOCOL files.

Right at the end of "BuildMPTS" files from
ibminstdrive'\IBMINST\TABLES\IBMCOM' and subdirectories are copied to
MPTS_Drive'\IBMCOM':

if nifs.0 > 0 then
      '@xcopy ' tabledir'\IBMCOM\* 'MPTS_Drive'\IBMCOM\ /S /E >nul 2>nul'

The only question that I have is if:
ibminstdrive = filespec(Drive,cfgfile)
is the boot drive (MPTS_Drive) or the CDROM drive (CD_Drive) ?



Shall I upload the files ?

Lars

In article <cjs9c4+ncfd@eGroups.com>,
"barf1234de" <lars.erdmann@...> wrote:

> Here is what I think you have to do:
>
> 1.) Build the UPDCD CD-ROM (but I guess you have already done so)
> 2.) Open file \updcd\burn\IBMINST\TABLES\ADAPTERS.FIL (assuming your
> base dir for UPDCD is \updcd)
> 3.) The contents of the file are sorted alphabetically. Add a driver
> line by adhering to the syntax of the other lines.
> 4.) Burn your UPDCD CD-ROM
> 5.) Check if it helped :-)

:) Great. Thanks. I wondered where the description would come from.
I'll try that.

regards, paul.

--
paul.marwick@...
Marwick Computer Services - Chipping Norton, Oxfordshire, UK
OS/2, LAN and general Computer Consultants

Hi,

I tried this myself, however I have the impression that it won't help.
I rather think npconfig.exe builds this list dynamically by looking
for all NIF files that it finds "somewhere" and reading in the driver
description that is in the NIF files.

I guess the "somewhere" is either directory CD_DRIVE\IBMINST\NIFS or
CD_DRIVE\IBMINST\NIFS\MACS or MPTS_DRIVE\IBMCOM\MACS where "CD_DRIVE"
is the drive of your updcd CD-ROM and MPTS_DRIVE is the drive of the
MPTS installation, in general your boot drive.

Lars

--- In updcd@yahoogroups.com, paul.marwick@v... wrote:
> In article <cjs9c4+ncfd@e...>,
> "barf1234de" <lars.erdmann@a...> wrote:
>
> > Here is what I think you have to do:
> >
> > 1.) Build the UPDCD CD-ROM (but I guess you have already done so)
> > 2.) Open file \updcd\burn\IBMINST\TABLES\ADAPTERS.FIL (assuming
your
> > base dir for UPDCD is \updcd)
> > 3.) The contents of the file are sorted alphabetically. Add a
driver
> > line by adhering to the syntax of the other lines.
> > 4.) Burn your UPDCD CD-ROM
> > 5.) Check if it helped :-)
>
> :) Great. Thanks. I wondered where the description would come from.
> I'll try that.
>
> regards, paul.
>
> --
> paul.marwick@v...
> Marwick Computer Services - Chipping Norton, Oxfordshire, UK
> OS/2, LAN and general Computer Consultants

** Reply to message from "kadzsol" <kadzsol@...> on Mon, 27 Sep 2004
11:27:34 -0000


>new: make mozilla default browser and associate it with html files

Will UPDCD accept FireFox in place of Mozilla?

--
Cliff

"Genius is one percent inspiration and ninety-nine percent perspiration." 
THOMAS ALVA EDISON