home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 15 Message
/
15-Message.zip
/
oe991211.zip
/
Oe991210.txt
< prev
next >
Wrap
Text File
|
1999-12-11
|
190KB
|
5,118 lines
General OS/2 Discussion (Fidonet)
Saturday, 04-Dec-1999 to Friday, 10-Dec-1999
+----------------------------------------------------------------------------+
From: Will Honea 04-Dec-99 00:53:00
To: Murray Lesser 04-Dec-99 00:53:00
Subj: Multiple visible primary
Murray Lesser wrote to Will Honea on 12-02-1999
ML> AFAIAC, the loss of that last cylinder is also "in the noise"
ML> :-(. If I wanted to guess, I would say that the practice you
ML> describe dates from the XT days when the last cylinder was reserved
ML> for a test track used only by the hard-drive read/write diagnostics.
ML> I had a small assembly-language routine for my XT that moved the
ML> heads over to that last cylinder before shutting down, so that if
ML> there wasn't a smooth landing, there would be no damage to usable
ML> data. As I understand it, this was done automatically on the AT.
ML> (I never owned an AT; I skipped the 286 generation as it didn't make
ML> any sense to me.) I would guess that hard-drive reliability (at
ML> least for drives from reputable makers) had improved (by the time
ML> OS/2 came along) to the point where that "test track" was probably
ML> unnecessary, but nobody noticed it was still there until relatively
ML> recently!
According to Sam Detweiler of IBM, this was originally a parking zone
but like so many things it got built into other unrelated programs.
Specifically, it was used for destructive read/write/read testing in
some diags that IBM used for their PC's. So we have 1 cylinder at
either end of the drive that is possibly wasted - mousefarts in a
hurricane. But as the politician said: "a trillion here, a trillion
there; pretty soon we're talking about some real money!"
Will Honea <whonea@codenet.net>
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Jonathan de Boyne Pollard 01-Dec-99 10:05:06
To: Eddy Thilleman 04-Dec-99 06:00:04
Subj: vkbd.sys
ET> I have that VKBD.SYS file in \OS2\MDOS in my boot partition, but it is
ET> not listed in config.sys. The virtual driver VKBD.SYS is loaded (I
ET> checked with Process Commander) so I assume it's loaded silently?
There are two sorts of VDDs, "base" VDDs and "installable" VDDs. The "base"
VDDs are always loaded, since they are essential to the operation of a VDM.
The "installable" VDDs are the ones listed in CONFIG.SYS .
There's a list of the "base" VDDs in the Virtual Device Driver Reference in
the OS/2 DDK.
» JdeBP «
--- FleetStreet 1.22 NR
* Origin: JdeBP's point, using Squish <yuk!> (2:257/609.3)
114/477
143/1
+----------------------------------------------------------------------------+
From: Jonathan de Boyne Pollard 02-Dec-99 09:01:22
To: Andrew Belov 04-Dec-99 06:00:04
Subj: odin-19991112
AB>>> The error message is always SYS0182 referencing USER32->PMWINX.1022,
JdBP>> That means that you don't have the latest PMWINX.DLL. Since
JdBP>> PMWINX.DLL is part of "Open32", that means in turn that you don't
JdBP>> have the latest Open32.
AB> PMWINX DLL 520559 4.12.98 20:35
Have you checked (with a tool such as EXEHDR or TDUMP) that it actually
exports something with ordinal number 1022, which is what the message is
complaining about ?
» JdeBP «
--- FleetStreet 1.22 NR
* Origin: JdeBP's point, using Squish <yuk!> (2:257/609.3)
114/477
143/1
+----------------------------------------------------------------------------+
From: Jonathan de Boyne Pollard 02-Dec-99 18:27:24
To: Holger Granholm 04-Dec-99 06:00:04
Subj: HPFS Filenames to Windows
RV>> N' = (nou = we
RV>> a = future indicator (shall)
RV>> pale = speak
RV>> pi = more
RV>> ta = late
RV>> [nah pal-AY pee tah]
HG> And what language is that? Miamish?
It looks like French spelled phonetically and slightly mangled.
"Nous allons parler plus tard"
Given that, my guess is that it's some form of creole.
» JdeBP «
--- FleetStreet 1.22 NR
* Origin: JdeBP's point, using Squish <yuk!> (2:257/609.3)
114/477
143/1
+----------------------------------------------------------------------------+
From: Nick Andre 03-Dec-99 15:48:26
To: All 04-Dec-99 06:00:04
Subj: OS/2 Printer
Hi!
I just picked up an IBM LaserPrinter E, and was wondering about its
capabilities, speed, etc? And is there a way to make it do a self-test? (ie,
print out a test pattern?). Any help appreciated.
--- DB A4000.3sl/000967
* Origin: Hidden Obsessions (1:252/501)
270/101
+----------------------------------------------------------------------------+
From: Gerard Zoer 03-Dec-99 08:31:29
To: Eddy Thilleman 04-Dec-99 06:00:04
Subj: wave files?
Hello Eddy,
Thursday December 02 1999 16:28, Eddy Thilleman wrote to All:
ET> WIN95.WAV 389140 W'95 client in panic asks for help
ET> Helpdesk is clueless. Starring Charles Heston.
ET> Time 0:35.28
Over here. WIN95S.RAR
- Greets,
--[Gerard]-- (gezo@hccfido.hcc.nl)
--- GoldED/2 3.0.1
* Origin: HCC Kennemerland * 31-23-5330478 * 33k6/ISDN * (2:280/5143)
+----------------------------------------------------------------------------+
From: Eddy Thilleman 03-Dec-99 12:43:14
To: Joe Provencio 04-Dec-99 06:00:04
Subj: Canon BJC 5000 printer driver
Hello Joe,
01 Dec 99 12:32, Joe Provencio wrote to All:
JP> there are no specific drivers for this model. There are drivers for
JP> the modle 5500 but not the 5000, Can the 5500 driver be used for the
JP> 5000 on a OS/2 v4 system ?? Any help on this appreciated TIA
I see it in the list of supported printers of the omni driver, it's in the
omni.lst file:
Canon BJC-5000: Canon BJC-5000 (omni.drv)
OMNI.LST - LIST OF ALL DEVICES SUPPORTED
So if your copy of the omni driver doesn't list it, download a new version
from IBM's device driver online pak website.
Greetings -=Eddy=- email: eddy.thilleman@net.hcc.nl
... POTTIE called (A)bort, (R)etry, (K)ill caller?
--- GoldED/2 3.0.1
* Origin: Windows95 is a graphic DOS extender (2:280/5143.7)
+----------------------------------------------------------------------------+
From: Stewart Buckingham 04-Dec-99 08:10:10
To: Gary Crain 04-Dec-99 06:00:04
Subj: Communicator Fatal Error
Hi Gary,
>> Thanks. I considered this and went looking for my Communicator
>> archive but unfortunately couldn't find it :( Nobody using 4.04 has
>> yet admitted they actually have an os2pref.js on their hard disk. I
>> would be interested in seeing what it looks like, and in which
>> directory it resides.
> I just checked here (I have 4.04 and 4.61 installed) and there is no such
> file. I do have a prefs.js in :\netscape\users\gcrain. Here's the file
> listing for it;
> prefs.js 8350 11-22-1999 15:55
Thanks. The file size and date of prefs.js will vary from user to user. It's
not the file I need tho' :( It does seem strange to me that Communicator 4.04
is trying to parse a non-existant file :(
Stu/2
--- BBBS/2 v3.50 Flag-A
* Origin: The Chili Channel * OS/2 - Java - Linux * chilies.com * (6:751/222)
2502/33
+----------------------------------------------------------------------------+
From: Stewart Buckingham 04-Dec-99 08:25:24
To: Ian Moote 04-Dec-99 06:00:04
Subj: Communicator Fatal Error
Hi Ian,
>> Thanks. I considered this and went looking for my Communicator
>> archive but unfortunately couldn't find it :( Nobody using 4.04 has
>> yet admitted they actually have an os2pref.js on their hard disk. I
>> would be interested in seeing what it looks like, and in which
>> directory it resides.
> I'm one of the previous respondants. I misread your original post and
> thought that you were posting about the "prefs.js" file in the users'
> subdirectories. Just to confirm, I don't have an os2pref.js file on my
> system.
Neither do I :( It does seem strange that Communicator is trying to parse a
non-existant file :(
> As I suggested, did you try renaming it to see if Netscape would
> recreate a clean one?
Yes I did rename prefs.js but it still wouldn't get past the "parsing
os2prefs.js error", so no new prefs.js was created. Thanks.
Stu/2
--- BBBS/2 v3.50 Flag-A
* Origin: The Chili Channel * OS/2 - Java - Linux * chilies.com * (6:751/222)
2502/33
+----------------------------------------------------------------------------+
From: Stewart Buckingham 04-Dec-99 08:37:03
To: MIKE RUSKAI 04-Dec-99 06:00:04
Subj: Communicator Fatal Error
Hi Mike,
>> Your best bet at this point would be to install Netscape over the old
>> version. If your settings are still there to be preserved, they will be.
>> Otherwise, you'll get a usable os2pref.js file without deleting anything.
>> Thanks. I considered this and went looking for my Communicator archive
>> but unfortunately couldn't find it :( Nobody using 4.04 has yet
>> admitted they actually have an os2pref.js on their hard disk. I would
>> be interested in seeing what it looks like, and in which directory it
>> resides.
> Well, I don't have one, but I do have a prefs.js file, which is Netscape
> actually can't read when it says it can't read os2pref.js.
Aha! So we are now getting somewhere! You seem to be saying that os2pref.js =
prefs.js. Well I tried renaming it and restarting, but still had the same
problem (error msg). Would this indicate some kind of pathing problem? Any
ideas where I should look?
Stu/2
--- BBBS/2 v3.50 Flag-A
* Origin: The Chili Channel * OS/2 - Java - Linux * chilies.com * (6:751/222)
2502/33
+----------------------------------------------------------------------------+
From: Stewart Buckingham 04-Dec-99 08:57:04
To: Eddy Thilleman 04-Dec-99 06:00:04
Subj: Communicator Fatal Error
Hi Eddy,
> The os2pref.js file is located in the netscape user directory (where for
>example also the bookmarks are located), it's a text file and mine begins
with
> // Netscape User Preferences
> // This is a generated file! Do not edit.
I just learned from Mike that os2pref.js = prefs.js. Anyhow I've tried
deleting the file and I've tried copying the file to os2pref.js, but neither
seems to solve the parsing problem. Is there a path to this file somewhere?
Stu/2
--- BBBS/2 v3.50 Flag-A
* Origin: The Chili Channel * OS/2 - Java - Linux * chilies.com * (6:751/222)
2502/33
+----------------------------------------------------------------------------+
From: Stewart Buckingham 04-Dec-99 10:07:11
To: Jonathan De Boyne Pollard 04-Dec-99 06:00:04
Subj: FileStar/2 Assumptions
Hi Jonathan,
> To briefly return to the initial topic of this thread, then:
>The CMD.EXE shipped by IBM with all versions of OS/2, up to and including
OS/2
> Warp 4 with the latest fixpack, and almost certainly including WSfeB as
well,
> is an entirely 16-bit program, despite the erroneous information displayed
by
> programs such as the current version of FileStar/2. It's another 16-bit
>vestige in OS/2 Warp 4 that is in need of replacement. JP Software's 4OS2 is
>mixed 32-bit/16-bit hybrid. But there does exist a pure 32-bit CMD, for
32-bi
> OS/2, that contains no 16-bit code whatsoever.
Where can this 32-bit CMD be obtained? Will it work under Warp4?
Stu/2
--- BBBS/2 v3.50 Flag-A
* Origin: The Chili Channel * OS/2 - Java - Linux * chilies.com * (6:751/222)
2502/33
+----------------------------------------------------------------------------+
From: Dave Davidson 03-Dec-99 21:52:24
To: David Randall 04-Dec-99 06:00:04
Subj: More OS/2 Questions.....
Hello David!
Wednesday November 17 1999 18:28, David Randall wrote to Dave Davidson:
> Dave Davidson wrote in a message to All:
>
DD>> (5) I haven't tried it yet, but the question still remains....
DD>> Will DOS Communications programs bomb under OS/2 with a
DD>> ScreenSaver active as they do with WIN9x? Keep in mine I've
DD>> been using WIN9x for a few years and it may take a while to
DD>> get over the "WIN think" as well. <g> Specifically,
DD>> Terminate! Under WIN9x, it will #NOT# answer the phone when a
DD>> screen saver is active.
>
> I use Warp 3 rather than 4, but BLANKER doesn't cause problems with
> DOS comm programs. I can't comment on other screen saver programs
> because I haven't tried them, but OS/2 handles DOS programs much
> better than WIN9x, so I don't believe you'll have a problem.
>
Thanks to you and several others that responded, Blanker is now working
overtime on my system, and everything is functioning properly.
I was somewhat over concerned with the screen blanking business, since I
had such a lousy experience with it under WIN9x. With OS/2 however, it really
isn't a consideration.
Thanks for your input.
Regards,
Dave Davidson
... URA Redneck if: You've lost a tooth opening a Beer bottle.
--- OS/2 * AdeptXBBS * AllFIX * GoldED+
* Origin: A. P. C. * Collonsville, IL * Now OS/2 * v90 (1:11/107)
+----------------------------------------------------------------------------+
From: Holger Granholm 03-Dec-99 21:10:00
To: Andy Roberts 04-Dec-99 07:45:13
Subj: USB
In a message dated 12-01-99, Andy Roberts said to Holger Granholm:
Hi Andy,
HG> Another question: Any hints on USB support in Warp 4?
AR>If you look on that CD you just got from me:
Yeah, see my previous reply ;-)
AR>Usbcom02.Zip was just announced by Pete Norloff, so it may not be on
AR>that CD.
Just checked, it isn't but I'll await your reply to the previous reply.
Regards,
Holger
___
* MR/2 2.26 * To whom the gods destroy, they first teach Windows...
--- PCBoard (R) v15.22 (OS/2) 2
* Origin: Coming to you from the Sunny Aland Islands. (2:20/228)
+----------------------------------------------------------------------------+
From: James Mckenzie 03-Dec-99 20:02:02
To: Eddy Thilleman 04-Dec-99 07:45:13
Subj: DELTREE
Hello Eddy!
02 Dec 99 10:14, Eddy Thilleman wrote to Holger Granholm:
ET> Hello Holger,
ET> 29 Nov 99 20:46, Holger Granholm wrote to Eddy Thilleman:
ET>>> Was that on a FAT partition with hundreds files in one or more
ET>>> directories under plain DOS booted (=not under OS/2) without a
ET>>> disk cache ?
HG>> AFAIK deltree is a DOS program and consequently it was a FAT
HG>> patition.
ET> That still leaves one question I asked to be answered: was it run
ET> under plain DOS booted (=not under OS/2) without a disk cache?
I have an OS/2 verision of DELTREE and it works on HPFS partions (I've
deleted an old OS/2 installation with it...)
ET> There are OS/2 programs with the name DELTREE and have the same
ET> purpose as its DOS counterpart. And DOS programs can be run under
ET> OS/2, and also on HPFS partitions.
Yep.
ET> So: was it run under plain DOS booted (=not under OS/2) without a
ET> disk cache?
Which one? The DOS deltree would not work under OS/2 and would delete
directories only on FAT partitions when booted to plain "old" DOS. Disk
caching did not matter as the version with DOS 6 was designed to work with
most disk caching schemes.
James
... ...If speed kills, then Windows users must live for ever.
--- GoldED/2 3.0.1
* Origin: OS/2 Support * Your place for OS/2 information and Files
(1:15/64)
114/477
143/1
+----------------------------------------------------------------------------+
From: Rachel Veraa 03-Dec-99 21:18:20
To: Francois Thunus 04-Dec-99 10:24:08
Subj: kreyol
In a message to Rachel Veraa, Francois Thunus wrote:
FT> 30 Nov 99 19:49, Rachel Veraa wrote to Holger Granholm:
HG>> And what language is that? Miamish?
RV> Well, it's now Miami's third language, after English and Spanish.
RV> It's Kreyòl, the language of Haiti.
RV> N'a pale pi ta,
FT> obviously based on French (on va parler plus tard)
Close!
N' = (nou) = we
a = future indicator (shall)
Actually, the "a" is derived from "aller" but it's lost any functional
connection long ago, and now serves entirely as an auxiliary verb along with:
ap = progressive indicator
te = past indicator
ta = subjunctive indicator
N'a pale pi ta,
Rachel
N'a pale pi ta,
Rachel
http://www.netside.net/~rveraa/
* Origin: Birdsoft - North Miami (1:135/907)
+----------------------------------------------------------------------------+
From: Will Honea 04-Dec-99 00:53:00
To: Murray Lesser 04-Dec-99 00:53:00
Subj: Multiple visible primary
Murray Lesser wrote to Will Honea on 12-02-1999
ML> AFAIAC, the loss of that last cylinder is also "in the noise"
ML> :-(. If I wanted to guess, I would say that the practice you
ML> describe dates from the XT days when the last cylinder was reserved
ML> for a test track used only by the hard-drive read/write diagnostics.
ML> I had a small assembly-language routine for my XT that moved the
ML> heads over to that last cylinder before shutting down, so that if
ML> there wasn't a smooth landing, there would be no damage to usable
ML> data. As I understand it, this was done automatically on the AT.
ML> (I never owned an AT; I skipped the 286 generation as it didn't make
ML> any sense to me.) I would guess that hard-drive reliability (at
ML> least for drives from reputable makers) had improved (by the time
ML> OS/2 came along) to the point where that "test track" was probably
ML> unnecessary, but nobody noticed it was still there until relatively
ML> recently!
According to Sam Detweiler of IBM, this was originally a parking zone
but like so many things it got built into other unrelated programs.
Specifically, it was used for destructive read/write/read testing in
some diags that IBM used for their PC's. So we have 1 cylinder at
either end of the drive that is possibly wasted - mousefarts in a
hurricane. But as the politician said: "a trillion here, a trillion
there; pretty soon we're talking about some real money!"
Will Honea <whonea@codenet.net>
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Stewart Buckingham 04-Dec-99 22:17:12
To: All 04-Dec-99 17:19:01
Subj: Communicator Fatal Error
Hi All,
Thanks for everyone's help. I resorted to a reinstall of Communicator 4.04. It
seemed to clear up the problem :)
I then went on to install Java 1.1.8,.... boy I had a shock... I had Netscape
in d:\inet\client\browser\netscape... The Java 1.1.8 install deleted
everything under d:\inet\client.... all my browsers/email/ftp/
irc/newreaders/telnet clients. Jeez that pissed me off, since my backup hard
disk is in for repair! Everything wiped! Including Netscape... all done by the
Java 1.1.8 installer!
Stu/2
--- BBBS/2 v3.50 Flag-A
* Origin: The Chili Channel * OS/2 - Java - Linux * chilies.com * (6:751/222)
208/1
103
+----------------------------------------------------------------------------+
From: Joe Provencio 04-Dec-99 17:42:05
To: Eddy Thilleman 04-Dec-99 17:42:05
Subj: Canon BJC 5000 printer driver
thanks for pointing it out I'll get it & try
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Linda Proulx 04-Dec-99 13:52:00
To: All 04-Dec-99 20:37:02
Subj: Newer update
Greetings,
Thought would let everyone know what's happening.
It seems that the install disks programs are too old for the hardware.
Getting newer disk image for the install disks. Hoping that these will
solve the install problems with fdisk.
More later.
Anon,
Linda
... A computer cuts your work in half and gives you back the bloody ends.
--- MultiMail/MS-DOS v0.32
* Origin: Robin's Universe BBS - Winnipeg MB (1:348/807)
103
+----------------------------------------------------------------------------+
From: Herbert Rosenau 05-Dec-99 00:44:10
To: Jonathan de Boyne Pollard 05-Dec-99 01:56:05
Subj: Clunker update
JdBP>>> "Presentation Manager is multithreaded, always has
JdBP>>> been, and has always had multiple input queues,
JdBP>>> one per application thread."
HR>> Yeah! But it has a *single* System Message Queue. This one is
HR>> that accepts events from keyboard and mouse. The multiple
HR>> application message queues are the other side.
JdBP> And as Mike Ruskai pointed out, that queue is *not* locked and
JdBP> *not* the cause of the problem. It doesn't have to be locked.
It doesn't! It is the PM (pmshell.exe) that is locked while it is calling the
application. Her ist not the application callin PM - PM is calling the
application!
In WinInitialise() the application takes its flow control to PM and PM calls
it back.
It looks like
app -> calls PM -> return -> app
Real it is a reverse stack:
app -> WinInitialise() --- until WinTerminate() PM controls the flow of it
Here it makes the reverse stack ready. The first time an application calls
WinGetMsg() it losts (for that thread) the flow control to PM.
PM calls the application each time it is ready to send an system message to
it. Then its waits for return of that message to send the next one.
Inside PM:
app -> calls WinGetMsg() -> hold app until message from system message
queue received.
Then CALL the application. Here is NO return from WingetMsg()
JdBP> When a thread that is executing WinGetMsg() takes a message
JdBP> from the raw input queue, it only needs to lock the queue
JdBP> whilst it is extracting the message.
No. No application (except PM itself) is able to receive a message from system
message queue. The only receiver is PM itself. PM puts the message (like any
other sended message from any source into the message queue of the receiving
application. Then it calls the application to work on it.
JdBP> It doesn't need to hold the queue locked once it has the
JdBP> message, which means that it isn't preventing other threads
JdBP> from accessing the raw input queue immediately afterwards
JdBP> whilst it goes away and calls WinDispatchMsg().
WinDispatchMessage() does nothing than finding the right message procedure and
calls it. This point acts like a simple subroutine. Only the return from an
message gets control back to PM if PM is the sender. Then PM can read the next
message from system message queue.
If you write a multi threaded PM application you'll see that PM is allocation
the contol of thread 1 (or the thread that is calling WinInitialise() the
first time inside app. Other threads are inependant from system message queue.
They would never receive a mesage from it - other than over thread 1 and
WinDispatchMessage(). Any other thread in any application can proceed with any
message handling. It my sen/post messages to any receiver it has to do -
without blocking the system message queue.
To do that the right way PM manipulates the stackpointer of each thread it
controls!
JdBP> In any case, if this *were* a problem with the raw input queue,
JdBP> it would be a problem on Windows NT as well, because Windows NT
JdBP> *also* has a single raw input queue. But Windows NT is famous
JdBP> for *not* having a "SIQ problem", therefore the problem is not
JdBP> caused by there being a single raw input queue. As I said, the
JdBP> letter 'S' in "SIQ" *does* *not* *stand* *for* *"single"*.
It stands for 'SYSTEM' not for single. The system message queue is the single
queue between the input devices (keyboard, mouse, touch screen...) and the
applications message queue. This queue serialises the events from input
devices so that each event can find its ordinate window.
JdBP> Your explanation of how the raw input queue is blocked
JdBP> is simply wrong. As, too, is your understanding of how PM
JdBP> applications work:
No. You should read the readbooks.
JdBP> In almost every respect your explanation is entirely backwards.
JdBP> Presentation Manager (and indeed Windows and the Macintosh)
JdBP> are "pull event" systems not "push event" systems. You seem to
JdBP> think that PMSHELL.EXE *is* Presentation Manager, and that it
JdBP> pushes events to other applications. This is rubbish.
JdBP> PMSHELL.EXE is simply the first application that uses the
JdBP> Presentation Manager library that happens to run. PMSHELL.EXE
JdBP> *is not* Presentation Manager. PMSHELL.EXE is the Workplace
JdBP> Shell *application*, that just happens to *use* Presentation
JdBP> Manager.
No. PMSHELL.EXE is a dual application. It runs twice.
The first instance (the lower PID) is the PM control - and the second (the
higher PID) is the WPS - a 'simple' user application.
JdBP> There is no single process that contains Presentation Manager.
There IS. It is called pmshell.exe - first instance.
JdBP> You cannot point to an executable and say "that is the PM
JdBP> server process". PM is not X.
Right. But the server process already exists. It has only one real (not
multiple virtual consoles).
JdBP> It doesn't *have* a single server process that pushes events
JdBP> out to all other processes. Presentation Manager is a
JdBP> coöperative effort of all of the applications that use the PM
JdBP> library to present a graphical user interface. And it uses a
JdBP> "pull event" paradigm.
You're wrong.
JdBP> It pulls messages out of the thread's message queue that have
JdBP> been posted to it with WinPostMsg(). It pulls any messages that
JdBP> have been sent to it by other threads with WinSendMsg().
JdBP> Presentation Manager doesn't "call the application" and push
JdBP> events onto it. The application's threads call the
JdBP> Presentation Manager library's WinGetMsg() function and *pull*
JdBP> events from various places, which they then distribute to their
JdBP> individual window functions by then calling WinDispatchMsg().
You should read the PM redbooks. There are some interesting details how are
the PM and PM apps are structured.
JdBP> Moreover, your idea that the application "returns back to PM"
JdBP> whereupon PM unlocks the raw input queue and goes on to process
JdBP> the next message is also completely backwards.
You goes a wrong way. Not the application goes back. The PM receives the
result of the system message it receives an then in sends the next one - if it
exists. The PM hooks on an timer to fit out that a message my never return -
not an users application. This (never returned) app will be sorted out from
receiving any future system message (until it returns). Therefore the PM
(since a early fixpack in WARP4 (FP 17 in WARP3) can continue with serving
the system message queue.
JdBP> The synchronous nature of the "Synchronous Input Queue"
Grrr, its correct name is SYSTEM MESSAGE QUEUE.
JdBP> problem is not that the raw input queue is locked. It *isn't*
JdBP> locked once WinGetMsg() has returned (PM returns to the
JdBP> application, not the other way around, by the way.) and the
JdBP> application is deciding what to do with the message that it has
JdBP> obtained.
The technique PM functions is truly reverse. The redbook described it as
'reverse function call. This means that the PM controls the application
simplified as main() controls any funtion of a C program.
JdBP> The synchronous nature of the SIQ problem is that focus change
JdBP> processing is synchronous. (I admit that I wasn't too clear
JdBP> about this in my previous message. But this isn't the OS2PROG
JdBP> echo where one normally goes into this sort of detail.) All of
JdBP> the WM_ACTIVATE, WM_FOCUS, and WM_SETSELECTION messages that
JdBP> result from WinFocusChange() are sent synchronously, as if by
JdBP> WinSendMsg(). This means that the focus change will block
JdBP> partway through changing the focus if one of the currently
JdBP> active windows isn't calling WinGetMsg() frequently, or at all.
JdBP> (You'll notice that you'll never see a known "bad" application
JdBP> lock Presentation Manager if you never give it the input focus
JdBP> or make any of its windows active.)
You have to differ between messages posted/send by an applications window and
the ones sent by PM resulting from system message queue. You can simply go out
blocking the system message queue by POSTING all longer actions to youself or
another thread. The point is the message received from system message queue
must return berfore another can go from it.
JdBP> The "desynchronisation" fix in OS/2 Warp is to modify
JdBP> WinFocusChange() so that the message sending will time out
JdBP> after a fixed period. (There's no timeout parameter to
JdBP> WinSendMsg() so it must be using an internal, not publically
JdBP> accessible, function to do this.) If a thread refuses to
JdBP> process and acknowledge a WM_ACTIVATE, WM_SETSELECTION, or
JdBP> WM_SETFOCUS message within that time, WinFocusChange() simply
JdBP> acts as if the message *had* been acknowledged, and also marks
JdBP> the offending (WC_FRAME) window as "unresponsive" (and paints a
JdBP> border around it) in case the same thing were to happen in the
JdBP> future.
A window that dosn't own the focus can't receive any message from system
queue. Bercaus PM sends this only to a window that owns the focus - or has to
own after the focus change sequence (its an atomic sequence) is done.
You can freeze the PM with any message that comes from the system message
queue. Write a simple PM program and let it never return from a WM_CHAR - and
the PM hangs - until the syncronous timer in PM removes it (the app) from
system message queue.
Use the simple
WM_CHAR:
while (1) sleep(10000);
to do it. You my act on a single key of your choce or whatever. Use a telnet
session to break the loop.
--- Sqed/32 1.15/development 45:
* Origin: Speed Kills - Use Windows! (2:2476/493)
231/992
+----------------------------------------------------------------------------+
From: Herbert Rosenau 05-Dec-99 01:26:06
To: Jonathan de Boyne Pollard 05-Dec-99 01:56:05
Subj: DETACH
HR>> The only thing a programmer has to do is to
HR>> - write a multithreaded VIO program
HR>> - link with a PM DLL
HR>> then if he would any PM ineraction he starts a thread that calls
HR>> the DLL and this can interact with PM as it likes.
JdBP> Maybe you should have tried this before posting.
I'd so! There is a very big system running a lot of VIO and PM applications
with a lot of functions in a couple of DLLs. To become a unified error handler
we have written a multithreaded DLL to become a PM window up even if the
calling application is a background one (AVIO - optionally detached).
JdBP> If you had, you would have found that WinCreateMsgQueue()
JdBP> returns an error if Presentation Manager detects that the
JdBP> process type in the PIB is for a windowed or full-screen VIO
JdBP> process. WinInitialize() will create an anchor block, but a
JdBP> text-mode process, because of this check, will fail if it tries
JdBP> to do anything that involves sending messages at any stage,
JdBP> because it doesn't have a message queue.
Yes - if it is tried in the same thread! Make a PM DLL, start inside that DLL
a separate thread (use semaphore to syncronise with the non PM thread). Then
link your application with that DLL.
All applications have to use the same compiler- and linker flags - but my use
differen program types.
The trick is the separate thread and the PM type of the DLL.
JdBP> For those unfamiliar with the mechanisms of PM, this can have
JdBP> surprising results. WinQueryWindowText() doesn't work when used
JdBP> by a text-mode application, for instance.
Nothing of Win..() APIs other than WinPostMessage() will work outside a PM
application.
JdBP> This is surprising to the PM novice, until he reads the PM
JdBP> reference and finds that WinQueryWindowText() simply calls
JdBP> WinSendMsg() with WM_QUERYWINDOWPARAMS behind the scenes. The
JdBP> WinSendMsg() fails, of course, because the text-mode
JdBP> application doesn't have a message queue.
Right.
But a thread my be a PM thread if the DLL is ready for PM. And you can make it
one if you declare it as PM in its *.def.
--- Sqed/32 1.15/development 389:
* Origin: Jede Loesung bringt neue Probleme ! (2:2476/493)
231/992
+----------------------------------------------------------------------------+
From: Peter French 05-Dec-99 00:00:00
To: Stewart Buckingham 05-Dec-99 00:00:00
Subj: Communicator Fatal Error
On 1999/12/04, Stewart Buckingham wrote to Eddy Thilleman on message number
316;
Stewart,
SB>
SB> I just learned from Mike that os2pref.js = prefs.js.
Something quite strange with your setup. os2pref.dll is the only file of
that name on my 4.61 install. prefs.js will not be recreated on startup as
it is a system file that I was warned should be edited with great care, as
any corruption will stop NS working. (p.s. did you ever - edit?)
I don't have a 4.40 on my system any more as the testing showed 4.61 to
be far superior from a feature and stability view. However, I can't
remember 4.40 asking for multiple user setup - so I suspect that there
shouldn't be a user directory. So,
1) why bother with 4.40 reinstall 4.61
2) DON'T EDIT prefs.js with anything other than EPM. (I added the
user_pref("toolbar.logo.frames",8); to mine without it complaining.
3) if u want to retain your setup, maybe get a new perfs.js from a
working system - I'll willingly send you mine (4.61)
4) retain your user files and reinstall from the download archive, then
see if perfs.js is recreated - may be a leftover from an aborted 4.61?
or a previous 4.40 install to different directories (did you move it?)
5) confirm categorically that there is a perfs.js on a working 4.40
install. Mine has a bunch of path specific statements so be aware
that they will not transplant easily. I assume that the file is
created at install time using install values.
Hope this helps and you don't feel that the suggestions are too trivial
___
X KWQ/2 1.2i X LINUX is only free if you don't value your own time!
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Peter French 05-Dec-99 00:00:01
To: Nick Andre 05-Dec-99 00:00:01
Subj: OS/2 Printer
On 1999/12/03, Nick Andre wrote to All on message number 310;
Nick,
NA> I just picked up an IBM LaserPrinter E, and was wondering
NA> about its capabilities, speed, etc? And is there a way to
NA> make it do a self-test? (ie, print out a test pattern?).
I think it is a great printer. Specific and OMNI drivers from IBM's
site. Graphics, Plotter, PostScript HP emulation etc. Try;
HOLD Start/Stop and power up the printer for a test pattern
HOLD Print/Check for a HEX trace print
I'll image my quick reference card and e-mail that to you if you are
interested - otherwise, ask at the local IBM office for one.
___
X KWQ/2 1.2i X I haven't reached this advanced age - by giving advice
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Peter French 05-Dec-99 00:00:02
To: Eddy Thilleman 05-Dec-99 00:00:02
Subj: r0stub.sys
On 1999/12/02, Eddy Thilleman wrote to Rob Basler on message number 294;
Eddy,
ET>
ET> Thanks. My soundcard is crystal based, not a creative labs.
Excuse the butting in on a thread that doesn't concern me :) did you
know: A new mixer for Crystal Semiconductor drivers is available from
Hobbes under name:
http://hobbes.nmsu.edu/pub/incoming/lbmix001.zip
This mixer works with IOCTL category 90 mixer API implemented in
Crystal v.2.08 and v.3.02 drivers (and probably later versions).
___
X KWQ/2 1.2i X The biggest room in the world is the room for self-improvement
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: John Thompson 04-Dec-99 16:07:00
To: Rachel Veraa 05-Dec-99 03:22:00
Subj: off-topic, please forgive
In a message to Holger Granholm, Rachel Veraa wrote re: HPFS Filenames to
Windows
RV> It's Kreyòl, the language of Haiti.
RV>
RV>
RV> N'a pale pi ta,
RV> Rachel
RV>
RV> http://www.netside.net/~rveraa/
RV> * Origin: Birdsoft - North Miami (1:135/907)
Off topic, but I've been meaning to ask for a while. Are you any
relation to Rich Veraa who long, long ago used to post in FIDO
Science echo (and elsewhere)? Also from Miami area, IIRC, and
also seemed to have a fascination with birds.
Reply to email below if you prefer...
* KWQ/2 1.2i * Internet: John.Thompson@attglobal.net
--- PCBoard (R) v15.3/M 10
* Origin: Spare Parts BBS - Appleton WI (920-731-7697) (1:139/0)
103
+----------------------------------------------------------------------------+
From: Holger Granholm 04-Dec-99 20:01:00
To: Eddy Thilleman 05-Dec-99 03:22:00
Subj: DELTREE
In a message dated 12-02-99, Eddy Thilleman said to Holger Granholm:
HG> AFAIK deltree is a DOS program and consequently it was a FAT patition.
ET>That still leaves one question I asked to be answered: was it run
ET>under plain DOS booted (=not under OS/2) without a disk cache?
YES!
Happy Holidays,
Holger
___
* MR/2 2.26 * Why look thru Windows? Open the door to the future: OS/2
--- PCBoard (R) v15.22 (OS/2) 2
* Origin: Coming to you from the Sunny Aland Islands. (2:20/228)
+----------------------------------------------------------------------------+
From: Holger Granholm 04-Dec-99 20:01:00
To: Lee Aroner 05-Dec-99 03:22:00
Subj: HPFS Filenames to Window
In a message dated 11-29-99, Lee Aroner said to Rachel Veraa:
RV> N'a pale pi ta,
LA> ^^^^^^ Swazi ? Zulu?
ROTFL !
Happy Holidays,
Holger
___
* MR/2 2.26 * If you want it done right, forget Microsoft.
--- PCBoard (R) v15.22 (OS/2) 2
* Origin: Coming to you from the Sunny Aland Islands. (2:20/228)
+----------------------------------------------------------------------------+
From: Will Honea 05-Dec-99 01:45:00
To: Herbert Rosenau 05-Dec-99 01:45:00
Subj: Clunker update
Herbert Rosenau wrote to Jonathan de Boyne Pollard on 12-05-1999
HR> A window that dosn't own the focus can't receive any
HR> message from system queue. Bercaus PM sends this only to a
HR> window that owns the focus - or has to own after the focus
HR> change sequence (its an atomic sequence) is done.
Not true. It will not receive mouse or keyboard messages but it sure
as heck gets WM_COMMAND and WM_SYSTEM meaasges even if hidden and/or
disabled! I use non-visible (hence no focus) windows to syncronize and
dispatch message results from a network worker thread all the time.
Will Honea <whonea@codenet.net>
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Andy Roberts 04-Dec-99 13:41:11
To: Holger Granholm 05-Dec-99 06:43:20
Subj: USB
Holger Granholm,
03-Dec-99 21:10:00, Holger Granholm wrote to Andy Roberts
HG> In a message dated 12-01-99, Andy Roberts said to Holger Granholm:
Subject: USB
HG>>> Another question: Any hints on USB support in Warp 4?
AR>> If you look on that CD you just got from me:
AR>> Usbcom02.Zip was just announced by Pete Norloff, so it may not be on
AR>> that CD.
HG> Just checked, it isn't but I'll await your reply to the previous
HG> reply.
If that's the file you need, then I'll send it to you via E-Mail File Attach.
I may be proven wrong in the long run, but my feeling about USB is in the same
class with VLB, which was only dominate for the 486 and mostly abandoned for
the Pentium, which forced a lot of very expensive VLB HW to become obsolete.
Granted PCI has advantages over VLB. And I'm sure USB has it's good points.
But I have no intention of throwing away my ISA and SCSI HW and jumping on the
USB bandwagon, just because some OEMs are trying to push new standards in an
effort to sell more HW. And from what I've seen of rapid USB driver
replacements, I'm not so sure they have all the bugs worked out. Fortunately
so far SCSI has not been abandoned. So If I have a choice of getting a new
device for SCSI or USB, then SCSI will win. Granted that does not solve the
problem of fewer ISA slots in some of the new MoBos. But there are still some
MoBos with a couple of ISA slots. I'm not sure what is going to be developed
to replace the Pentium. Frankly I'm surprised it is not already here,
considering how fast OEMs moved to dump the 486. I'm not sure there is going
to be a smooth upgrade path for USB any more than there was for VLB. IMO USB
is a lot of development by marketing staff. Thus I'm not impressed with USB.
Thanks and Good Luck, Andy Roberts
andy@shentel.net
--- Terminate 5.00/Pro*at
* Origin: OS/2: penthouse. DOS: poorhouse. Windows: outhouse. (1:109/921.1)
+----------------------------------------------------------------------------+
From: Rich Wonneberger 05-Dec-99 10:59:28
To: All 05-Dec-99 13:33:05
Subj: Kodak DVC-323 Camera
I know OS/2 has USB support now, but does anyone know if a Kodak DVC-323
camera will work with it??
Next, all I want to do is snap a picture every minute or so (over write the
old one). Is there any simple software for this??
If I backup my CONFIG.SYS file and install the USB support and it doesnt work,
will restoring the CONFIG.SYS file and re-booting put me back to where I was
before??
I -dont- have Windy support installed. Would prefer a OS/2 solution.
TIA
Rich
I-Net turtil@frontiernet.net
... Can I call you Ms. Dos?
---
* Origin: Turtil's Pond BBS. Monroe NY 914 783-2106 (1:2625/50)
+----------------------------------------------------------------------------+
From: Herbert Rosenau 05-Dec-99 15:04:21
To: Eddy Thilleman 05-Dec-99 13:33:05
Subj: cache
ET> Is there an advantage to have more than one lazy write workers on
ET> the HPFS cache?
run=f:\os2\cache.exe /LAZY:9 /MAXAGE:12500 /DISKIDLE:7500 /BUFFERIDLE:2000
/READAHEAD:1
ET> Does this help with the performance when writing to disk (HPFS
ET> partition)?
It depends on your system usage. The line above is optimised to have the
highest possible throuput on my ISDN lines under cantaloup (OS/2 PM FIDO
mailer).
Yes, disk caching is the most recent parameter on it.
--- Sqed/32 1.15/development 499:
* Origin: WIN95 - nach 32 BIT kann ich auch alles. (2:2476/493)
231/992
+----------------------------------------------------------------------------+
From: Herbert Rosenau 05-Dec-99 14:48:14
To: Stewart Honsberger 05-Dec-99 13:33:05
Subj: Install
LP>>> FILES=20
HR>> Should at least 90
SH> Why? I've never had a problem. Besides, if you get a DOS app that
SH> needs more, just change it for that specific VDM.
Yes, you my change it for each DOS/Win program separatly. But it's better to
have a more practical value as default. You would omit some unwanted problems.
You can do this under MDOS painless because MDOS presents you more lower (and
upper) memory as each standalone DOS can do.
SH> No need to chew memory needlesly.
LP>>> SWAPPATH=d:\ 4096 10240
HR>> 20480 10240
SH> I don't think that (the first value) needs to be set quite that
SH> high. I've got mine at 16MeB's right now, which should give me
SH> plenty of time to start killing errant apps before I overflow.
It should be quite higher. Because this is the point OS/2 will warn you if the
FREE room on disk containing swapper.dat sinks under that limit. On an I386/16
and old, slow disks 2M was enough. On a PII it will you let STOP the system
before you can see a warning. If you swapper is on a (logical disk) with a lot
of free place let the system the chance to warn you before it has to stop.
In case of low memory OS/2 does nothing as to swap out until the disk is full.
If the disk is full and the swapper can't grow the stystem stops hard.
If the free space on disk shrinks below the warn limit a separate thread is
started to warn you for that situation and give you the chance to end or kill
some applications to make room in virtual addresspace to continue.
If the limit is too small the growing process goes on an the system my stop
before you can ever seen the warning. It is not enough to *see* the warning
*you* need time to register it, check the running processes, save pending data
in your applications..... Therefore you need any second the system can give
you at this moment. There is nothing that will stop the forthgoing allocation
after the appears other than YOU. It is only on you to break that by ending
all well behaved applications or killing the one that does illegal consumes
the memory.
OS/2 can address 4GB RAM - and if not enough real RAM is available it tries to
use disk space instead. On a modern processor with modern disks this can be 1
GB/s. If you disk (the swapper resides) is big enough to fit the whole 4GB
addressroom you'll never see the warning. If not it depends on the memory your
applications can use. You're right if you think this can never occure on your
system - but in an unwanted ituation it my occure. It is nothing than a last
chance to hold your system running in a purly seldom situation.
I've got here a PII 450 with 256 MB RAM + up to 600 MB free room for swapper -
but can find quickly a situation where the system goes out of memory and stops
without any warning - if I not set the warn limit high enough.
SH> Then again, I've got a swapfile and drivespace monitor on my WPS,
SH> so I'd be an idiot to miss the bars moving up and down
SH> respectively :>
Hi, hi. The monitor can't warn you right. If YOU're busy you dont look on it.
If the system has to warn you it will do it dramatically - a VIO fullscreen
session appears with highest priority - and you have to swith back to your
applications to do something.
LP>>> THREADS=256
HR>> 512
SH> Again - why? I'm at 256 and have never once come close to running
SH> out, and I've even tried. :>
Inside the system is a limited area of management data. This area is created
during boot time and can't grow. The Thread-/processes table is one of them.
The parameter threads includes ALL: any process (per se 1 thread,
any thread that can started from an process, and all modern apps are
multithreaded and most of them starts multiple threads on demand.
You should not run hard on any limit because if you're always near that you my
quickly run out of it. Some application doesn't check all and every error.
Thereby normally a thread start goes well. But if threads is to small it fails
- and the application too. Do you like to lose data?
All three parameters make your system savelier. They help you to work well in
case of low resources.
--- Sqed/32 1.15/development 270:
* Origin: Bitte beachten Sie die zweite Seite! (2:2476/493)
231/992
+----------------------------------------------------------------------------+
From: Herbert Rosenau 05-Dec-99 14:51:27
To: Dave Davidson 05-Dec-99 13:33:05
Subj: Netscape....
DD> After switching from WIN98/IE environment to OS/2 & Netscape, I
DD> miss my rather extensive "Favorites" folder of URL's.
DD> Is there any way to convert or import MS's IE bookmarks to OS/2's
DD> Netscape? There's gotta be a way, I just haven't figured out
DD> how....yet.
NS bookmarks are pure HTML.
--- Sqed/32 1.15/development 67:
* Origin: Zwei Ohren hoeren besser als vier Augen. (2:2476/493)
231/992
+----------------------------------------------------------------------------+
From: Kees Bergwerf 04-Dec-99 11:14:22
To: All 05-Dec-99 13:33:05
Subj: not enough diskspace
Hello All!
I tried to install a network card..
After a reboot I got a message that I don't have enough disk space to handle
the locked files. But there is still 217 MB free on my C drive!
Also my startup.cmd was changed by the setup program (everything is
capitalised) and I got a lot of errors when rebooting after the install,
because my startup.cmd was not executed properly.
But why are those locked files not handled? The next boot does not give any
message after locked files at all. But when they are not properly handled, why
does OS/2 remove the locked files device driver?
I use Warp4 US, fixpack12, on a pentium II/400
Kees
---
* Origin: Trefpunt BBS Den Haag +31-70-3967407 (2:280/1507)
+----------------------------------------------------------------------------+
From: Ian Moote 05-Dec-99 10:30:00
To: HOLGER GRANHOLM 05-Dec-99 13:33:05
Subj: Creole or whatever!
HG> RV>It's Kreyòl, the language of Haiti.
HG>
HG> Thank you Rachel. Now everybody reading this echo knows it.
HG>
HG> However, you'll have to answer the same question when new users
HG> join.
As interesting as this topic is...!! [:/
---
■■ Vote for Independence - it beats having to fight for it. RAH
--- AdeptXBBS v1.11y (FREEWare/2)
* Origin: Moote Pointe (1:2424/140)
231/992
+----------------------------------------------------------------------------+
From: Ian Moote 05-Dec-99 10:30:00
To: LEE ARONER 05-Dec-99 13:33:05
Subj: WarpCenter INI file ?
LA> IM> Back in April John Angelico was kind enough to inform me that
[...]
LA> And so they are!
LA>
LA> Info filed away and thanks Ian!!
Thank John! [:) All I did was regurgitate. [;) Take care and TTYL.
---
■■ Veni, vidi, virtual -- I came, I saw, I went remote.
--- AdeptXBBS v1.11y (FREEWare/2)
* Origin: Moote Pointe (1:2424/140)
231/992
+----------------------------------------------------------------------------+
From: Bob Wright 26-Nov-99 20:58:16
To: Holger Granholm 05-Dec-99 13:33:05
Subj: Installation problem
Greetings, Holger...
Holger Granholm hastily said to Jack Stein:
JS>> CFGINFO7.ZIP OS/2 Config.sys Optimizer! Sysop Recommended! (188K)
HG> Where can *I* grab a copy of that? Have nr. 6.
HG> FTP or Telnet preferred.
Hobbes... directory pub/os2/util/config. The main new thing is that it
contains a new version of the data file (os2cfg16). The main executable is
still Rick's original dated in June of 95.
-- Bob
--- GoldED 2.41
* Origin: Merlin's Tower - Surrey, BC (1:153/944)
103
+----------------------------------------------------------------------------+
From: Bob Wright 27-Nov-99 18:28:02
To: Andrew Belov 05-Dec-99 13:33:05
Subj: odin-19991112
Greetings, Andrew...
Jonathan de Boyne Pollard said to Andrew Belov:
JdBP> ( I couldn't tell you the exact minimum OS/2 Warp 3 fixpack number for
JdBP> the most recent Open32 updates. Someone here who is still using OS/2
JdBP> Warp 3 might be able to, though. )
The readme.1st for fp 40 references installation of Open32 in its notes.
However, the latest APAR that I could find that specifically mentions
Open32(in read.me2) was from fp30.
-- Bob
--- GoldED 2.41
* Origin: Merlin's Tower - Surrey, BC (1:153/944)
103
+----------------------------------------------------------------------------+
From: Wes Newell 05-Dec-99 11:36:16
To: All 06-Dec-99 00:14:21
Subj: DELTREE
My dos 6.22 deltree command works quite well on W4. I don't have msdos
installed. All my drives are hpfs. I can run it from an os/2 session (which
automatically brings up a dos vdm), or of course I can run it from a dos vdm.
--- Maximus/2 3.01
* Origin: Wylie Connection 128K ISDN-V34+ DS 972-429-7005 (1:124/7028)
231/992
+----------------------------------------------------------------------------+
From: Russell Tiedt 04-Dec-99 07:48:25
To: Lee Aroner 06-Dec-99 09:49:05
Subj: HPFS Filenames to Window
Lee Aroner wrote in a message to Rachel Veraa:
RV> N'a pale pi ta,
LA> ^^^^^^ Swazi ? Zulu?
Not Swazi or Zulu. :-))
Go well,
Russell
--- LoraBBS-OS/2 v2.42B1+
* Origin: Rusty's BBS - Bloemfontein, Free State, South Africa (5:7106/23)
+----------------------------------------------------------------------------+
From: Bat Lang 05-Dec-99 03:05:21
To: Peter French 06-Dec-99 09:49:05
Subj: cache
-=> Quoting Peter French to Eddy Thilleman, [03 Dec 99 17:27:00] <=-
ET> Is there an advantage to have more than one lazy write
ET> workers on the HPFS cache? Does this help with the
ET> performance when writing to disk (HPFS partition)?
PF> I was told by Denis Tonn that there is an optimum - too many can
PF> also degrade performance. For my 96MB system he suggested:
PF> DiskIdle: 30000 milliseconds
PF> MaxAge: 60000 milliseconds
PF> BufferIdle: 15000 milliseconds
PF> Cache size: 2048 kbytes
PF> 3 Lazy write worker(s) are enabled.
PF> 1 Read ahead worker(s) are enabled.
PF> Relationship as DiskIdle=2*BufferIdle, Maxage=2(to 5)*DiskIdle
Where is this information 'entered' into your configuration? Thanks.
Happy Holydays! & Good Modeming! /\oo/\
... FidoNet-Mail: 1:382/92 or E-mail: Bat.Lang@92.ima.infomail.com
--- Blue Wave/DOS v2.30
* Origin: Rendezvous!! 8gigs_20000files_500echoareas 512-303-1324 (1:382/92)
231/992
+----------------------------------------------------------------------------+
From: Eddy Thilleman 04-Dec-99 11:22:15
To: Gerard Zoer 06-Dec-99 09:49:05
Subj: wave files?
Hello Gerard,
03 Dec 99 08:31, Gerard Zoer wrote to Eddy Thilleman:
GZ> Over here. WIN95S.RAR
Got it, thanks! ;-))
Greetings -=Eddy=- email: eddy.thilleman@net.hcc.nl
... WinErr #014: Impossible error. This cannot really happen.
--- GoldED/2 3.0.1
* Origin: Windows98 is a graphic DOS extender (2:280/5143.7)
+----------------------------------------------------------------------------+
From: Herbert Rosenau 06-Dec-99 12:08:06
To: Will Honea 06-Dec-99 11:47:12
Subj: Clunker update
WH> Herbert Rosenau wrote to Jonathan de Boyne Pollard on 12-05-1999
HR>> A window that dosn't own the focus can't receive any
HR>> message from system queue. Bercaus PM sends this only to a
HR>> window that owns the focus - or has to own after the focus
HR>> change sequence (its an atomic sequence) is done.
WH> Not true.
True.
WH> It will not receive mouse or keyboard messages but it sure as
WH> heck gets WM_COMMAND and WM_SYSTEM meaasges even if hidden and/or
WH> disabled!
Who is forwarding them? Any window can send/post such messages to any other
window. Neither WM_COMMAND nor WM_SYSTEM are generated in system message
queue. Tey are generated by an frame window related on WM_MOUSE.../WM_CHAR
received from system message queue. You can send/post any message to any
window. So you my send/post a WM_COMMAND from any window to another to become
the action you would.
It is usual to interact between serval windows (of serval applications) this
way.
WH> I use non-visible (hence no focus) windows to syncronize and
WH> dispatch message results from a network worker thread all the
WH> time.
Yeah, Your window procedure sends it to it. It's quite legal to do so!
--- Sqed/32 1.15/development 142:
* Origin: Ginseng - die Wurzel fuer die Wurzel. (2:2476/493)
231/992
633/260
2501/209
+----------------------------------------------------------------------------+
From: Kees Bergwerf 05-Dec-99 01:38:08
To: All 06-Dec-99 13:45:21
Subj: not enough diskspace
Hello All!
Saturday December 04 1999 11:14, Kees Bergwerf wrote to All:
problem solved! :-)
KB> After a reboot I got a message that I don't have enough disk space to
KB> handle the locked files.
I removed thesus5.sys ene os20emu.sys from config.sys
i also switched program commander off.
Now the network software is installed correctly (i think it is; no more
messges about locked files that can't be replaced).
Program commander is working again without trouble. I think I will not use
theseus5 again. It was neccesary because of sysbench and memsize (and memsize
did give nothing but trouble: it worked fine for a while but I tried to change
a setting in the config: use theseus, and then the program crashed and I have
not been able to start it again without crashing.)
Kees
---
* Origin: Trefpunt BBS Den Haag +31-70-3967407 (2:280/1507)
772/1
+----------------------------------------------------------------------------+
From: Lee Aroner 02-Dec-99 18:36:00
To: Will Honea 06-Dec-99 14:14:26
Subj: WarpCenter INI file ?
WH> Lee Aroner wrote to All on 11-28-1999
LA> Anyone know what the WarpCenter INI file is?
LA>
LA> Had a crash today and wound up having to install from backup
LA> because I conldn't find any obvious file to restore the only
LA> broken part - the WarpCenter.
WH> Don't think there is one, Lee. Some of the stuff is kept in the
> OS2.INI but it appears that most of the Warpcenter stuff is in the
> \os2\dll\dockxx.cfg files (all that marvelous documentation helps -
> sure!). Only way I've found to recover is to a: restore an archived
> desktop during boot or b: delete the dockxx.cfg files and start over or
> c: restore the whole thing from backup or d: PUNT!
I suspect that restoring the dockxx.cfg's would'a done the trick,
WC came up, it just complained about corrupted config files and
then loaded a blank default config.
Anyways, I had a fresh backup, just zapped the OS2 tree back in
and was up and running in 15 minutes...
Thanks for the feedback!
LRA
-- SPEED 2.01 #2720: Apathy Error: Don't Bother Striking Any Key
--- Maximus/2 3.01
* Origin: Top Hat BBS (1:343/40)
278/111
+----------------------------------------------------------------------------+
From: Lee Aroner 02-Dec-99 18:16:01
To: Scott Jones 06-Dec-99 14:14:26
Subj: WarpCenter INI file ?
-=> On 28 Nov 99 16:38:00, Lee Aroner wrote to All <=-
LA> Anyone know what the WarpCenter INI file is?
LA> Had a crash today and wound up having to install from backup
LA> because I conldn't find any obvious file to restore the only
LA> broken part - the WarpCenter.
SJ> The Warpcenter consists of (all in x:\OS2\DLL) SCENTER.CFG, SCENTER.DLL,
> and DOCK*.CFG.
Thanks Scott !!
LRA
-- SPEED 2.01 #2720: And the RESET button lets you re-run AUTOEXEC.BAT
--- Maximus/2 3.01
* Origin: Top Hat BBS (1:343/40)
278/111
+----------------------------------------------------------------------------+
From: Lee Aroner 02-Dec-99 18:48:02
To: Jonathan De Boyne Pollar 06-Dec-99 14:14:26
Subj: Install
LA>> This is the usual case of MS's "Do as I say, not as I do", since
LA>> Command.Com continues to use FCBs for fast directlry deletions,
LA>> just as I do.
LE>> Try it under MS-DOS v6.x. Then try it in a Win 95 or 98 DOS "window"
LE>> (or with the system booted to the MS-DOS 7 that Win 9x runs on top of).
LA> You might want to try that yourself...my routines have been used
LA> under those conditions for years.
JdBP> I think that Leonard is trying to make the point that using
> FCBs for "fast deletions" is pointless in those
> environments, because it *isn't* actually faster that doing
> things the more up-to-date way using a simple
> findfirst/findnext loop.
I *have* compared it Johnathan, and it's a whole big pile faster
than running a loop, which, of course, is the backup routine in
case the drive in question is HPFS (since warp intentionally
traps if you try this on HPFS with a wildcard spec).
Think about it...which is faster, looping 500 times to do a
findnext/handle delete, or once to nuke the entire directory
contents?
If BillieSoft had come up with some magical way to duplicate the
speed without using FCBs, they would have removed this from their
CLI a long time ago...
LRA
-- SPEED 2.01 #2720: Thank you for pressing the self destruct button...
--- Maximus/2 3.01
* Origin: Top Hat BBS (1:343/40)
278/111
+----------------------------------------------------------------------------+
From: Lee Aroner 03-Dec-99 18:15:00
To: Sandro Coana 06-Dec-99 14:14:26
Subj: WarpCenter INI file ?
SC> Hello Lee Aroner,
LA> Anyone know what the WarpCenter INI file is?
LA> Had a crash today and wound up having to install from backup
LA> because I conldn't find any obvious file to restore the only
LA> broken part - the WarpCenter.
SC>
> Backup Warpcenter.CMD
SC> @echo off
> rem ****************** Backup Warpcenter *****************
> copy c:\os2\dll\dock*.cfg c:\warpctr
> copy c:\os2\dll\SCENTER.CFG c:\warpctr
Thanks for the suggestion Sandro !!
LRA
-- SPEED 2.01 #2720: White dwarf seeks red giant for binary relations.
--- Maximus/2 3.01
* Origin: Top Hat BBS (1:343/40)
278/111
+----------------------------------------------------------------------------+
From: Don Guy 06-Dec-99 08:14:10
To: Eddy Thilleman 06-Dec-99 14:14:26
Subj: wave files?
Greetings Eddy!
A long time ago, in a galaxy far, far away, a coded message from Eddy
Thilleman to All was intercepted...
ET> W95.WAV 2009650 Nice parody on the Rolling Stones song
ET> Start me up that Microsoft used for their
ET> W'95 campaign. Time 1:31.13
ET> Greetings -=Eddy=- email: eddy.thilleman@net.hcc.nl
On its way to the e-mail address above...
-Don
... "Bother," said Pooh, as he deleted his source code.
---
* Origin: EI/2 [Carleton Place, Ontario, Canada] (1:249/176)
+----------------------------------------------------------------------------+
From: Cyrill Vakhneyev 06-Dec-99 13:19:17
To: Linda Proulx 06-Dec-99 15:54:18
Subj: Newer update
Hello Linda!
04 Dec 99 13:52, Linda Proulx wrote to All:
LP> It seems that the install disks programs are too old for the hardware.
Which install disks and which hardware?
LP> Getting newer disk image for the install disks. Hoping that these
LP> will solve the install problems with fdisk.
Get latest ibm1s506.add (idedasd.exe at IBM's DriverPack). RTFM
Bye!
Cyrill [Team OS/2 CV004]
... You said Windows was a Power Tool???
---
* Origin: I feel like Popeye! (2:5053/7.1)
278/111
+----------------------------------------------------------------------------+
From: Cyrill Vakhneyev 06-Dec-99 13:23:08
To: Rich Wonneberger 06-Dec-99 15:54:18
Subj: Kodak DVC-323 Camera
Hello Rich!
05 Dec 99 10:59, Rich Wonneberger wrote to All:
RW> I know OS/2 has USB support now, but does anyone know if a Kodak
RW> DVC-323 camera will work with it??
Did you try this. Maybe it helps...
8< === Begin OS/2 Clipboard === >8
Upload Information Template for Hobbes.nmsu.edu
===============================================
Archive Filename: dcitu18e_beta.zip
Short Description: Digital Camera Image Transfer Utility for OS/2
Long Description: OS/2 PM application to allow serial port transfer
of
images from the following digital camera models: Kodak DC25, Kodak DC120,
Kodak
DC200, Kodak DC210, Kodak DC215, Kodak DC220, Kodak DC240, Kodak DC260, Kodak
DC265, Kodak DC280, Agfa ePhoto, Epson PhotoPC, Minolta Dimage, Nikon Coolpik,
Olympus, Sanyo VPC/DSC, Sierra SD640 and Toshiba PDR-2
Proposed directory
for placement: /pub/os2/apps/mmedia/video/capture
Your name: Stephane Charette
Email address: charette@writeme.com
Program contact name: (same)
Program contact email: (same)
Program URL: http://users.uniserve.ca/~software/dcitu/index.html
Would you like the
contact email address
included in listings? yes
Operating System/Version: OS/2 v3.x and higher
Additional requirements: supported digital camera
Replaces: dcitu*.zip
_________________________________________________________________________
! !
! DCITU v1.8e [beta] - Digital Camera Image Transfer Utility for OS/2 !
!_________________________________________________________________________!
This application was written in my spare time from information
gathered on various WWW sites.
Previous versions of this tool (once upon a time, back in 1997 when I
was single and still had lots of free time on my hands) were called
"DC210" since it was originally written specifically for use with
Kodak's DC210 camera. More than 35 digital cameras are now supported,
not to mention the fact that it now has a graphical user interface,
on-line context-sensitive help, support for thumbnails, etc...!
_________________________________________________________________________
! !
! New in this beta release !
!_________________________________________________________________________!
- scripts can be run in foreground or background
- "select all", "select none" and "select toggle" are now on a thread
to help speed up system response time with hundreds of images
- various small bug fixes
_________________________________________________________________________
! !
! Quick notes for those who cannot wait to get started !
!_________________________________________________________________________!
- type "DCITU.EXE" to start; there are no command-line parameters
- verify the options and select your camera type in Settings->Options
- click on Camera->Connect to get started
_________________________________________________________________________
! !
! Contact information !
!_________________________________________________________________________!
The author of DCITU can be contacted at charette@writeme.com. I love
getting e-mail from people who let me know what type of camera they're
currently using with DCITU! (Hint, hint!)
DCITU's web page is http://users.uniserve.ca/~software/dcitu/index.html
Please consult the web site for up-to-date information, including the
full list of cameras and models that are known to work with DCITU.
I will gladly work with anyone who has suggestions or trouble using
DCITU, regardless of whether or not you have registered. My goal is
to write simple-to-use software that works for everyone.
_________________________________________________________________________
! !
! OS/2 revisions supported !
!_________________________________________________________________________!
DCITU should work with any version of OS/2 starting with v3.0.
_________________________________________________________________________
! !
! Camera models supported !
!_________________________________________________________________________!
DCITU was written for use with the following cameras:
- Kodak DC220, Kodak DC260, Kodak DC265, Minolta Dimage:
1) select "Digita" as the camera type
2) thumbnails are only in grayscale (this is being worked on)
3) some thumbnails may not work (this is being worked on)
4) camera must be set to "connect" mode
- Kodak DC240 & Kodak DC280
1) camera must be set to "connect" mode
- Kodak DC200, Kodak DC210 & Kodak DC215:
1) infra-red transfers not supported
2) camera must be set to "connect" mode
- Kodak DC120:
1) albums not supported; images must be saved/moved to "NO ALBUM"
2) thumbnails are not supported
3) image delete is not supported
4) attach cable, slide cover to "ON/OPEN", click "FILE->CONNECT"
5) there is a bug if more than 12 images are in the camera (this
is being worked on)
- Kodak DC25:
1) also download "KDC_DC2.ZIP" to convert .dc2 image files
2) supports both internal and external memory image files
3) image delete is not supported
4) date and time not supported
- Agfa ePhoto, Epson PhotoPC, Nikon, Olympus, Sanyo VPC/DSC, Sierra
SD640 & Toshiba PDR-2 (cameras known as Project/Protocol "O")
1) some models may require a 2 or 3 second timeout period
2) some models may require the "alternate startup" to be selected
3) some models may require a pause between commands
4) date and time not supported
- Casio:
1) these cameras are no longer supported
_________________________________________________________________________
! !
! Use of this software !
!_________________________________________________________________________!
This application is fairly straight-forward to use.
Basically:
1) make certain your camera is plugged in using the serial cable
2) turn on the camera
3) set the camera to serial connection mode (if applicable)
4) run "DCITU.EXE"
5) verify the settings in the options notebook
6) click on "OK" to close the options notebook
7) select "Connect" from the menubar
+--NOTE TO LAN SERVER AND OS/2 PEER USERS-----------------------------+
! !
! If you mount a serial port over the network, you can download !
! images onto a computer while the camera is hooked up somewhere !
! else on the network. For example, on my home network, I have the !
! camera hooked up to serial port 1 of one particular computer while !
! I connect to a Peer redirected COM port from a second computer. !
! !
+---------------------------------------------------------------------+
Starting with version 1.8a, a new command-line switch has been added
to allow loading the .INI settings from a specific drive, directory,
or .INI file. Use the parameter /i=x:\foo\bar.ini to specify the
file to use. One such example would be:
dcitu.exe /i=c:\apps\public\myfile.ini
Starting with version 1.8d, a new setting in the .INI file has been
included which is *not* viewable with the DCITU options notebook.
Open the DCITU.INI file using an OS/2 INI editor such as REGEDIT2.EXE
and view the setting called "Queue Size Increase". This value, which
defaults to "100", dictates how the message queue should be increased.
This number *must* be larger than the number of images that DCITU
deals with. Eventually -- as time permits -- a new control will be
created in the Options Notebook for this setting.
_________________________________________________________________________
! !
! Distribution and registration !
!_________________________________________________________________________!
This application is distributed as freeware/shareware.
- the freeware version of this application will work for unlimited
time at a maximum transfer speed of 9600 baud; you are NOT required
to register the freeware version, and you will still receive any
technical support that I can reasonably offer over e-mail.
- for faster transfer speeds, a registration fee is requested; when
payment is received, you will be sent a registration number which
allows you to use transfer rates as high as 230400 (on cameras and
computers that support such transfer rates).
For registration information, please see the REGISTER.TXT file.
_________________________________________________________________________
! !
! Disclaimer !
!_________________________________________________________________________!
I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT CAN OCCUR FROM USING THIS
APPLICATION. YOU ACCEPT WHATEVER RISKS INVOLVED, INCLUDING BUT NOT
LIMITED TO, DAMAGES TO BOTH YOUR COMPUTER AND YOUR DIGITAL CAMERA.
On a lighter note: I am not aware of any damages that _could_ occur
from using this application. I have been using it on my own systems
with a Kodak DC260, Kodak DC240, Kodak DC210, and an Olympus D220, all
without problems. Other camera models were tested by various people
contacted through the internet.
_________________________________________________________________________
! !
! Legal notice of contributions !
!_________________________________________________________________________!
Kodak DC220 & DC260 camera support is based in part on documentation
made available on the DIGITA digital camera operating system and by
initial programming efforts by David LaRue from david.larue@acm.org
Kodak DC280 camera support is based in part on Eastman Kodak's
"DC280 Host Interface Specification" documentation at www.kodak.com
Kodak DC240 camera support is based in part on Eastman Kodak's
"DC240 Host Interface Specification" documentation at www.kodak.com
Kodak DC200, DC210 & DC215 camera support is based in part on Eastman
Kodak's "DC210 Host Interface Specification" documentation at
www.kodak.com
Kodak's DC120 .KDC file format support is based in part on
documentation from www.hamrick.com/dc120
Kodak's DC20/25 camera support is based in part on documentation
from home.t-online.de/home/Oliver.Hartmann/dc20prot.htm
"Project O" camera support is based in part on documentation
from www.best.com/~rudnicki/olycmd.html
Thumbnail support for "Project O", Kodak DC240 & Kodak DC280 cameras
is based in part on the work of the Independent JPEG Group at
ftp.uu.net/graphics/jpeg
_________________________________________________________________________
! !
! End of README.TXT !
!_________________________________________________________________________!
8< === End OS/2 Clipboard === >8
Bye!
Cyrill [Team OS/2 CV004]
... "If you can't make it good, make it LOOK good." - B Gates
---
* Origin: I feel like Popeye! (2:5053/7.1)
278/111
+----------------------------------------------------------------------------+
From: Holger Granholm 05-Dec-99 20:45:00
To: Jonathan de Boyne Pollard 06-Dec-99 20:29:01
Subj: HPFS Filenames to Windows
In a message dated 12-02-99, Jonathan de Boyne Pollard said to Holger
Granholm:
RV>> N' = (nou = we
RV>> a = future indicator (shall)
RV>> pale = speak
RV>> pi = more
RV>> ta = late
RV>> [nah pal-AY pee tah]
HG> And what language is that? Miamish?
JP>It looks like French spelled phonetically and slightly mangled.
JP>"Nous allons parler plus tard"
JP>Given that, my guess is that it's some form of creole.
Hi Jonathan,
As you have already seen, you're right. But what if we all would start
finishing our messages with some local abracadabra?
Happy Holidays,
Holger
___
* MR/2 2.26 * Help you out? Certainly! Which way did you come in?
--- PCBoard (R) v15.22 (OS/2) 2
* Origin: Coming to you from the Sunny Aland Islands. (2:20/228)
+----------------------------------------------------------------------------+
From: Holger Granholm 05-Dec-99 20:45:00
To: August Abolins 06-Dec-99 20:29:01
Subj: Yet another magazine
In a message dated 12-03-99, August Abolins said to Holger Granholm:
Hello August,
AA>On 11-23-1999 at 07:15:00PM,
AA>Holger Granholm (2:20/228) wrote to All:
HG> It is with deep regret that I can inform that the last OS/2 column in
HG> the Personal Computer World will appear in the January 2000 issue.
AA>There are still quite a few darn good info sources on the web.
There may be but they will never substitute the printed info for me.
And I don't like to spend a lot of time searching and reading on the
web as long as every minute of phone use costs money.
Happy Holidays,
Holger
___
* MR/2 2.26 * Don't diet! Download a virus to destroy the FAT!
--- PCBoard (R) v15.22 (OS/2) 2
* Origin: Coming to you from the Sunny Aland Islands. (2:20/228)
+----------------------------------------------------------------------------+
From: Holger Granholm 05-Dec-99 20:45:00
To: Nick Andre 06-Dec-99 20:29:01
Subj: OS/2 Printer
In a message dated 12-03-99, Nick Andre said to All:
NA>I just picked up an IBM LaserPrinter E, and was wondering about its
NA>capabilities, speed, etc? And is there a way to make it do a
NA>self-test? (ie, print out a test pattern?). Any help appreciated.
Hello Nick,
The self test is usually done by pressing one of the push buttons while
at the same time switching on the printer. That has worked for all the
laser printers I have serviced.
Seasons Greetings,
Holger
___
* MR/2 2.26 * Windows NT: From the makers of Windows 3.1!
--- PCBoard (R) v15.22 (OS/2) 2
* Origin: Coming to you from the Sunny Aland Islands. (2:20/228)
+----------------------------------------------------------------------------+
From: Stewart Honsberger 06-Dec-99 16:23:11
To: Peter Knapper 06-Dec-99 20:29:01
Subj: fdisk /query
04 Dec 99 10:36, Peter Knapper wrote to Jonathan de Boyne Pollard:
PK> Ok, maybe I should have made that "How about mounting other
PK> partitions off the Root (booted) file system (partition) similar to
PK> unix."
You mean like CC: ?
Stewart Honsberger,
blackdeath@tinys.oix.com
... Alcohol: The more you drink, the less you think!
-!- GOPGP/2 v1.23
--- Msged/2 TE 05
* Origin: Blackdeath BBS - Private (1:229/604)
2320/38
+----------------------------------------------------------------------------+
From: Preston Smith 06-Dec-99 18:24:02
To: All 06-Dec-99 23:30:17
Subj: TCPIP Upgrade
Hello All!
I sent this message to both the TEAMOS2 and OS2 e-mail lists on saturday and
no one has responded. Can you folks help?
I decided to try to upgrade my TCPIP version so I downloaded "TCP/IP For
OS/2 V3.1 & V4.0 Universal FixPak UN_0980" to apply to my sytem.
The first thing I see in the readme file is
Note: You should have MPTS FixPak WRx8421 (or above) installed on
your system before applying this FixPak. Also note that WRx8610
should not be installed on a non-SMP Warp Server without installing
TCP/IP v4.1 along with it. There have been various problems reported
when using WRx8610 without TCP/IP v4.1.
Warning: 1 - This FixPak services some of the TCP/IP files based on
the MPTS level on the system. If you have WRx8610 or above on your
system when you install this FixPak, you should not install a version
of MPTS older than WRx8610 because it will back-level some of the
TCP/IP files. If you have an MPTS version prior to WRx8610 when you
install this FixPak and you then install WRx8610, you should
reinstall this FixPak to ensure that the proper TCP/IP files are
installed. If you plan to install WRx8620, it should be installed
after installing this FixPak.
My questions are (results of Syslevel are shown below)
1. Is it normal to see what appear to be duplicate entries in the
Syslevel info? If not, how do I clean it up?
2. I see I have TCPIP 4.00 on my system - should I upgrade to TCPIP 4.1?
3. How do I know what MPTS level is on my system? Should this be upgraded to
WRx842x? or WRx8610 then 8620?
4. Are there any other related upgrades I should install to bring my
communication suite up to date?
Thanks for the help
Preston
D:\INTERNET\NETSCAPE4\PROGRAM\SYSLEVEL.NN2
Netscape Communicator 4.61 for OS/2 Warp (Secured)
Version 4.61 Component ID 5697B8601
Type ASD
Current CSD level: XR00461
Prior CSD level: XR00461
E:\DMISL\SYSLEVEL.DMI
IBM OS/2 DMTF Service Layer
Version 1.10 Component ID 576562200
Current CSD level: CA00000
Prior CSD level: CA00000
E:\IBMCOM\SYSLEVEL.TRP
IBM OS/2 LAN Adapter and Protocol Support
Version 5.10 Component ID 5639A5700
Current CSD level: WR08400
Prior CSD level: WR08210
E:\IBMI18N\SYSLEVEL.I18
IBM I18N Toolkit
Version 1.05 Component ID 5639A5700
Current CSD level: WR08400
Prior CSD level: WR08210
E:\IBMINST\SYSLEVEL.WCB
OS/2 Warp Networking Services Installation
Version 4.00 Component ID 5939a9200
Current CSD level: IP08400
Prior CSD level: IP08400
E:\Java11\bin\SYSLEVEL.JAV
Java Runtime
Version 1.16 Component ID 5639B3300
Current CSD level: XR04006
Prior CSD level: XR04005
E:\Java11\bin\SYSLEVEL.JUF
Java Unicode Font
Version 1.00 Component ID 5639D7200
Current CSD level: XR04005
Prior CSD level: XR04005
E:\MPTN\SYSLEVEL.DHC
IBM OS/2 Dynamic Host Configuration Protocol Services
Version 4.00 Component ID 562290901
Current CSD level: WR08400
Prior CSD level: WR08210
E:\MPTN\SYSLEVEL.MPT
IBM OS/2 TCP/IP Stack
Version 5.10 Component ID 5639B1700
Current CSD level: WR08400
Prior CSD level: WR08210
E:\MPTN\I18N\SYSLEVEL.I18
IBM I18N Toolkit
Version 1.05 Component ID 5639A5700
Current CSD level: WR08400
Prior CSD level: WR08210
E:\opendoc\bin\SYSLEVEL.ODC
OpenDoc
Version 1.00 Component ID 5639B3100
Current CSD level: XR01000
Prior CSD level: XR01000
E:\OS2\DLL\SYSLEVEL.FIA
IBM OS/2 Feature Install
Version 1.22 Component ID 5639C7300
Type ASD
Current CSD level: XR03100
Prior CSD level: XR03100
E:\OS2\INSTALL\SYSLEVEL.BDD
IBM OS/2 Base Device Drivers
Version 4.00 Component ID 5639A6100
Type 0C
Current CSD level: XR0D001
Prior CSD level: XR04000
E:\OS2\INSTALL\SYSLEVEL.FPK
OS/2 Warp 4 Service Level
Version 1.00 Component ID 566933010
Type Fixpak
Current CSD level: XR0M011
Prior CSD level: XR0M011
E:\OS2\INSTALL\SYSLEVEL.GRE
IBM OS/2 32-bit Graphics Engine
Version 4.00 Component ID 5639A6100
Type 0C
Current CSD level: XR04000
Prior CSD level: XR04000
E:\OS2\INSTALL\SYSLEVEL.OS2
IBM OS/2 Base Operating System
Version 4.00 Component ID 5639A6100
Type 0C
Current CSD level: XR0M011
Prior CSD level: XR04000
E:\OS2\INSTALL\SYSLEVEL.SDS
Distributed SOM Framework
Version 2.01.5 Component ID 562222700
Current CSD level: SM20012
Prior CSD level: NONE
E:\OS2\INSTALL\SYSLEVEL.SEM
SOM Event Management Framework
Version 2.01.5 Component ID 562222700
Current CSD level: SM20012
Prior CSD level: NONE
E:\OS2\INSTALL\SYSLEVEL.SIR
SOMobjects Interface Repository Framework
Version 2.01.5 Component ID 562222700
Current CSD level: SM20012
Prior CSD level: NONE
E:\OS2\INSTALL\SYSLEVEL.SRK
SOM Run-time Kernel
Version 2.01.5 Component ID 562222700
Current CSD level: SM20012
Prior CSD level: NONE
E:\OS2\INSTALL\SYSLEVEL.SUT
SOMobjects Utility Classes
Version 2.01.5 Component ID 562222700
Current CSD level: SM20012
Prior CSD level: NONE
E:\TCPIP\bin\SYSLEVEL.DBX
IBM OS/2 TCPIP DOS Windows
Version 4.00 Component ID 5639A6500
Current CSD level: UN00000
Prior CSD level: UN00000
E:\TCPIP\bin\SYSLEVEL.IAK
IBM Internet Connection for Warp
Version 4.00 Component ID 5639A6400
Current CSD level: UN00000
Prior CSD level: UN00000
E:\TCPIP\bin\SYSLEVEL.TCP
IBM TCP/IP for Warp
Version 4.00 Component ID 5639A6600
Current CSD level: UN00000
Prior CSD level: UN00000
E:\TCPIP\pcmos2-\SYSLEVEL.PCS
IBM Personal Communications AS/400 and 3270 for OS/2 - TCP/IP Entry Level
Version 4.10.1 Component ID 5639A3300
Current CSD level: WR00000
Prior CSD level: WR00000
N:\DMISL\SYSLEVEL.DMI
IBM OS/2 DMTF Service Layer
Version 1.10 Component ID 576562200
Current CSD level: CA00000
Prior CSD level: CA00000
N:\IBMCOM\SYSLEVEL.TRP
IBM OS/2 LAN Adapter and Protocol Support
Version 5.10 Component ID 5639A5700
Current CSD level: WR08400
Prior CSD level: WR08210
N:\IBMI18N\SYSLEVEL.I18
IBM I18N Toolkit
Version 1.05 Component ID 5639A5700
Current CSD level: WR08400
Prior CSD level: WR08210
N:\IBMINST\SYSLEVEL.WCB
OS/2 Warp Networking Services Installation
Version 4.00 Component ID 5939a9200
Current CSD level: IP08400
Prior CSD level: IP08400
N:\Java11\bin\SYSLEVEL.JAV
Java Runtime
Version 1.16 Component ID 5639B3300
Current CSD level: XR04006
Prior CSD level: XR04005
N:\Java11\bin\SYSLEVEL.JUF
Java Unicode Font
Version 1.00 Component ID 5639D7200
Current CSD level: XR04005
Prior CSD level: XR04005
N:\MPTN\SYSLEVEL.DHC
IBM OS/2 Dynamic Host Configuration Protocol Services
Version 4.00 Component ID 562290901
Current CSD level: WR08400
Prior CSD level: WR08210
N:\MPTN\SYSLEVEL.MPT
IBM OS/2 TCP/IP Stack
Version 5.10 Component ID 5639B1700
Current CSD level: WR08400
Prior CSD level: WR08210
N:\MPTN\I18N\SYSLEVEL.I18
IBM I18N Toolkit
Version 1.05 Component ID 5639A5700
Current CSD level: WR08400
Prior CSD level: WR08210
N:\opendoc\bin\SYSLEVEL.ODC
OpenDoc
Version 1.00 Component ID 5639B3100
Current CSD level: XR01000
Prior CSD level: XR01000
N:\OS2\DLL\SYSLEVEL.FIA
IBM OS/2 Feature Install
Version 1.22 Component ID 5639C7300
Type ASD
Current CSD level: XR03100
Prior CSD level: XR03100
N:\OS2\INSTALL\SYSLEVEL.BDD
IBM OS/2 Base Device Drivers
Version 4.00 Component ID 5639A6100
Type 0C
Current CSD level: XR0D001
Prior CSD level: XR04000
N:\OS2\INSTALL\SYSLEVEL.FPK
OS/2 Warp 4 Service Level
Version 1.00 Component ID 566933010
Type Fixpak
Current CSD level: XR0M011
Prior CSD level: XR0M011
N:\OS2\INSTALL\SYSLEVEL.GRE
IBM OS/2 32-bit Graphics Engine
Version 4.00 Component ID 5639A6100
Type 0C
Current CSD level: XR04000
Prior CSD level: XR04000
N:\OS2\INSTALL\SYSLEVEL.OS2
IBM OS/2 Base Operating System
Version 4.00 Component ID 5639A6100
Type 0C
Current CSD level: XR0M011
Prior CSD level: XR04000
N:\OS2\INSTALL\SYSLEVEL.SDS
Distributed SOM Framework
Version 2.01.5 Component ID 562222700
Current CSD level: SM20012
Prior CSD level: NONE
N:\OS2\INSTALL\SYSLEVEL.SEM
SOM Event Management Framework
Version 2.01.5 Component ID 562222700
Current CSD level: SM20012
Prior CSD level: NONE
N:\OS2\INSTALL\SYSLEVEL.SIR
SOMobjects Interface Repository Framework
Version 2.01.5 Component ID 562222700
Current CSD level: SM20012
Prior CSD level: NONE
N:\OS2\INSTALL\SYSLEVEL.SRK
SOM Run-time Kernel
Version 2.01.5 Component ID 562222700
Current CSD level: SM20012
Prior CSD level: NONE
N:\OS2\INSTALL\SYSLEVEL.SUT
SOMobjects Utility Classes
Version 2.01.5 Component ID 562222700
Current CSD level: SM20012
Prior CSD level: NONE
N:\TCPIP\bin\SYSLEVEL.DBX
IBM OS/2 TCPIP DOS Windows
Version 4.00 Component ID 5639A6500
Current CSD level: UN00000
Prior CSD level: UN00000
N:\TCPIP\bin\SYSLEVEL.IAK
IBM Internet Connection for Warp
Version 4.00 Component ID 5639A6400
Current CSD level: UN00000
Prior CSD level: UN00000
N:\TCPIP\bin\SYSLEVEL.TCP
IBM TCP/IP for Warp
Version 4.00 Component ID 5639A6600
Current CSD level: UN00000
Prior CSD level: UN00000
N:\TCPIP\pcmos2-\SYSLEVEL.PCS
IBM Personal Communications AS/400 and 3270 for OS/2 - TCP/IP Entry Level
Version 4.10.1 Component ID 5639A3300
Current CSD level: WR00000
Prior CSD level: WR00000
Preston (prsmith@navnet.net)
---
* Origin: Canadian Connection, St Margarets Bay NS (902)826-7774 (1:251/11)
114/477
143/1
5100/8
+----------------------------------------------------------------------------+
From: Linda Proulx 06-Dec-99 16:07:11
To: Cyrill Vakhneyev 06-Dec-99 23:30:17
Subj: Re: Newer update
Greetings and Salutations,
-=> Cyrill Vakhneyev wrote to Linda Proulx <=-
CV> Which install disks and which hardware?
The Blue Connect install disks & the second hard drive on a Asus pentium
board.
LP> Getting newer disk image for the install disks. Hoping that these
LP> will solve the install problems with fdisk.
CV> Get latest ibm1s506.add (idedasd.exe at IBM's DriverPack). RTFM
Thanks for the info. Forwarded to my Inet person for DL.
Anon,
Linda
... Be nice to moderators. They HATE that!
--- MultiMail/MS-DOS v0.32
* Origin: Robin's Universe BBS - Winnipeg MB (1:348/807)
278/111
+----------------------------------------------------------------------------+
From: Stewart Honsberger 06-Dec-99 17:13:24
To: Herbert Rosenau 06-Dec-99 23:30:17
Subj: Install
05 Dec 99 14:48, Herbert Rosenau wrote to Stewart Honsberger:
SH>> Why? I've never had a problem. Besides, if you get a DOS app that
SH>> needs more, just change it for that specific VDM.
HR> Yes, you my change it for each DOS/Win program separatly. But it's
HR> better to have a more practical value as default. You would omit some
HR> unwanted problems.
Maybe it's just because of the small amount of DOS software I use. I've
got all my default settings configure to the minimum values to conserve
as much memory as possible for OS/2 apps.
SH>> I don't think that (the first value) needs to be set quite that
SH>> high. I've got mine at 16MeB's right now, which should give me
SH>> plenty of time to start killing errant apps before I overflow.
HR> It should be quite higher. Because this is the point OS/2 will warn
HR> you if the FREE room on disk containing swapper.dat sinks under that
HR> limit. On an I386/16 and old, slow disks 2M was enough. On a PII it
HR> will you let STOP the system before you can see a warning. If you
HR> swapper is on a (logical disk) with a lot of free place let the
HR> system the chance to warn you before it has to stop.
Put simply - my swapfile has 123MeB's to grow in, from a default size of
32MeB's. If it ever grows that much that quickly, I won't be closing
apps - I'll be three-fingered-saluting the machine post-haste.
LP>>>> THREADS=256
HR>>> 512
SH>> Again - why? I'm at 256 and have never once come close to running
SH>> out, and I've even tried. :>
HR> Inside the system is a limited area of management data. This area is
HR> created during boot time and can't grow. The Thread-/processes table
HR> is one of them.
I realize that.
HR> You should not run hard on any limit because if you're always near
HR> that you my quickly run out of it. Some application doesn't check all
HR> and every error. Thereby normally a thread start goes well. But if
HR> threads is to small it fails - and the application too. Do you like
HR> to lose data?
Like I said - I've never even come close to running out. Running a
personnal system with several apps loaded (ICQ client, MP3 player,
office suite, Fido mailer, VModem, two POP3 mail checkers, RC5 client,
TCP/IP keep-alive, etc..) I haven't even hit 200 yet. If ever I notice
that I'm running out, I might raise it - but in the mean time, why the
overhead?
Stewart Honsberger,
blackdeath@tinys.oix.com
... An animal with two humps is a camel, how about women ...?
-!- GOPGP/2 v1.23
--- Msged/2 TE 05
* Origin: Blackdeath BBS - Private (1:229/604)
2320/38
+----------------------------------------------------------------------------+
From: Rich Wonneberger 06-Dec-99 20:20:24
To: Cyrill Vakhneyev 06-Dec-99 23:30:17
Subj: Kodak DVC-323 Camera
*** Quoting Cyrill Vakhneyev to Rich Wonneberger dated 12-06-99 ***
> Did you try this. Maybe it helps...
(bit del)
> Long Description: OS/2 PM application to allow serial port
> transfer of
> images from the following digital camera models: Kodak DC25, Kodak
> DC120, Kodak
> DC200, Kodak DC210, Kodak DC215, Kodak DC220, Kodak DC240, Kodak DC260,
> Kodak
> DC265, Kodak DC280, Agfa ePhoto, Epson PhotoPC, Minolta Dimage, Nikon
Cyrill,
This looks like its for snap shot type camera with a serial port for x-fering
images. Mine is a DVC which is like a camcorder type camera. Like the c-you
type camera. It's also USB and no serial port.
Thanks anyway
Rich
I-Net turtil@frontiernet.net
... Grape nuts? What do they do with the rest of the grape?
---
* Origin: Turtil's Pond BBS. Monroe NY 914 783-2106 (1:2625/50)
+----------------------------------------------------------------------------+
From: Daniela Engert 05-Dec-99 19:07:26
To: George White 06-Dec-99 23:30:17
Subj: More OS/2 Questions.....
Hi George!
Thus quoth George White to MIKE RUSKAI:
GW> It's a valid number for heads, Jonathan has got it slightly wrong
GW> (a rare event so note it down - but see below), afaiaa the BIOS
GW> INT13 C/H/S access call limits are:-
GW> Cylinders 0 to 1023 = 1024
GW> Heads 0 to 255 = 256
GW> Sectors 1 to 63 = 63
GW> That form of translation on ATA (or IDE if you insist) drives over
GW> 504 MB is used as the ATA C/H/S addressing scheme is limited to
GW> _16_ heads (according to Ralf Brown's Interrupt List it's for
GW> compatibility with the then standard Western Digital WD1003
GW> controller for ST506 interface drives which could only support 16
GW> heads). The alternative for drives over 504 MB is to use LBA
GW> addressing (which is the only way for drives over 8 GB).
I'm sorry, but you mixed up two totally different things:
1) there is the CHS translation visible at the BIOS API as you described with
its value ranges. This translation applies to any sort of transport technology
(SCSI, ATA, ...)
2) there is another CHS translation - or much more correct: addressing scheme
- used on the EIDE channel with these limits:
Cylinders 0 to 65535 = 65536
Heads 0 to 15 = 16
Sectors 1 to 63 = 63
Some BIOS implementations have bugs which prevent the use of 16 logical heads.
So, as you stated, any EIDE command initiator *should* use the LBA addressing
scheme for drives with capacities above 7.8GiB because the ATA spec tells you
so (f.e. Fujitsus just fail if you don't); but the CHS addressing scheme is
good for up to about 31GiB (and f.e. IBMs support that). Any bigger drive
*requires* the LBA addressing scheme.
bye, Dani
--- Sqed/32 1.14/r01354
* Origin: Nachtigall/2,Nuernberg/Ger,+49-911-861319,Z19+ISDN (2:2490/2576)
114/477
143/1
5100/8
+----------------------------------------------------------------------------+
From: Daniela Engert 05-Dec-99 19:19:04
To: Rob Basler 06-Dec-99 23:30:17
Subj: OS/2 3.0 with FP40
Hi Rob!
Thus quoth Rob Basler to Jaap Van.Veen:
JV>>As I have recalled earlier, my system (486DX2 66) is much faster
JV>> with FP40 installed. This has to do with the faster handling of the
JV>> harddisk.
JV>>However during the regular status checks the COM1 port is not
JV>> serviced in time causing overruns. Does somebody know how I can
JV>> avoid overrun of COM1.
RB> Most likely, if you add /A:0 /U:0 /!BM to your IBM1S506 line your
RB> problem (and the added speed) will go away. This disables
RB> busmastering which is on by default in the newer HD drivers and
RB> which can cause serial problems. You might also try adding /!SMS to
RB> the end of the line as well to make things even slower. You can
RB> use the /V switch to see what the driver is seeing for your HD's
RB> and how they are being set up. Note that there is at least one
RB> version of IBM1S506 that ignores the !BM switch, if you try the
RB> DANIS IDE driver, this problem is rectified.
This sounds like the infamous SMS issue. Older versions of IBM1S506 honoured
the /!SMS switch and sacrificed performance for COM stability. The later ones
suffered from a bug which lead to disregarding /!SMS. In my driver /!SMS
works, and even better: there is a /SMS:n option which gives you optimum
control on this parameter. People have reported failures with later IBM1S506
versions, but stable COM operation with my driver at SMS values of 4 or 8
(nearly optimum performance).
bye, Dani
--- Sqed/32 1.14/r01354
* Origin: Nachtigall/2,Nuernberg/Ger,+49-911-861319,Z19+ISDN (2:2490/2576)
114/477
143/1
5100/8
+----------------------------------------------------------------------------+
From: Daniela Engert 05-Dec-99 19:22:15
To: Jonathan de Boyne Pollard 06-Dec-99 23:30:17
Subj: Phoenix INT 13h Extensions
Hi Jonathan!
Thus quoth Jonathan de Boyne Pollard to MIKE RUSKAI:
JdBP> As far as I have been able to find out, there are only three
JdBP> operating systems whose boot code uses the new INT 13h
JdBP> extensions. Two of those are Microsoft DOS-Windows 98 (and 95
JdBP> OSR2) and IBM OS/2 Warp Server 5. (IBM OS/2 Warp Server 5
JdBP> contains a new Boot Manager that uses the INT 13h Extensions and
JdBP> that can thus boot from any partition anywhere on any disk, for
JdBP> example.)
Thanks! I never heard about that before. This asks for a test...
bye, Dani
--- Sqed/32 1.14/r01354
* Origin: Nachtigall/2,Nuernberg/Ger,+49-911-861319,Z19+ISDN (2:2490/2576)
114/477
143/1
5100/8
+----------------------------------------------------------------------------+
From: Will Honea 06-Dec-99 19:55:00
To: Herbert Rosenau 06-Dec-99 19:55:00
Subj: Clunker update
Herbert Rosenau wrote to Will Honea on 12-06-1999
HR> Who is forwarding them? Any window can send/post such
HR> messages to any other window. Neither WM_COMMAND nor
HR> WM_SYSTEM are generated in system message queue. Tey are
HR> generated by an frame window related on WM_MOUSE.../WM_CHAR
HR> received from system message queue. You can send/post any
HR> message to any window. So you my send/post a WM_COMMAND
HR> from any window to another to become the action you would.
HR> It is usual to interact between serval windows (of serval
HR> applications) this way.
AH! Terminology problem. I completly agree that the system INPUT
queue only posts to the window with focus. The system MESSAGE queue is
another beast entirely - as are the individual queues established by
applications.
Will Honea <whonea@codenet.net>
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Will Honea 06-Dec-99 20:02:01
To: Kees Bergwerf 06-Dec-99 20:02:01
Subj: not enough diskspace
Kees Bergwerf wrote to All on 12-05-1999
KB> Program commander is working again without trouble. I think I will
KB> not use theseus5 again. It was neccesary because of sysbench and
KB> memsize (and memsize did give nothing but trouble: it worked fine
KB> for a while but I tried to change a setting in the config: use
KB> theseus, and then the program crashed and I have not been able to
KB> start it again without crashing.)
Theseus5 is working on multiple machines here with Warp 4, fp9-12, and
Warp 3, fp38 or 40. Better be - I rely on it. I never got os2memu to
work after fp8 or so and agve it up. For Memsize, just go to the
memsize directory and delete the memsize.ini file. It will then
restart fine w/o theseus.
Will Honea <whonea@codenet.net>
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Andrew Belov 06-Dec-99 08:13:21
To: Jonathan de Boyne Pollard 07-Dec-99 00:48:00
Subj: Re: odin-19991112
Hi Jonathan!
(Thu Dec 02 1999) Jonathan de Boyne Pollard wrote to Andrew Belov...
AB>> PMWINX DLL 520559 4.12.98 20:35
JdBP> Have you checked (with a tool such as EXEHDR or TDUMP) that it actually
JdBP> exports something with ordinal number 1022, which is what the message
is
JdBP> complaining about ?
USER32 imports it, as follows from the dump:
Page: 78 ( Object: 1/78 ) Offset: 00006CCC Length: 470
[...]
08/01 32bit Self-relative by ordinal PMWINX.1022
This ordinal is reported as "Unused entry" in PMWINX.DLL.
Good luck.
---
* Origin: Conea Software Mail system - Moscow, Russia (2:5020/181.2)
278/111
+----------------------------------------------------------------------------+
From: George White 05-Dec-99 15:15:12
To: Murray Lesser 07-Dec-99 01:35:01
Subj: Multiple visible primary
Hi Murray,
On 02-Dec-99, Murray Lesser wrote to Will Honea:
<snip>
ML> AFAIAC, the loss of that last cylinder is also "in the noise" :-(.
ML> If I wanted to guess, I would say that the practice you describe
ML> dates from the XT days when the last cylinder was reserved for a
ML> test track used only by the hard-drive read/write diagnostics. I
ML> had a small assembly-language routine for my XT that moved the
ML> heads over to that last cylinder before shutting down, so that if
ML> there wasn't a smooth landing, there would be no damage to usable
ML> data. As I understand it, this was done automatically on the AT.
ML> (I never owned an AT; I skipped the 286 generation as it didn't
ML> make any sense to me.) I would guess that hard-drive reliability
ML> (at least for drives from reputable makers) had improved (by the
ML> time OS/2 came along) to the point where that "test track" was
ML> probably unnecessary, but nobody noticed it was still there until
ML> relatively recently!
The need to reserve the last track as a test track became redundant
with the demise of ST506 drives. While I don't know the details of
EDSI so I can't comment on them, in all the ATA & SCSI drives
currently available the geometry presented to the OS bears no
relationship at all to the underlying geometry of the hardware, with
the disk controller also handling bad sector re-mapping etc.
While the reliability may have improved, the ability to use the test
track was removed by the on drive controllers.
George
--- Terminate 5.00/Pro
* Origin: A country point under OS/2 (2:257/609.6)
231/992
633/260
2501/209
+----------------------------------------------------------------------------+
From: George White 05-Dec-99 16:11:25
To: Stewart Buckingham 07-Dec-99 01:35:01
Subj: FileStar/2 Assumptions
Hi Stewart,
On 04-Dec-99, Stewart Buckingham wrote to Jonathan De Boyne Pollard:
SB> Where can this 32-bit CMD be obtained? Will it work under Warp4?
a) It's in beta :-).
b) Yes :-). (I'm beta testing it on Warp 4 GA).
George
--- Terminate 5.00/Pro
* Origin: A country point under OS/2 (2:257/609.6)
231/992
633/260
2501/209
+----------------------------------------------------------------------------+
From: Will Honea 06-Dec-99 23:13:00
To: Preston Smith 06-Dec-99 23:13:00
Subj: TCPIP Upgrade
Preston Smith wrote to All on 12-06-1999
Preston, I can't keep up with all the numbers for SYSLEVEL, but here's
a simpler check:
Just type in INETVER. If it gives a version somelike 4.02x (x is
anything) you still have the 16 bit version that came with Warp 4. If
it gives a 3-4 line result with 3 components identified, you have the
8610/4.1 level. If you're not sure (or we can't figure it out) then the
safest way to update this is to get WR08423 (that's a full refresh of
the version 4 stack) and install that before you apply the new
all-in-all update. That should meet all the requirements.
I tried the 8610 (wr08610_conv) and it was OK, but no world shaker.
There were a few bugs in it. The 4.1 upgrade is not free and REQUIRES
Java to configure. I have it on here but I see no huge difference on
my little setup. On the production servers at work it's a different
story - there is a world of difference on a loaded server but I doubt
that this would apply to your situation. Unless you have already
applied 8610 ( and it does not look like you have), I wouldn't bother.
You'll get just as good a result by sticking to the Ver 4 stack. Apply
8423 just to be sure where you are, then UN_0980.
If you are thinking of allowing net access to the BBS, you might
consider 8610 (or 4.1). The security is better and, in general, the
ftp and telnet daemons are much better and more secure - but that's
another topic.
If you can't find the wr08423 fix anymore, I can send it to you via
email or upload it if you have an ftp server up. It's 6 floppy images,
a good 8-9 meg. Good, solid release. Anyway, see what inetver reports
and we can go from there.
Quick comments on your syslevel dump:
Java 1.1.8 is a good 25% or more faster than 1.1.6.
Feature installer ver. 1.25 is current and required for most current
installs.
Will Honea <whonea@codenet.net>
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Holger Granholm 06-Dec-99 18:29:00
To: Bob Wright 07-Dec-99 05:58:03
Subj: Installation problem
In a message dated 11-26-99, Bob Wright said to Holger Granholm:
JS>> CFGINFO7.ZIP OS/2 Config.sys Optimizer! Sysop Recommended! (188K)
HG> Where can *I* grab a copy of that? Have nr. 6.
HG> FTP or Telnet preferred.
BW>Hobbes... directory pub/os2/util/config. The main new thing is
BW>that it contains a new version of the data file (os2cfg16). The
BW>main executable is still Rick's original dated in June of 95.
Thanks Bob, will grab it from there.
Happy Holidays,
Holger
___
* MR/2 2.26 * I love running Windows! NOT!
--- PCBoard (R) v15.22 (OS/2) 2
* Origin: Coming to you from the Sunny Aland Islands. (2:20/228)
772/1
+----------------------------------------------------------------------------+
From: Holger Granholm 06-Dec-99 18:29:00
To: Andy Roberts 07-Dec-99 05:58:03
Subj: USB
In a message dated 12-04-99, Andy Roberts said to Holger Granholm:
Hi Andy,
AR>> Usbcom02.Zip was just announced by Pete Norloff, so it may not be
AR>> on that CD.
HG> Just checked, it isn't but I'll await your reply to the previous
HG> reply.
AR>If that's the file you need, then I'll send it to you via E-Mail
AR>File Attach.
Thanks, but not necessary. I used the MTel application I received from
Jack Stein for the first time to grab it from his (Pete's) site.
AR>I may be proven wrong in the long run, but my feeling about USB is
AR>in the same class with VLB, which was only dominate for the 486 and
AR>mostly abandoned for the Pentium, which forced a lot of very
AR>expensive VLB HW to become obsolete.
Well this BBS machine is running on a VLB mobo with an AMD 486DX80.
It would be nice to upgrade it to the old mobo coming from my work
machine but I don't fancy buying new SCSI and video controllers to
replace the VLB units.
AR>And I'm sure USB has it's good points. But I have no intention
AR>of throwing away my ISA and SCSI HW and jumping on the USB
AR>bandwagon, just because some OEMs are trying to push new standards
Well, actually I really don't see the need either but thought I would
"future proof" the work machine while at it.
I might buy a 250 Mb ZIP but it will be a SCSI unit because I have an
Adaptec AHA-2842 in this machine and an 2940 in the work machine and
both sport a similar external connector and the controllers termination
can be switched on and off from the keyboard.
AR>I'm not sure what is going to be developed to replace the Pentium.
In my case, AMD will replace the Pentium. I don't see the need to feed
Intel any more than M$.
Have a nice day,
Holger
___
* MR/2 2.26 * I have no problem with God. It's His fan club I avoid.
--- PCBoard (R) v15.22 (OS/2) 2
* Origin: Coming to you from the Sunny Aland Islands. (2:20/228)
772/1
+----------------------------------------------------------------------------+
From: Peter Knapper 07-Dec-99 17:58:13
To: Stewart Honsberger 07-Dec-99 05:58:03
Subj: fdisk /query
Hi Stewart,
PK> Ok, maybe I should have made that "How about mounting other
PK> partitions off the Root (booted) file system (partition) similar to
PK> unix."
SH> You mean like CC: ?
I'm not sure what you mean by CC: sorry. Please explain......pk.
--- Maximus/2 3.01
* Origin: Another Good Point About OS/2 (3:772/1.10)
772/1
+----------------------------------------------------------------------------+
From: Peter Knapper 07-Dec-99 19:32:14
To: Stewart Honsberger 07-Dec-99 05:58:03
Subj: fdisk /query
Hi Stewart,
PK> Ok, maybe I should have made that "How about mounting other
PK> partitions off the Root (booted) file system (partition) similar to
PK> unix."
SH> You mean like CC: ?
Ummm, I'm not sure what you mean by CC: sorry, is that some sort of utility?
The only CC is am aware of is Carbon Copy, but thats a pretty old DOS app that
doesn't seem to fit into the discussion......;-) Please explain......pk.
--- Maximus/2 3.01
* Origin: Another Good Point About OS/2 (3:772/1.10)
772/1
+----------------------------------------------------------------------------+
From: Peter Knapper 07-Dec-99 21:10:11
To: All 07-Dec-99 05:58:03
Subj: HPFS Directories.
Hi Folks,
A simple question.......;-) Where is the FIRST root directory entry located on
an HPFS volume? I know that HPFS uses a directory recording methodology
similar to a B-Tree, and it writes files in BANDS across the partition,
however the very FIRST directory entry MUST be located somewhere that can be
calculated as a FIXED location for that particular partition. Alternatively
there must be a data structure within an HPFS partition that contains details
of the partition "layout". Now how can I find out where that location is?
My need is thus. I have a 2GB partition located in the middle of a drive
(other paritions before and after it) that is _SOMETIMES_ corrupting its Root
directory entry or a pointer to the Root directory entry, if there is a power
failure and the system is not shut down cleanly. If it IS shutdown cleanly,
the next boot up is fine and all is well. If a startup invokes CHKDSK, it
compains that it "cannot find the Directory \", and it then tries a recovery
which locks the machine SOLID after 173 files have been found! I have to boot
from Floppy and run CHKDSK from the commandline. In this case CHKDSK E: /F:2
detects the exact same problem, but it succeeds in fixing it and recovers ALL
the files EVERY TIME! These files are perfect with no errors. I can then place
them back where they belong, and everything works perfect, until the power
fails again.......;-( Also interesting is that only FILES are lost, never
Sub-directories (there are about 15,000 files on the volume).
My thinking is that if the HD has a faulty track right at the begining of the
partition I can shrink the partition and leave that Cylinder free. With FAT
this could work, but with HPFS I am not so sure. Ultimately I need a new
drive, but I was just wondering if I can work around this.
Any useful bits of info appreciated.
Thanks........pk.
--- Maximus/2 3.01
* Origin: Another Good Point About OS/2 (3:772/1.10)
772/1
+----------------------------------------------------------------------------+
From: Murray Lesser 06-Dec-99 08:41:00
To: Bob Wright 06-Dec-99 08:41:00
Subj: odin-19991112
(Excerpts from a message dated 11-27-99, Bob Wright to Andrew Belov)
Hi Bob--
BW>The readme.1st for fp 40 references installation of Open32 in its
>notes. However, the latest APAR that I could find that specifically
>mentions Open32(in read.me2) was from fp30.
The readme.1st file on any FixPak names all the files that have been
modified by FixPaks for that version of OS/2 since FixPak 1, up to and
including the FixPak you are looking at. It also gives the date each
such modification was last made. (Note that some files have been
modified several times.) Only those files dated the same as the FixPak
itself were introduced (or modified) in that one. Obviously, there is a
procedure that will tell you which FixPak last made the "fix" you are
interested in, but you have to have better back-issue files than I have
to use it :-(.
Regards,
--Murray
<Team PL/I>
___
* MR/2 2.25 #120 * If it ain't broke, don't FixPak it.
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Peter French 07-Dec-99 00:00:00
To: Bat Lang 07-Dec-99 00:00:00
Subj: cache
On 1999/12/05, Bat Lang wrote to Peter French on message number 301;
Hi Bat,
-=> Quoting Peter French to Eddy Thilleman, [03 Dec 99 17:27:00]
BL> PF> Relationship as DiskIdle=2*BufferIdle, Maxage=2(to 5)*DiskIdle
BL>
BL> Where is this information 'entered' into your configuration?
Input to an ordinary text file named startup.cmd in the root of the boot
drive as follows;
--
echo off
C:\OS2\cache.exe /diskidle:30000 /maxage:60000 /bufferidle:15000 /LAZY:3
/READAHEAD:ON
EXIT
--
(note these are my parameters - YEMV from mine given different memory sizes
etc., or - even entered manually at an OS/2 Command Line prompt will last for
the entire session.
___
X KWQ/2 1.2i X CABANGA = Think in Zulu
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Ian Singer 06-Dec-99 23:56:00
To: Dave Davidson 07-Dec-99 09:29:15
Subj: Netscape....
DD> Is there any way to convert or import MS's IE bookmarks to OS/2's
DD> Netscape? There's gotta be a way, I just haven't figured out
DD> how....yet.
Not sure about OS/2 but saw this file
SABBC100.ZIP 082498 SAB Bookmarks Converter v1.00. Converts IE
| bookmarks to Netscape bookmarks and Netscape
| bookmarks to IE bookmarks. Can be used to
| merge IE and Netscape bookmarks. Can also be
| used to merge multiple Netscape bookmark
| files into one or into IE
--- PCBoard (R) v15.23/M 5
* Origin: FidoNet * IDS Place * 416-754-7695 56.6Kbs FTS/QWK (1:250/462)
231/992
633/260
2501/209
+----------------------------------------------------------------------------+
From: Lee Aroner 05-Dec-99 20:39:00
To: Holger Granholm 07-Dec-99 12:42:05
Subj: HPFS Filenames to Window
HG> In a message dated 11-29-99, Lee Aroner said to Rachel Veraa:
RV> N'a pale pi ta,
LA> ^^^^^^ Swazi ? Zulu?
HG> ROTFL !
Hey, tis the season, eh?
HG> Happy Holidays,
You too Holger...
LRA
-- SPEED 2.01 #2720: Heisenberg might have been here.
--- Maximus/2 3.01
* Origin: Top Hat BBS (1:343/40)
278/111
+----------------------------------------------------------------------------+
From: Stewart Honsberger 07-Dec-99 10:30:12
To: Peter Knapper 07-Dec-99 15:30:22
Subj: fdisk /query
07 Dec 99 17:58, Peter Knapper wrote to Stewart Honsberger:
PK>> Ok, maybe I should have made that "How about mounting other
PK>> partitions off the Root (booted) file system (partition) similar to
PK>> unix."
SH>> You mean like CC: ?
PK> I'm not sure what you mean by CC: sorry. Please explain......pk.
Currently, OS/2 is installed on the C: partition. What I gathered from
your message was that you were suggesting somehow doubling up the drive
letters, so that you could have CC:, CD:, CE:, etc.. (which would then
make the partition limit up somewhere in the hundreds, unless tripling
the drive letters were permitted, allowing CCC:, CCD:, etc... which
would likely have the limit in the 100's of 1000's).
Sorry for not clarifying.
Stewart Honsberger,
blackdeath@tinys.oix.com
... Civil War. There's an oxymoron if I've ever heard one.
-!- GOPGP/2 v1.23
--- Msged/2 TE 05
* Origin: Blackdeath BBS - Private (1:229/604)
2320/38
+----------------------------------------------------------------------------+
From: Eddy Thilleman 06-Dec-99 09:28:28
To: Jonathan De Boyne Pollard 07-Dec-99 17:25:27
Subj: vkbd.sys
Hello Jonathan,
01 Dec 99 10:05, Jonathan de Boyne Pollard wrote to Eddy Thilleman:
JP> There are two sorts of VDDs, "base" VDDs and "installable" VDDs. The
JP> "base" VDDs are always loaded, since they are essential to the
JP> operation of a VDM. The "installable" VDDs are the ones listed in
JP> CONFIG.SYS .
I don't know, I never looked into this.
JP> There's a list of the "base" VDDs in the Virtual Device Driver
JP> Reference in the OS/2 DDK.
I don't think I have the OS/2 DDK. Is that available on internet?
Greetings -=Eddy=- email: eddy.thilleman@net.hcc.nl
... The biggest computer fraud in history: WINDows 3.x
--- GoldED/2 3.0.1
* Origin: Windows95 is a graphic DOS extender (2:280/5143.7)
772/1
+----------------------------------------------------------------------------+
From: Eddy Thilleman 06-Dec-99 09:32:14
To: Stewart Buckingham 07-Dec-99 17:25:27
Subj: Communicator Fatal Error
Hello Stewart,
04 Dec 99 08:57, Stewart Buckingham wrote to Eddy Thilleman:
SB> I just learned from Mike that os2pref.js = prefs.js. Anyhow I've
SB> tried deleting the file and I've tried copying the file to os2pref.js,
SB> but neither seems to solve the parsing problem. Is there a path to
SB> this file somewhere?
Like I said before, it is located in the netscape user directory (where for
example also the bookmarks are located)
Greetings -=Eddy=- email: eddy.thilleman@net.hcc.nl
... Dogs crawl under Gates, software crawls under Windoze.
--- GoldED/2 3.0.1
* Origin: Windows98 is a graphic DOS extender (2:280/5143.7)
772/1
+----------------------------------------------------------------------------+
From: Eddy Thilleman 06-Dec-99 09:34:22
To: James Mckenzie 07-Dec-99 17:25:27
Subj: DELTREE
Hello James,
03 Dec 99 20:02, James Mckenzie wrote to Eddy Thilleman:
JM> I have an OS/2 verision of DELTREE and it works on HPFS partions
I too have an OS/2 version of DELTREE.
JM> Which one? The DOS deltree would not work under OS/2 and would delete
JM> directories only on FAT partitions when booted to plain "old" DOS.
I never used the "DOS DELTREE" because I've written my own DOS DELTREE version
which works under any DOS version (including DOS sessions under OS/2, and on
HPFS partitions too). I don't put crap version checks in my programs.
JM> Disk caching did not matter as the version with DOS 6 was designed to
JM> work with most disk caching schemes.
Disk caching should work transparently, so any program can work with any disk
cache without knowing it.
Greetings -=Eddy=- email: eddy.thilleman@net.hcc.nl
... All's well that ends well. - E.A. Poe
--- GoldED/2 3.0.1
* Origin: Windows98 is a graphic DOS extender (2:280/5143.7)
772/1
+----------------------------------------------------------------------------+
From: Eddy Thilleman 06-Dec-99 09:48:17
To: Holger Granholm 07-Dec-99 17:25:27
Subj: DELTREE
Hello Holger,
04 Dec 99 20:01, Holger Granholm wrote to Eddy Thilleman:
ET>> That still leaves one question I asked to be answered: was it run
ET>> under plain DOS booted (=not under OS/2) without a disk cache?
HG> YES!
That's what I thought. Thanks for the answer. :)
Greetings -=Eddy=- email: eddy.thilleman@net.hcc.nl
... OS/2 vs. Windows is a no-Win situation.
--- GoldED/2 3.0.1
* Origin: Windows95 is a graphic DOS extender (2:280/5143.7)
772/1
+----------------------------------------------------------------------------+
From: Eddy Thilleman 06-Dec-99 09:51:02
To: Peter French 07-Dec-99 17:25:27
Subj: r0stub.sys
Hello Peter,
05 Dec 99 00:00, Peter French wrote to Eddy Thilleman:
PF> Excuse the butting in on a thread that doesn't concern me :) did you
PF> know: A new mixer for Crystal Semiconductor drivers is available
PF> from Hobbes under name:
PF> http://hobbes.nmsu.edu/pub/incoming/lbmix001.zip
I've seen the filename before, but hadn't had the time to check it, but I'll.
PF> This mixer works with IOCTL category 90 mixer API implemented in
PF> Crystal v.2.08 and v.3.02 drivers (and probably later versions).
I'm now running the 2.08 version, I think this is the newest for
ISA-soundcards. The 3.x version is problably for PCI-soundcards?
Greetings -=Eddy=- email: eddy.thilleman@net.hcc.nl
... If it ain't broke, don't FixPak it.
--- GoldED/2 3.0.1
* Origin: Windows98 is a graphic DOS extender (2:280/5143.7)
772/1
+----------------------------------------------------------------------------+
From: Eddy Thilleman 06-Dec-99 10:47:26
To: Kees Bergwerf 07-Dec-99 17:25:27
Subj: not enough diskspace
Hello Kees,
04 Dec 99 11:14, Kees Bergwerf wrote to All:
KB> But why are those locked files not handled? The next boot does not
KB> give any message after locked files at all. But when they are not
KB> properly handled, why does OS/2 remove the locked files device driver?
I don't know...
KB> I use Warp4 US, fixpack12, on a pentium II/400
I too tried to install fixpak 12 on my Warp 4, but I got only errors and
lockups (I didn't got error messages about not enough diskspace to handle the
locked files) during booting the system locked up so I had to reboot into the
maintenaince partition so I could remove fixpak 12, so I returned to fixpak 9.
Greetings -=Eddy=- email: eddy.thilleman@net.hcc.nl
... I think that I'll stand up-wind, if you don't mind.
--- GoldED/2 3.0.1
* Origin: Windows95 is a graphic DOS extender (2:280/5143.7)
772/1
+----------------------------------------------------------------------------+
From: Eddy Thilleman 06-Dec-99 11:34:02
To: Peter French 07-Dec-99 17:25:27
Subj: cache
Hello Peter,
03 Dec 99 17:27, Peter French wrote to Eddy Thilleman:
PF> 3 Lazy write worker(s) are enabled.
So I assume you don't know why 3 lazy write workers are (or should be) faster
than 2 or 1 lazy write workers?
Greetings -=Eddy=- email: eddy.thilleman@net.hcc.nl
... "Screw the prime directive, Sir. I say give the Borg Windows 3" ■ Worf
--- GoldED/2 3.0.1
* Origin: Windows95 is a graphic DOS extender (2:280/5143.7)
772/1
+----------------------------------------------------------------------------+
From: Eddy Thilleman 06-Dec-99 11:43:14
To: Herbert Rosenau 07-Dec-99 17:25:27
Subj: cache
Hello Herbert,
05 Dec 99 15:04, Herbert Rosenau wrote to Eddy Thilleman:
HR> run=f:\os2\cache.exe /LAZY:9 /MAXAGE:12500 /DISKIDLE:7500
HR> /BUFFERIDLE:2000 /READAHEAD:1
9 lazy write workers? I haven't seen mentioned that high before.
Is there something like a rule of thumb for this, or a relation between how
much disk intensive an application is, the disk throughput and the number of
lazy write workers? Is there a trade-off, for example more lazy write workers
need more memory? If so, how much?
HR> It depends on your system usage.
It always depends on your system usage, I know. :)
HR> Yes, disk caching is the most recent parameter on it.
I don't know what you mean with this. Can you clarify this? Didn't you use the
cache command before?
Greetings -=Eddy=- email: eddy.thilleman@net.hcc.nl
... A teenage male can do it every 20 minutes! It's true!
--- GoldED/2 3.0.1
* Origin: Windows95 is a graphic DOS extender (2:280/5143.7)
772/1
+----------------------------------------------------------------------------+
From: Eddy Thilleman 06-Dec-99 11:49:09
To: Rich Wonneberger 07-Dec-99 17:25:27
Subj: Kodak DVC-323 Camera
Hello Rich,
05 Dec 99 10:59, Rich Wonneberger wrote to All:
RW> I know OS/2 has USB support now, but does anyone know if a Kodak
RW> DVC-323 camera will work with it??
I don't know.
DCITU18F.RAR 675K 05-11-99 DCITU v1.8f [beta]
Digital Camera Image Transfer Utility for
OS/2
- Kodak DC220, Kodak DC260, Kodak DC265,
Minolta Dimage:
- Kodak DC240 & Kodak DC280
- Kodak DC200, Kodak DC210 & Kodak DC215
- Kodak DC120 & Kodak DC25
- Agfa ePhoto, Epson PhotoPC, Nikon, Olympus,
Sanyo VPC/DSC, Sierra SD640 & Toshiba PDR-2
(cameras known as Project/Protocol "O")
I don't have a digital camera, so I don't have experience with this.
Greetings -=Eddy=- email: eddy.thilleman@net.hcc.nl
... OS/2 Warp 4.0: Where even the Properties have Properties
--- GoldED/2 3.0.1
* Origin: Windows95 is a graphic DOS extender (2:280/5143.7)
772/1
+----------------------------------------------------------------------------+
From: Craig Ford 07-Dec-99 18:46:16
To: All 07-Dec-99 22:35:20
Subj: Help!
Hello All!
With IBM's withdrawl of support for Warp3, I finally upgraded my installation
to Merlin, and tried to install FP12 to it. Alas, application of the Fixpak
failed due to a checksum error in PMMERGE.DLL.
Would some one be so kind as to tell me the size and timestamp of PMMERGE.DLL
in a virgin Warp4 installation? It would also help if someone could tell me in
which immage file on the distribution CD it is contained.
Regards....
Craig
aka: cford@ix.netcom.com
: craig.ford@2001.conchbbs.com
--- timEd/2 1.10.y2k+
* Origin: Dayze of Futures Past * V.Everything * 281-458-0237 * (1:106/2001)
231/992
633/260
2501/209
+----------------------------------------------------------------------------+
From: Will Honea 07-Dec-99 20:34:00
To: Peter Knapper 07-Dec-99 20:34:00
Subj: HPFS Directories.
Peter Knapper wrote to All on 12-07-1999
PK> A simple question.......;-) Where is the FIRST root directory
PK> entry located on an HPFS volume? I know that HPFS uses a directory
PK> recording methodology similar to a B-Tree, and it writes files in
PK> BANDS across the partition, however the very FIRST directory entry
PK> MUST be located somewhere that can be calculated as a FIXED
PK> location for that particular partition. Alternatively there must be
PK> a data structure within an HPFS partition that contains details of
PK> the partition "layout". Now how can I find out where that location
PK> is?
I'm sure Mike Ruskai will jump in here, but you should take a long
look at DFSEE (Hobbes, etc). It has considerable power to look into
and correct some of the superblock info among other things. It's saved
my bacon a couple of times.
Will Honea <whonea@codenet.net>
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Peter French 08-Dec-99 00:00:00
To: Eddy Thilleman 08-Dec-99 00:00:00
Subj: cache
On 1999/12/06, Eddy Thilleman wrote to Peter French on message number 330;
Hello Eddy
ET> 03 Dec 99 17:27, Peter French wrote to Eddy Thilleman:
ET> PF> 3 Lazy write worker(s) are enabled.
ET>
ET> So I assume you don't know why 3 lazy write workers are (or
ET> should be) faster than 2 or 1 lazy write workers?
No, I assumed that Denis selected 3 because of my memory size. At the time,
he was helping me to trace the burst of disk activity - at a high priority -
that seemed to occur every couple of minutes. This burst was really bugging
me
as it seemed that some people have this "effect" while others do not complain
about it. I realise that it (in all probability) was the system flushing
cache
to disk - however the priority was so high that it would effect use of
something like EPM. If I was typing - for instance - the burst would mean
that
the characters appearing on the screen would STOP until the burst stopped and
the system caught up to me. This just seemed wrong on a OS that was designed
to do many things at the same time. (we did confirm it was the USER/SYSTEM
INI
update)
My understanding is, that each worker is a thread which means that the write
to disk is achieved by a worker, and a second one is activated should parallel
"stuff" in memory is required to be written at the same time! Unless you have
a very memory intensive application it is unlikely that the volume to be
written out of cache would require more than the 3.
Our co-operation was not conclusive - the problem was helped by cleaning up
my INI files, and I assume it is something to do with my system, my setup,
whatever. I have found a very good work-around though - one I can recommend
to
anyone seeing the disk burst on their system.
REM -------------RAM INI Backup----------------------------
ifs=d:\util\ramfs64\ramfs64.ifs
REM SET USER_INI=C:\OS2\OS2.INI
REM SET SYSTEM_INI=C:\OS2\OS2SYS.INI
set user_ini=z:\inis\os2.ini
set system_ini=z:\inis\os2sys.ini
run=d:\util\ramfs64\ramdisk.exe z: ramdisk
run=D:\util\updini12\updini.exe c:\os2\ 10
REM ----------------RAM INI--------------------------------
This change to the CONFIG.SYS sets up a RAM disk using RAMFS64 and changes
the systems standard INI positioning to the new RAM location. Then it runs
the
UPDINI.EXE by Peter Engels. This application copies the INI's - if they have
changed, to the normal location in idle and low priority time. The "burst"
disappears, the system goes quiet, the operation does not effect any user
operations, the same caveats apply to operational data held in memory - should
the system abend abnormally. OS/2 works (for me) now like I assume it should
and for over a year of use I have not had any (known) ill effects.
___
X KWQ/2 1.2i X There is no right way to do a wrong thing
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Murray Lesser 07-Dec-99 15:10:00
To: Will Honea 07-Dec-99 15:10:00
Subj: OS20MEMU and THESEUS 3
(Excerpts from a message dated 12-06-99, Will Honea to Kees Bergwerf:
original topic: not enough disk space):
Hi Will--
WH>Theseus5 is working on multiple machines here with Warp 4, fp9-12,
>and Warp 3, fp38 or 40. Better be - I rely on it. I never got
>os2memu to work after fp8 or so and agve it up...
Couple of quick queries, and one not so quick:
Some Warp 3 FixPak around 10 killed OS20MEMU. It was revived for
Warp 4 with a patch I got from Hobbes based on advice from
devcon@ibm.net at the time (name of patch not recalled, but the file
OS20MEMU.DLL in my OS2MEMU folder is dated 9/12/96; all the other files
are dated in '94). I am now running it under Warp 4, FixPak 5. Are you
saying that os20memu died again on a later Warp 4 FixPak? If so,
another good reason to not "upgrade" if I don't have to :-). If its
only death to date was in Warp 3, I have no worry since both of my
machines are running on Warp 4 FixPak 5.
I am using Theseus 3 (theseus5.sys in config.sys). Do you really
mean you are using a later version, Theseus 5, or was that a slip of the
fingers? If you meant it, where did you get it?
I am also still running OSRM2 Lite, which uses theseus2.sys as a
driver to run a working set analysis. The output doesn't agree with
that given by Theseus 3; it appears that OSRM2 doesn't show the shared
system memory. I think I will give up the disk space taken up by OSRM2
since the vendor has apparently vanished and I now have Theseus 3. The
results shown by OSRM2, OS20MEMU, and THESEUS 3, for "owned memory" are
all different, and I haven't the slightest idea of which one (if any) is
"correct" :-(. In general, I use OS20MEMU only for quick checks on the
effects of coding changes (mostly for multithreaded programs) on memory
usage. Any comment?
Regards,
--Murray
<Team PL/I>
___
* MR/2 2.25 #120 * If it ain't broke, don't FixPak it.
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Sanford Shapiro 08-Dec-99 11:00:00
To: All 08-Dec-99 11:00:00
Subj: Wordperfect 7
I have a copy of Corel Wordperfect 7 for Windows 3.1. It works great
under OS/2 (WinOS2).
The question I have is -- it mentions OS/2 integration tools. These
are no longer available from Corel.
Does anyone have these OS/2 integration tools that I can get a copy
of? Are they listed on any of the OS/2 BBS's?
Thanks,
Sandy Shapiro
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Will Honea 08-Dec-99 19:16:00
To: Murray Lesser 08-Dec-99 19:16:00
Subj: OS20MEMU and THESEUS 3
Murray Lesser wrote to Will Honea on 12-07-1999
ML> Couple of quick queries, and one not so quick:
ML>
ML> Some Warp 3 FixPak around 10 killed OS20MEMU. It was revived for
ML> Warp 4 with a patch I got from Hobbes based on advice from
ML> devcon@ibm.net at the time (name of patch not recalled, but the
ML> file OS20MEMU.DLL in my OS2MEMU folder is dated 9/12/96; all the
ML> other files are dated in '94). I am now running it under Warp 4,
ML> FixPak 5. Are you saying that os20memu died again on a later Warp 4
ML> FixPak? If so, another good reason to not "upgrade" if I don't have
ML> to :-). If its only death to date was in Warp 3, I have no worry
ML> since both of my machines are running on Warp 4 FixPak 5.
I pretty much got away from OS/2memu so I'm just reporting what I
remembered seeing - I haven't had it up in over a year.
The version is Thesues3, last copy I saw at Testcase was Th?/3000.zip
- same content as originally offersd. The DLL is theseus5.sys
ML> I am using Theseus 3 (theseus5.sys in config.sys). Do you
ML> really mean you are using a later version, Theseus 5, or was that a
ML> slip of the fingers? If you meant it, where did you get it?
Same animal. Works well for me. AIR, you rename the DLL in
distribution to Theseus0.DLL and that's the only Theseusx.DLL I've ever
noticed beung loaded.
ML> I am also still running OSRM2 Lite, which uses theseus2.sys as
ML> a driver to run a working set analysis. The output doesn't agree
ML> with that given by Theseus 3; it appears that OSRM2 doesn't show the
ML> shared system memory. I think I will give up the disk space taken
ML> up by OSRM2 since the vendor has apparently vanished and I now have
ML> Theseus 3. The results shown by OSRM2, OS20MEMU, and THESEUS 3, for
ML> "owned memory" are all different, and I haven't the slightest idea
ML> of which one (if any) is "correct" :-(. In general, I use OS20MEMU
ML> only for quick checks on the effects of coding changes (mostly for
ML> multithreaded programs) on memory usage. Any comment?
The only place I ever heard of OSRM2 was when you mentioned it before
so I have zero idea how it works. I trust Theseus over OS2Memu for
reporting, altho the latter was a bit quicker to interpret. I use
Theseus all the time to monitor the programs I'm working on for memory
leaks and occasionally for hot spot analysis in some LAN based comm
threads. Theseus is considerably more detailed in it's memory analysis
but it's also harder to learn to interpret. Off the top of my head, I
don't recall seeing a break out for cache usage in Theseus - but
there's enough there to make missing something easy.
Will Honea <whonea@codenet.net>
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Will Honea 08-Dec-99 19:24:01
To: Craig Ford 08-Dec-99 19:24:01
Subj: Help!
Craig Ford wrote to All on 12-07-1999
CF> With IBM's withdrawl of support for Warp3, I finally
CF> upgraded my installation to Merlin, and tried to install
CF> FP12 to it. Alas, application of the Fixpak failed due to a
CF> checksum error in PMMERGE.DLL.
CF>
CF> Would some one be so kind as to tell me the size and
CF> timestamp of PMMERGE.DLL in a virgin Warp4 installation? It
CF> would also help if someone could tell me in which immage
CF> file on the distribution CD it is contained.
If you smart enough to take the backup/archive option offered by
SERVICE, then just got to that directory find PMMERGE.DL_. If it's
there - and there should be 2 copies if you had a backup from a
previous FP because it then created an archive directory. Anyway, if
you can find one of these then boot to a command line, change to the
OS2\DLL directory, and run "UNPACK <archive path>\pmmerge.dl*". That
will recover your previous one. You might want to try the updated
PMMERGE.DLL distributed after FP12 came out - supposedly it fixed a
nagging memory leak.
You DID make a backup, right???
Will Honea <whonea@codenet.net>
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Will Honea 08-Dec-99 19:27:02
To: Sanford Shapiro 08-Dec-99 19:27:02
Subj: Wordperfect 7
Sanford Shapiro wrote to All on 12-08-1999
SS>
SS> I have a copy of Corel Wordperfect 7 for Windows 3.1. It works
SS> great under OS/2 (WinOS2).
SS>
SS> The question I have is -- it mentions OS/2 integration tools.
SS> These are no longer available from Corel.
SS>
SS> Does anyone have these OS/2 integration tools that I can get a
SS> copy of? Are they listed on any of the OS/2 BBS's?
I've got a copy I guess I could send you, but they are essentially
useless - caused me more grief than they were worth.
Will Honea <whonea@codenet.net>
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Sanford Shapiro 08-Dec-99 21:11:00
To: Will Honea 08-Dec-99 21:11:00
Subj: Wordperfect 7
Well that is good to know. I don't feel I need these tools, but I
thought it would be fun to try them out and see what they do.
If it's not too much trouble, could you e-mail me the file or files as
an attachment to:
sshapiro@ucsd.edu ?
Thanks very much,
Sandy Shapiro
WH> SS> Does anyone have these OS/2 integration tools that I can get a
WH> SS> copy of?
WH> I've got a copy I guess I could send you, but they are essentially
WH> useless - caused me more grief than they were worth.
WH>
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Ron Nicholls 09-Dec-99 22:42:00
To: All 09-Dec-99 22:42:00
Subj: Fix_Paks
Are the early fix paks for Warp 4 ( 1 to 8 )
still available anywhere.
-
-
Regards RonN
-
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Louis Aubree 06-Dec-99 22:32:00
To: Gord Hannah 10-Dec-99 06:58:06
Subj: Warp 3 install
Hi Gord,
LA>> Install Warp 3 red with Dual Boot on HPFS ? Is it possible ? With
LA>> Win apps needed?
GH>
GH> I don't see why not my first install of Warp3 was a botched deal
GH> from the start, but it worked just fine, winapps can reside any
GH> where, just use th and if they are good should work, and yes there a
GH> few good Win apps out there, the only fault they have is the OS they
GH> must run under..:-)
I understand that Warp 3 _blue_ spine (with WinOS2 inside) can be
installed on HPFS, but I still don't understand the same for the
_red_ spine version.
I think that Warp _red_ spine has to be installed _after_ DOS and
Win3.1x, on the same primary partition, so this partition has to be
FAT16 formated. Then, the user could choose to never use Dual Boot
anymore and run anything (hum!) from OS/2. Where am I wrong? Is it
possible to install Win3.1x _after_ Warp 3 red spine on an HPFS
partition? Or use another trick?
Hope this will be clear soon.
Louis
P.S. Eddy Thilleman also replied: he also believes Warp 3 red cannot
be installed on HPFS.
...
* ATP/OS2 1.42 * Bonjour de Nantes, Bretagne.
--- MsgToss 2.0d(beta) 02/21/93
* Origin: Island's BBS * Nantes et sa region * (+33) 0251.397.478 (2:326/2)
231/992
633/260
2501/209
+----------------------------------------------------------------------------+
From: Michael Box 07-Dec-99 19:35:24
To: Craig Ford 10-Dec-99 06:58:06
Subj: Help!
Hello Craig.
Tuesday December 07 1999 18:46, you wrote to All:
CF> With IBM's withdrawl of support for Warp3, I finally upgraded my
CF> installation to Merlin, and tried to install FP12 to it. Alas,
CF> application of the Fixpak failed due to a checksum error in
CF> PMMERGE.DLL.
CF> Would some one be so kind as to tell me the size and timestamp of
CF> PMMERGE.DLL in a virgin Warp4 installation? It would also help if
CF> someone could tell me in which immage file on the distribution CD it
CF> is contained.
I ran into the same problem and thought it was something I was doing wrong.
Although it was with fixpack 11. I've downloaded the darn FP 3 times and still
got the same results. My system is warp 4 with no FP's applied. I have Peer
and TCPIP networking running. If you come across a fix or work around, I'd
love to hear about it. I've just gotta upgrade this thing soon.
Thanks
Michael
--- 3.0.1
* Origin: Mikey's Mystery Mailer (1:103/100)
278/111
+----------------------------------------------------------------------------+
From: SINISA PAVLOVIC 07-Dec-99 22:31:00
To: All 10-Dec-99 06:58:06
Subj: Re: Another leaky fixpak?
From: sinip@hamhq.yfnet.org.yu (SINISA PAVLOVIC)
Reply-To: sinip@hamhq.yfnet.org.yu (SINISA PAVLOVIC)
Organization: HAM HQ BBS, Doboj, RS, 074/24-360
-=> Quoting Jack Pfisterer to All <=-
SP> Where I can find it? I have occasional errors on pmmerge.dll with
SP> Acrobat Reader for OS/2, so new one might help me?
JP> Contact Ivan Adzhubei, ivan@protein.bio.msu.su and ask if he still has
JP> it available for FTP. That's where I got the copy I installed. I've
JP> heard there's an even-newer one out, but haven't been able to locate
JP> it.
OK, thanks.
JP> If all else fails, check back with me and I can attach it to an
JP> e-mail. The ZIP is a little over one meg in size and also includes a
But just to be sure that I'm not going to get the same one, PMMERGE that
I have here is:
PMMERGE.DLL 1238971 bytes 08.Oct.1998 12.14pm
JP> newer keyboard.dcp.
What is that for?
Visit: http://www.targetshop.com/users/level1.asp?refId=349351
Regards from Doboj, Republic of Srpska. mail to: 4n4da@qsl.net
... Not all Sysops are user friendly!
___ Blue Wave/OS2 v2.30
--- FIDOGATE 4.3.5
* Origin: fido.org.yu domain gateway (2:382/5.0)
231/992
633/260
2501/209
+----------------------------------------------------------------------------+
From: Andy Brown 07-Dec-99 22:15:06
To: Louis Aubree 10-Dec-99 06:58:06
Subj: Warp 3 install
Hello Louis.
06 Dec 99 22:32, you wrote to Gord Hannah:
LA> I think that Warp _red_ spine has to be installed _after_ DOS and
LA> Win3.1x, on the same primary partition, so this partition has to be
LA> FAT16 formated. Then, the user could choose to never use Dual Boot
LA> anymore and run anything (hum!) from OS/2. Where am I wrong? Is it
LA> possible to install Win3.1x _after_ Warp 3 red spine on an HPFS
LA> partition? Or use another trick?
_If_ you want to have DUAL BOOT or use Win 3.1 then your boot drive has to be
Fat 16 formated and DOS/WIN3.1 installed.. That does not prevent you from
booting up under OS/2 you just loose the benefits of the HPFS system on that
drive.. You can still have any other dirves formated HPFS and DOS/WIN3.1 can
access them _if_ you boot up OS/2 and use them from there.. _If_ you do not
want DUAL BOOT or WIN3.1 installed then all your drives can be HPFS format..
LA> Hope this will be clear soon.
Hope this helps you understand..
Andy
--- MyTosser 1.20/Pro
* Origin: College Area Hub, San Diego,CA (MO) (1:202/805)
278/111
+----------------------------------------------------------------------------+
From: Peter Knapper 08-Dec-99 23:43:04
To: Stewart Honsberger 10-Dec-99 06:58:06
Subj: fdisk /query
Hi Stewart,
SH> Currently, OS/2 is installed on the C: partition. What I gathered from
SH> your message was that you were suggesting somehow doubling up the drive
SH> letters, so that you could have CC:, CD:, CE:, etc..
Ahaaa, I was thinking of an old DOS program called Carbon Copy.....;-)
No, a single drive letter is all that is needed. Ok, some further explaination
is required. In my partition/drive lettering scheme, the booted partition
containing OS/2 would ALWAYS be Drive C:, and never anything else. It would be
possible to use such a machine with no other drive letter assignment at all,
unless the user wanted to allocate a drive letter for some reason (probably
some old brain dead S/W). To make other partitions visible to the booted OS,
the user supplies a directive to ADD that partition into the directory
structure of C: similar to the unix MOUNT command. EG:
Lets say you have 1 hard drive with 3 partitions on it. Forget Logical Drives,
Primary Partiions, they are all irrelevant in my scenario. The only criteria
here is that the partion FORMAT can be read, either natively or by loading
some driver, by OS/2. Lets assume you have a single HD with 3 partitions -
Partition Partition
No. Name
1 DOS622
2 WARP5
3 MYDATA
If Partition 2 is set up to be the active partition, then WARP5 boots up and
assigns Partition 2 as Drive C: (because partition 2 is the booted partion).
At this point the other partitions are invisible and unknown to OS/2. If the
user wants to access the DOS622 partition, then they issue a command similar
to this -
mount 1 \MYDOS
Which means that the DOS622 partition then appears on the C: drive as a
directory structure starting at \MYDOS, which is the ROOT directory of
Partition 1. Similar, the command -
mount 3 \DATAFILES
would mount the 3rd partition under \DATAFILES, and ALL data on ALL partitions
would be accessible as data somewhere under the root directory of Drive C:.
Now if the user had some old brain dead S/W that needed to see the directory
structure on MYDATA on a unique drive letter, then a command similar to -
assign J: \DATAFILES\DUMBAPPDATA
means that if S/W accesed J:\, it would actually be accessing
C:\DATAFILES\DUMBAPPDATA\ but know the fies in that directory as Drive J:\.
This gets a bit more complicated with multiple HD's, but the same concepts can
apply, IE the user has total control over WHICH partitions are accessable,
WHERE they mount, and what DRIVE LETTERS they become known by.
Does that explain it better?
Cheers............pk.
--- Maximus/2 3.01
* Origin: Another Good Point About OS/2 (3:772/1.10)
772/1
+----------------------------------------------------------------------------+
From: James Mckenzie 08-Dec-99 05:45:02
To: Preston Smith 10-Dec-99 06:58:06
Subj: TCPIP Upgrade
Hello Preston!
06 Dec 99 18:24, Preston Smith wrote to All:
PS> Hello All!
PS> I sent this message to both the TEAMOS2 and OS2 e-mail lists on
PS> saturday and no one has responded. Can you folks help?
PS> I decided to try to upgrade my TCPIP version so I downloaded "TCP/IP
PS> For OS/2 V3.1 & V4.0 Universal FixPak UN_0980" to apply to my sytem.
PS> The first thing I see in the readme file is
PS> Note: You should have MPTS FixPak WRx8421 (or above) installed on
PS> your system before applying this FixPak. Also note that WRx8610
PS> should not be installed on a non-SMP Warp Server without installing
PS> TCP/IP v4.1 along with it. There have been various problems reported
PS> when using WRx8610 without TCP/IP v4.1.
PS> Warning: 1 - This FixPak services some of the TCP/IP files based on
PS> the MPTS level on the system. If you have WRx8610 or above on your
PS> system when you install this FixPak, you should not install a version
PS> of MPTS older than WRx8610 because it will back-level some of the
PS> TCP/IP files. If you have an MPTS version prior to WRx8610 when you
PS> install this FixPak and you then install WRx8610, you should
PS> reinstall this FixPak to ensure that the proper TCP/IP files are
PS> installed. If you plan to install WRx8620, it should be installed
PS> after installing this FixPak.
PS> My questions are (results of Syslevel are shown below)
PS> 1. Is it normal to see what appear to be duplicate entries in the
PS> Syslevel info? If not, how do I clean it up?
Yes, there are several components to the TCP/IP sub-system.
PS> 2. I see I have TCPIP 4.00 on my system - should I upgrade to TCPIP
PS> 4.1?
No.
PS> 3. How do I know what MPTS level is on my system? Should this be
PS> upgraded to WRx842x? or WRx8610 then 8620?
The current level is WR8400 and it should be upgraded to WR0842x (I think
that 23 or 24 is the latest) and then apply the UN patch.
PS> 4. Are there any other related upgrades I should install to bring my
PS> communication suite up to date?
Not that I'm aware of. However, there is a site on the internet with several
good lists of current updates.
James
... Try Win'95 and you'll never use DOS again... or the rest of your PC!
--- GoldED/2 3.0.1
* Origin: OS/2 Support * Your place for OS/2 information and Files
(1:15/64)
231/992
633/260
2501/209
+----------------------------------------------------------------------------+
From: John Angelico 08-Dec-99 00:45:00
To: Ian Moote 10-Dec-99 06:58:06
Subj: WarpCenter INI file ?
On 29/11/1999, Ian Moote said to LEE ARONER about WarpCenter INI file ?:
IM> LA> Anyone know what the WarpCenter INI file is?
IM>
IM> Back in April John Angelico was kind enough to inform me that the
IM> WarpCenter configuration is stored in the files c:\os2\dll\scenter.cfg
IM> and c:\os2\dll\dock*.cfg. Hope this helps. Take care and TTYL.
IM>
Ahem... just getting back online after the Club lost its upline feed...
Ian: thank you for remembering.
John Angelico
Co-convener, OS/2 SIG
Melbourne PC User Group
also known as: talldad@kepl.com.au
___
X KWQ/2 1.2i X I am positive that a definite maybe is probably in order.
---
* Origin: Melbourne PC User Group BBS (3:633/309)
231/992
633/260
2501/209
+----------------------------------------------------------------------------+
From: Herbert Rosenau 08-Dec-99 18:13:01
To: Eddy Thilleman 10-Dec-99 06:58:06
Subj: cache
HR>> run=f:\os2\cache.exe /LAZY:9 /MAXAGE:12500 /DISKIDLE:7500
HR>> /BUFFERIDLE:2000 /READAHEAD:1
ET> 9 lazy write workers? I haven't seen mentioned that high before.
Why not?
ET> Is there something like a rule of thumb for this, or a relation
ET> between how much disk intensive an application is, the disk
ET> throughput and the number of lazy write workers? Is there a
ET> trade-off, for example more lazy write workers need more memory?
ET> If so, how much?
The optimasion was done at a time this computer was used as
- 3 lines node with mostly ISDN throughput
- developement mashine (edit/compile/debug...) with all lines running
- some other aktive tasks
HR>> Yes, disk caching is the most recent parameter on it.
ET> I don't know what you mean with this.
The optimasion was at least done with help another node to become the highest
possible transfer rate during an connect on both lines and running tosser in
background.
I'd found that throwing on the cache parameters has the most incredible effect
on the transfer rates. I'd found values that are commonly nearst the physical
maximum (7950/15500 cps as sender and 7850/14500 as receiver of *.bmp)
Exchange of large *.bmp can kill the telko's convey station if both sides can
send with maximum speed on direct CAPI. :-)
Without the excessive optimasision step my transfer rate where more than 200
cps less.
For now this computer has lost all funtions other than holding the node 24h/7d
online.
ET> Can you clarify this? Didn't you use the cache command before?
Yes. But not this extensive testing to find the best parameters.
The first step to optimise is to optimise the config.sys:
maxwait=x 1 - 3, depending on RAM and CPU
it is the first parameter to push up or slow down
the mailer;
priority_disk_io=no let the mailer (and othert background) thread
have higher priority to wirte/read to/from disk
than forground threads
must be NO if you would have a maximum throughput
to your lines.
Both changes requires a system reboot
After that playing with the cache parameters can speed up the lines more.
Changes can be made without reboot. call cache.exe with the propper
parameters.
--- Sqed/32 1.15/development 477:
* Origin: User error - (R)eplace, (I)gnore, (K)ill ?? (2:2476/493)
231/992
633/260
2501/209
+----------------------------------------------------------------------------+
From: Herbert Rosenau 08-Dec-99 18:22:21
To: Louis Aubree 10-Dec-99 06:58:06
Subj: Warp 3 install
LA> I understand that Warp 3 _blue_ spine (with WinOS2 inside) can be
LA> installed on HPFS, but I still don't understand the same for the
LA> _red_ spine version.
Each OS/2 version since OS/2 1.3 (the first with HPFS) can be installed on
each HPFS formatted drive - so long as the whole drive is under track 1024
(the BIOS limit).
LA> I think that Warp _red_ spine has to be installed _after_ DOS and
LA> Win3.1x, on the same primary partition, so this partition has to
LA> be FAT16 formated.
Noways. It can (optionally) integrate the pre installed Win 3.1x - but
independant of the drive it is installed itself.
LA> Then, the user could choose to never use Dual Boot anymore and
LA> run anything (hum!) from OS/2.
Nowhere! Dual boot is NOT designed for an productive environment. You my use
it to test OS/2 but not more.
LA> Where am I wrong? Is it possible to install Win3.1x _after_ Warp
LA> 3 red spine on an HPFS partition? Or use another trick?
You my install Win3.x under DOS on drive C: (FAT) - and you can have installed
OS/2 on drive g: (HPFS). If you don't have already Win support installed you
can do so by starting the installation program and integrate it then.
It would be quite simper to install DOS/Win first and then install OS/2 on its
own drive because OS/2 will dedekt the pre installed windows and ask you to
integrate that.
--- Sqed/32 1.15/development 392:
* Origin: Kann den DFUe Suende sein ?! (2:2476/493)
231/992
633/260
2501/209
+----------------------------------------------------------------------------+
From: Jack Pfisterer 08-Dec-99 10:46:00
To: SINISA PAVLOVIC 10-Dec-99 06:58:06
Subj: Re: Another leaky fixpak?
-=> SINISA PAVLOVIC wrote to All <=-
JP> Contact Ivan Adzhubei, ivan@protein.bio.msu.su and ask if he still has
JP> it available for FTP. That's where I got the copy I installed. I've
JP> heard there's an even-newer one out, but haven't been able to locate
JP> it.
SP> But just to be sure that I'm not going to get the same one, PMMERGE
SP> that I have here is:
SP> PMMERGE.DLL 1238971 bytes 08.Oct.1998 12.14pm
The one from ivan@protein.bio.msu.su is dated 10 Oct 99 and is 1254973
bytes.
JP> newer keyboard.dcp.
SP> What is that for?
I really don't know. It just happens to be included. Probably just
some very specialized fixes.
Jack P.
~~~ Blue Wave/QuickBBS
* Origin: Hooray For Hollywood * Los Angeles,CA -=- 213-653-7508 (1:102/749)
231/992
633/260
2501/209
+----------------------------------------------------------------------------+
From: Holger Granholm 07-Dec-99 20:30:00
To: Kees Bergwerf 10-Dec-99 06:58:06
Subj: not enough diskspace
In a message dated 12-05-99, Kees Bergwerf said to All:
Hello Kees,
KB>memsize (and memsize did give nothing but trouble: it worked fine
KB>for a while but I tried to change a setting in the config: use
KB>theseus, and then the program crashed and I have not been able to
KB>start it again without crashing.)
Known problem :-( I too installed memsize but in my case I never got
it to work so I deleted it. However, I found an entry in the OS2.INI
still referring to memsz and the directory it had been installed in.
So I asked Rick Papo for a proper uninstall program. In the meantime
I installed memsz again into the same directory as before.
When I ran the uninstall.cmd that I received from Rick, it told me that
it couldn't find memsize and that it "probably" wasn't installed !!!!
Then I deleted the whole shebang again but the reference of course is
still in the .INI file. God only knows how many references there are
to programs that have been installed and then removed again.
Happy Holidays,
Holger
___
* MR/2 2.26 * Welcome to Hell. Here is your copy of Windows 98.
--- PCBoard (R) v15.22 (OS/2) 2
* Origin: Coming to you from the Sunny Aland Islands. (2:20/228)
772/1
+----------------------------------------------------------------------------+
From: Linda Proulx 08-Dec-99 18:00:28
To: All 10-Dec-99 06:58:06
Subj: File addresses
Greetings,
I appreciate folk giving pointers about newer files for installing, etc.
But it can be extrememly difficult to find anything on the IBM site.
If someone suggests a file from a site, my internet person would be very
appreciative if one could also put the whole pointer for it.
Thanks.
Linda
... Be nice to moderators. They HATE that!
--- MultiMail/MS-DOS v0.32
* Origin: Robin's Universe BBS - Winnipeg MB (1:348/807)
278/111
+----------------------------------------------------------------------------+
From: Linda Proulx 08-Dec-99 20:41:13
To: Cyrill Vakhneyev 10-Dec-99 06:58:06
Subj: Re: Newer update
Greetings and Salutations,
-=> Cyrill Vakhneyev wrote to Linda Proulx <=-
CV> Get latest ibm1s506.add (idedasd.exe at IBM's DriverPack). RTFM
Do you know the address for it?
Anon,
Linda
... "I try to keep an open mind, but not so open that my brains fall out."
--- MultiMail/MS-DOS v0.32
* Origin: Robin's Universe BBS - Winnipeg MB (1:348/807)
278/111
+----------------------------------------------------------------------------+
From: Craig Ford 08-Dec-99 21:32:25
To: Michael Box 10-Dec-99 06:58:06
Subj: Help!
Michael Box wrote the following to Craig Ford, and I quote (in part):
-=> Note: Copied from OS2 by WIMM/2 1.31
CF> With IBM's withdrawl of support for Warp3, I finally upgraded my
CF> installation to Merlin, and tried to install FP12 to it. Alas,
CF> application of the Fixpak failed due to a checksum error in
CF> PMMERGE.DLL.
CF> Would some one be so kind as to tell me the size and timestamp of
CF> PMMERGE.DLL in a virgin Warp4 installation? It would also help if
CF> someone could tell me in which immage file on the distribution CD it
CF> is contained.
MB> I ran into the same problem and thought it was something I was
MB> doing wrong. Although it was with fixpack 11. I've downloaded the
MB> darn FP 3 times and still got the same results. My system is warp 4
MB> with no FP's applied. I have Peer and TCPIP networking running. If
MB> you come across a fix or work around, I'd love to hear about it.
MB> I've just gotta upgrade this thing soon.
It took an "all-nighter" to get it going. :-(
I extracted the original PMMERGE.DLL from the DISK 8 of the distribution CD,
and replaced the copy on my drive.
I also obtained a fresh copy of the XR_M012.1DK from IBM's FTP site.
I deleted all remants of the suspended FP application, and tried it again.
Whooooopeeeee!
Warp 3 was never this difficult.
Regards....
Craig
aka: cford@ix.netcom.com
: craig.ford@2001.conchbbs.com
--- timEd/2 1.10.y2k+
* Origin: Dayze of Futures Past * V.Everything * 281-458-0237 * (1:106/2001)
231/992
633/260
2501/209
+----------------------------------------------------------------------------+
From: Eddy Thilleman 07-Dec-99 11:02:16
To: Bat Lang 10-Dec-99 06:58:06
Subj: cache
Hello Bat,
05 Dec 99 03:05, Bat Lang wrote to Peter French:
BL> Where is this information 'entered' into your configuration? Thanks.
I've in my startup.cmd:
cache -diskidle:3000 -maxage:6000 -bufferidle:1500 -lazy:3
Greetings -=Eddy=- email: eddy.thilleman@net.hcc.nl
... VirCure: Windows Found...delete? [Y/Yeah/Heck Yeah]?
--- GoldED/2 3.0.1
* Origin: Windows98 is a graphic DOS extender (2:280/5143.7)
772/1
+----------------------------------------------------------------------------+
From: Gord Hannah 08-Dec-99 21:51:00
To: Louis Aubree 10-Dec-99 06:58:06
Subj: Warp 3 install
Replying to a message from Louis Aubree 2:326/2 to Gord Hannah,
About Warp 3 install, On Mon Dec 06 1999
LA> I understand that Warp 3 _blue_ spine (with WinOS2 inside) can be
LA> installed on HPFS, but I still don't understand the same for the
LA> _red_ spine version.
The above was my installation Blue (Connect).
LA> P.S. Eddy Thilleman also replied: he also believes Warp 3 red cannot
LA> be installed on HPFS.
I would go with what Eddy is telling you he has more experience with OS/2 than
I do.
Hope this helps. Keep us posted.
We are a fine board trying to make it better.
http://www.pris.bc.ca/ghannah
ghannah@pris.bc.ca
Gord
-=Team OS/2=-
--- timEd/2 1.10.y2k+
* Origin: Marsh BBS (c) [Dawson Creek BC Canada] 1-250-786-7921 (1:17/23.1)
278/111
+----------------------------------------------------------------------------+
From: Gord Hannah 08-Dec-99 05:53:15
To: Holger Granholm 10-Dec-99 06:58:06
Subj: USB
Replying to a message from Holger Granholm 2:20/228 to Andy Roberts,
About USB, On Mon Dec 06 1999
AR>I'm not sure what is going to be developed to replace the Pentium.
HG> In my case, AMD will replace the Pentium. I don't see the need to
HG> feed Intel any more than M$.
Good choice, I have ran OS/2 with AMD's since my first install, I wont have an
Intel chip at all, reason is simple Intel lied to the computing world about
the Floating Point problem, all be it a lie of omission, it was still a lie.
Besides AMD's are cheaper, and do just as good a job. The system I am writing
this on is being powered by an AMD K6/2-300.
Hope this helps. Keep us posted.
We are a fine board trying to make it better.
http://www.pris.bc.ca/ghannah
ghannah@pris.bc.ca
Gord
-=Team OS/2=-
--- timEd/2 1.10.y2k+
* Origin: Marsh BBS (c) [Dawson Creek BC Canada] 1-250-786-7921 (1:17/23.1)
278/111
+----------------------------------------------------------------------------+
From: Charles Gaefke 06-Dec-99 18:41:22
To: Wes Newell 10-Dec-99 06:58:06
Subj: Re: DELTREE
WN> My dos 6.22 deltree command works quite well on W4. I don't have msdos
WN> installed. All my drives are hpfs. I can run it from an os/2 session
(which
WN> automatically brings up a dos vdm), or of course I can run it from a dos
vd
I wrote a util called DeltreeX. It deltree's directories fast.
It's X because it doesn't prompt "are you sure".
So, don't do "deltreex c:\".
:)
EMail me if you want it.
C. Gaefke
cdgaefke@earthlink.net
... I love my job! Do you?
--- Renegade v98-356a Dos
* Origin: LOTL/2 * www.icubed.com/~cdgaefke (1:129/230)
231/992
633/260
2501/209
+----------------------------------------------------------------------------+
From: Steve McCrystal 08-Dec-99 06:40:06
To: Eddy Thilleman 10-Dec-99 06:58:06
Subj: cache
;
In a msg of <Monday December 06 1999>, Eddy Thilleman writes to Herbert
Rosenau:
;
Eddy,
HR>> run=f:\os2\cache.exe /LAZY:9 /MAXAGE:12500 /DISKIDLE:7500
HR>> /BUFFERIDLE:2000 /READAHEAD:1
ET> 9 lazy write workers? I haven't seen mentioned that high before.
I noticed that, and hadn't seen it before either, so I checked the online
docs. They say that LAZY takes one of two parameters... OFF or ON. I then
modified my own cache statement, changing LAZY:3 to LAZY:9 and the resulting
display shows there are indeed 9 lazy workers allocated. I have no idea what
difference it might make, especially given the obvious inaccuracy of the docs,
but I think I'll play with it a bit! :^)
-[Steve]-
--- GoldED/2 3.0.1/#
* Origin: -[Steve's Place]- New Berlin, WI (FidoNet 1:154/731.2)
278/111
+----------------------------------------------------------------------------+
From: Linda Proulx 09-Dec-99 12:43:06
To: All 10-Dec-99 06:58:06
Subj: Happy Holidays!
Greetings & Salutations Everybody!
Before everyone gets into the hectic of holiday season, I thought that
I would wish everyone a joyous and safe holiday season and a happy
millenium.
May 2000 be like your computing, enjoyable.
Take care.
Linda
... It's only a hobby...it's only a hobby...it's only a hobby...
--- MultiMail/MS-DOS v0.32
* Origin: Robin's Universe BBS - Winnipeg MB (1:348/807)
278/111
+----------------------------------------------------------------------------+
From: Eddy Thilleman 08-Dec-99 10:15:00
To: Don Guy 10-Dec-99 06:58:06
Subj: wave files?
Hello Don,
06 Dec 99 08:14, Don Guy wrote to Eddy Thilleman:
DG> On its way to the e-mail address above...
I got it. Thanks. (for the rest here :)
Greetings -=Eddy=- email: eddy.thilleman@net.hcc.nl
... Windows stinks!
--- GoldED/2 3.0.1
* Origin: Windows95 is a graphic DOS extender (2:280/5143.7)
772/1
+----------------------------------------------------------------------------+
From: Eddy Thilleman 08-Dec-99 10:42:00
To: Peter Knapper 10-Dec-99 06:58:06
Subj: Power failures
Hello Peter,
07 Dec 99 21:10, Peter Knapper wrote to All:
PK> corrupting its Root directory entry or a pointer to the Root directory
PK> entry, if there is a power failure and the system is not shut down
PK> cleanly. If it IS shutdown cleanly, the next boot up is fine and all
So your real problem are power failures. Have you considered an UPS, to be
able to shut down cleanly when a power failures hits?
Greetings -=Eddy=- email: eddy.thilleman@net.hcc.nl
... "Accountability is Un-American!!" - Opus
--- GoldED/2 3.0.1
* Origin: Windows98 is a graphic DOS extender (2:280/5143.7)
772/1
+----------------------------------------------------------------------------+
From: Michael Box 09-Dec-99 18:44:26
To: Craig Ford 10-Dec-99 06:58:06
Subj: Help!
Hello Craig.
Wednesday December 08 1999 21:32, you wrote to me:
CF> It took an "all-nighter" to get it going. :-(
CF> I extracted the original PMMERGE.DLL from the DISK 8 of the
CF> distribution CD, and replaced the copy on my drive.
CF> I also obtained a fresh copy of the XR_M012.1DK from IBM's FTP site.
CF> I deleted all remants of the suspended FP application, and tried it
CF> again.
Thanks for the info... Looks like I have a project for sometime this weekend..
Michael
--- 3.0.1
* Origin: Mikey's Mystery Mailer (1:103/100)
278/111
+----------------------------------------------------------------------------+
From: Murray Lesser 09-Dec-99 08:48:00
To: Will Honea 09-Dec-99 08:48:00
Subj: OS20MEMU and THESEUS 3
(Excerpts from a message dated 12-08-99, Will Honea to Murray Lesser)
Hi Will-
WH>The version is Thesues3, last copy I saw at Testcase was Th?/3000.zip
>- same content as originally offersd. The DLL is theseus5.sys
ML> I am using Theseus 3 (theseus5.sys in config.sys). Do you
ML> really mean you are using a later version, Theseus 5, or was that a
ML> slip of the fingers? If you meant it, where did you get it?
WH>Same animal. Works well for me. AIR, you rename the DLL in
>distribution to Theseus0.DLL and that's the only Theseusx.DLL I've
>ever noticed beung loaded.
Thanks. I am using the self-extracting-file version I downloaded
from Pete's BBS: THES3000.EXE, 1160 K, 10-09-99. Invoked, the "product
information" pop-up says it is version 3.000.00.
Nothing in the readme about renaming any DLL; there are two:
theseus0.dll and theseus1.dll. Utility seems to work OK but I am still
learning.
Regards,
--Murray
<Team PL/I>
___
* MR/2 2.25 #120 * Happily hitchhiking on the Information Highway
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Ron Nicholls 10-Dec-99 20:01:00
To: Will Honea 10-Dec-99 20:01:00
Subj: Help!
WH> OS2\DLL directory, and run "UNPACK <archive path>\pmmerge.dl*".
WH> That will recover your previous one. You might want to try the
WH> updated PMMERGE.DLL distributed after FP12 came out - supposedly it
WH> fixed a nagging memory leak.
I think I have that memory leak. Where is the
updated file posted. Will?
-
-
Regards RonN
-
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Will Honea 10-Dec-99 17:30:00
To: Louis Aubree 10-Dec-99 17:30:00
Subj: Warp 3 install
Louis Aubree wrote to Gord Hannah on 12-06-1999
LA>
LA> installed on HPFS, but I still don't understand the same for the
LA> _red_ spine version.
LA>
LA> I think that Warp _red_ spine has to be installed _after_ DOS and
LA> Win3.1x, on the same primary partition, so this partition has to
LA> be FAT16 formated. Then, the user could choose to never use Dual
LA> Boot anymore and run anything (hum!) from OS/2. Where am I wrong?
LA> Is it possible to install Win3.1x _after_ Warp 3 red spine on an
LA> HPFS partition? Or use another trick?
Warp 3 Red has to be installed after Win 3.1: TRUE in most cases. Win
3.1 can in fact reside on ANY fat-formatted partition and there were
some people who claimed to have gotten it installed on HPFS - runs only
under OS/2 that way - and I recall seeing a way to add Win 3.1 after
OS/2 is installed but that is ancient history by now.
As for the rest, Warp 3 can be installed on ANY bootable partition.
FAT/ HPFS is not an installation determinant nor is the precise
partition. The only requirement is that the partition containing Win
3.1 be accessible by OS/2. This usually results in DOS/Win 3.1 on C:
FAT with OS/2 on D: or higher, preferably on HPFS.
Will Honea <whonea@codenet.net>
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Will Honea 10-Dec-99 17:34:01
To: Ron Nicholls 10-Dec-99 17:34:01
Subj: Fix_Paks
Ron Nicholls wrote to All on 12-09-1999
RN> Are the early fix paks for Warp 4 ( 1 to 8 )
RN> still available anywhere.
I have nearly all of them on the DEVCON CD's and I think I saw an FTP
site somewhere that had them, but don't ask me to quote the URL. Try
FTPSEARCH for XR_M00n.DSK or .ZIP with variations if you want to look.
What do you need exactly?
Will Honea <whonea@codenet.net>
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Will Honea 10-Dec-99 23:06:00
To: Ron Nicholls 10-Dec-99 23:06:00
Subj: Help!
Ron Nicholls wrote to Will Honea on 12-10-1999
RN> I think I have that memory leak. Where is the
RN> updated file posted. Will?
I think I saw it on Hobbes - pmr00052.zip I think.
Will Honea <whonea@codenet.net>
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Will Honea 10-Dec-99 23:13:01
To: Peter Knapper 10-Dec-99 23:13:01
Subj: Power failures
Peter Knapper wrote to Eddy Thilleman on 12-10-1999
PK> That power failures are MONTHS apart is irrelevant, there
PK> are other reasons why the system fails to shut down
PK> correctly. Regardless of the reason for it, if the system
PK> is NOT shut down "normally", then the HPFS partition ROOT
PK> directory entry cannot be found upon restart!
When you put it that way, it caught my eye. So Murphy lives at you
house now?
I would be curious to see what DFSEE reported about that partition
after a dirty shutdown (boot to another partition/floppy, no chkdsk of
course but DFSEE will take care of the dirty bit). My initial thoughts
all run to a hardware problem with the disk, right in the superblock
sector, of course... Tell Murph hello as he's a regular here.
Will Honea <whonea@codenet.net>
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Murray Lesser 10-Dec-99 09:51:00
To: Louis Aubree 10-Dec-99 09:51:00
Subj: Warp 3 install
(Excerpts from a message dated 12-06-99, Louis Aubree to Gord Hannah)
Hi Louis--
LA>> Install Warp 3 red with Dual Boot on HPFS ? Is it possible ? With
LA>> Win apps needed?
LA>I think that Warp _red_ spine has to be installed _after_ DOS and
>Win3.1x, on the same primary partition, so this partition has to be
>FAT16 formated. Then, the user could choose to never use Dual Boot
>anymore and run anything (hum!) from OS/2. Where am I wrong? Is it
>possible to install Win3.1x _after_ Warp 3 red spine on an HPFS
>partition? Or use another trick?
LA>P.S. Eddy Thilleman also replied: he also believes Warp 3 red cannot
>be installed on HPFS.
I cannot help much in this installation argument, because I have
never done Windows. But I can assure you, from several years'
experience, that Warp 3 red can indeed be installed in an HPFS
partition.
My understanding is that installing Dual Boot with the "easy
installation" method requires that OS/2 and DOS both be installed in FAT
partitions. According to my leftover "User's Guide to OS/2 Warp[3]"
manual, you can install Win3x in a Fat partition _after_ you have
installed OS/2 in an HPFS partition. RTFM.
Regards,
--Murray
<Team PL/I>
___
* MR/2 2.25 #120 * One printed manual is worth a thousand INF files
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
From: Murray Lesser 10-Dec-99 10:05:01
To: Holger Granholm 10-Dec-99 10:05:01
Subj: not enough diskspace
(Excerpts from a message dated 12-07-99, Holger Granholm to Kees
Bergwerf)
Hi Holger--
HG>Then I deleted the whole shebang again but the reference of course is
>still in the .INI file. God only knows how many references there are
>to programs that have been installed and then removed again.
IMO, every OS/2 user should have a program that cleans up the .INI
files and all the other "handle" information that is left behind when
object files are deleted from the system. I use UniMaint v 5.10.02 (a
shrink-wrapped program) that also does many other things (such as
backing up the desktop and essential files). I run the cleanup portion
of UniMaint after every object deletion, and the backup portion after
every desktop change (I keep the most recent five backups). But, I am
told that there are many other programs that clean up the two .INI
files, some of which are freeware. I suggest that you look into it.
"Uninstall" programs are notorious for being short-sighted. The one
that comes with UniMaint includes special warnings to the user, and a
means for telling it exactly what you want to uninstall along with the
app itself (including references in config.sys). I find it more bother
to use than it is worth :-(.
Regards,
--Murray
<Team PL/I>
___
* MR/2 2.25 #120 * One printed manual is worth a thousand INF files
--- Maximus/2 2.02
* Origin: OS/2 Shareware BBS, telnet://bbs.os2bbs.com (1:109/347)
+----------------------------------------------------------------------------+
+============================================================================+