Does FP 15 (or FP13) break Colorworks v2.0 (testing Scitech DDPro)?
Cathy Sullivan
followed by a completely new re-installation of removed and recreated HD
partition (fubar ini's). After re-installing Warp 4.0, I installed
WarpUp's FP13 (for the first time) because I want to install Odin.
Since I had a totally clean system, I went ahead and applied FP15 via
RSU...a smooth install. DD02 failed 3 times...hung up while Service was
running without ever getting an active button to continue. I am on DSL,
so RSU is quick.
I have noticed a couple of problems since FP13...network drives set to
auto-connect at logon do not...they are inactive on logon and must be
reconnected each time. But, the REALLY BAD problem for me is that
Colorworks v.2.0 with the appropriate patch for Warp 4.0 installed no
longer displays properly.
Yesterday, I installed a brand new ATI Radeon 64MB SDR video card. I
had already installed the IBM Scitech SE video driver for use with the
2MB Matrox MGA card that I put into the machine after "Puff the Magic
Dragon's" recent visit while searching for information on what video
cards WILL work as flawlessly as possible with OS/2. I still had visual
anomolies in a rather large image I was working on when the machine
failed.
At 100% image size, I can see the entire image, but at 10%, all I see is
a narrow stripe down the left hand side of the image. At 100%,
scrolling the image to work on lower sections results in horizontal
"bands" repeating sections of the image beneath (or above) it.
I must complete the image and I am unwilling to damage it due to a
problem. I futzed with the whole mess for several hours again last
night, and have come to the conclusion that I am hopelessly lost as to
how to repair the problem. It does not appear to be the image or video
resolution or refresh rates...the same image comes up fine in a WinOS2
graphics app, and the rest of the display has been good so far.
I am currently testing Sctiech's Display Doctor Pro (20 more days) and
will happily buy it if it provides better display than the IBM SE
version, since ATI has no drivers. I really wanted another Matrox (my
puffed card was a 16MB Millinium II and worked great!), but would have
to wait for shipment of a 32MB G450 for about the same price as the ATI
Radeon which I could get retail immediately.
Any help would be appreciated. Thanks!!!
- Cat
Cathy Sullivan
catm...@earthlink.net
"unwilling to give up my operating system...OS/2"
Klaus Staedtler-Przyborski
> Recently I had reason (smoke) to upgrade all hardware except HD and NIC,
> followed by a completely new re-installation of removed and recreated HD
> partition (fubar ini's). After re-installing Warp 4.0, I installed
> WarpUp's FP13 (for the first time) because I want to install Odin.
> Since I had a totally clean system, I went ahead and applied FP15 via
> RSU...a smooth install. DD02 failed 3 times...hung up while Service was
> running without ever getting an active button to continue. I am on DSL,
> so RSU is quick.
Best procedure is to install FP15 directly on Warp 4 unfixed and then apply
DD02
Klaus Staedtler
cmh...@umich.edu
>I have noticed a couple of problems since FP13...network drives set to
>auto-connect at logon do not...they are inactive on logon and must be
>reconnected each time. But, the REALLY BAD problem for me is that
>Colorworks v.2.0 with the appropriate patch for Warp 4.0 installed no
>longer displays properly.
>Yesterday, I installed a brand new ATI Radeon 64MB SDR video card. I had
>already installed the IBM Scitech SE video driver for use with the 2MB
>Matrox MGA card that I put into the machine after "Puff the Magic
>Dragon's" recent visit while searching for information on what video
>cards WILL work as flawlessly as possible with OS/2. I still had visual
>anomolies in a rather large image I was working on when the machine
>failed.
>At 100% image size, I can see the entire image, but at 10%, all I see is
>a narrow stripe down the left hand side of the image. At 100%, scrolling
>the image to work on lower sections results in horizontal "bands"
>repeating sections of the image beneath (or above) it.
Cathy:
This is a known problem (at least scitechsoft knows about it) and it's
related to a bug in gradd. As of the convenience pack (in my case, ECS
GA), it's not fixed. It might be fixed in CP fixpak 1 (don't know; haven't
yet OK'd it for ecomstation). There definitely won't be a fix for Warp
(unless you can scrounge a gradd/pmmerge combo that fixes the problem).
Unfortunately, the only thing you can do is use the most compatible native
driver. All gradd based ones will have the bug.
--
Chris M. Hall
Assistant Research Scientist
Dept. of Geological Sciences
University of Michigan
2534 C.C. Little Building
425 E. University Ave.
Ann Arbor, MI 48109-2534
Thank you Andre, I'll have the veal piccate.
Al Savage
<staedtler-...@web.de> wrote:
> Best procedure is to install FP15 directly on Warp 4 unfixed and then apply
> DD02
I agree.
http://asavage.fdns.net/OS2/Warp4Install/Warp4Install.html
--
Regards,
Al S.
* Hillman & Rootes Group manuals online: http://asavage.fdns.net/Hillman
* Ford Falcon manuals online: http://FalconFAQ.fdns.net
This OS/2 system ("Tori", W4 FP15) uptime is 5 days 10:59 hours
Cathy Sullivan
- Cat
Cathy Sullivan
the wrong processing loop. I know there was a reason why I did the Warp-Up CD
first, but I can't remember exactly what it was...possibly to avoid trying to
get to the RSU site with Web Explorer since I have *no* bookmarks, don't have
it "inked" anywhere, and so many web pages don't even load.
Is there any known way to repair the auto-connecting network drives? It's not
a critical situation...my home network...but it's a pain to have to reconnect
each time.
- Cat
Graham C. Norris
> Is there any known way to repair the auto-connecting network drives? It's not
> a critical situation...my home network...but it's a pain to have to reconnect
> each time.
Open up Shared Resources and Network Connections (in Network Services
under Connections), select the Connections page: each connection has an
Auto-connect setting which can be changed using the Update... button
while the line is selcted.
Graham.
--
*-* Please remove spam free prefix before replying *-*
Al Savage
wrote:
> I am currently testing Sctiech's Display Doctor Pro (20 more days) and
> will happily buy it if it provides better display than the IBM SE
> version, since ATI has no drivers. I really wanted another Matrox (my
> puffed card was a 16MB Millinium II and worked great!), but would have
> to wait for shipment of a 32MB G450 for about the same price as the ATI
> Radeon which I could get retail immediately.
I really, really like Matrox for vid cards. Mill only, of course. The
same OS/2 driver set for ALL of the Mill series, from Mill I to Mill
G450, same driver. Nice.
--
Regards,
Al S.
* Hillman & Rootes Group manuals online: http://asavage.fdns.net/Hillman
* Ford Falcon manuals online: http://FalconFAQ.fdns.net
This OS/2 system ("Tori", W4 FP15) uptime is 6 days 00:39 hours
Cathy Sullivan
to fix the auto-connect thing. Didn't work. Tried it again just now (3rd or 4th
time now) but still didn't work.
I also tried deleting all connections and re-establishing them, and unchecking the
*connect to resource at logon* selection, logging off, logging on (can't remember if
I rebooted or not...think I might have), and setting them all up again with the same
negative result.
I *had* already established these connections prior to FP13 (I control the printer
right now) and they were active when I Warp('d)Up.
The Shared Resources icon is one of only about 20 icons that I allow to live on my
desktop. I just love the little guy...perhaps because I support Windows xxx
professionally and despise the hoops that must be jumped through to set up the same
things that are ALL in the same OS/2 *network* notebook. ;-)
Thank you for the suggestion. I really appreciate your help. Wish it had been
that. I'm guessing (heh!) that because I had already established them and they were
*running* while the FP was being applied, perhaps *something* was not properly
updated when the fixpack was applied...???
- Cat
Cathy Sullivan
work...it was a '"certified" by SDD and IBM' chip...ATI had the most RAM and
was 20 minutes away. I have had previous ATI cards in my OS/2 machine over
the years and they worked fine. I have ATI memories going back into the
mid-'80's. I labored and fretted over the decision for most of the weekend,
surfing for info, and video card availability. I ordered the card on-line
from a local firm after they closed and picked it up Sunday morning.
I have written to ATI for suggestions...pleading they NOT toss out my email
when they read the "OS/2" part. The card actually has the words "Rage 6"
printed on it. I am hoping that Rage drivers (which ran my video card just
prior to the Millinium II) will at least drive the card. I don't play games
or watch TV...I do graphics, and I truly need only good color resolution and
an accurate display.
- Cat
eegr...@dont-spam-me.org
>Ooh...sorry, I should have said that the Update button was the first
>thing I tried to fix the auto-connect thing. Didn't work. Tried it
>again just now (3rd or 4th time now) but still didn't work.
... remainder snipped ...
I don't know if there is a fix for this or not, but you can certainly
use your STARTUP.CMD to LOGON and NET USE the resources you need and
save yourself the need to do it manually.
-- Dave
-----------------------------------------------------------
dhdurgee<at>verizon<dot>net
-----------------------------------------------------------
cmh...@umich.edu
at 11:59 AM, Cathy Sullivan <catm...@earthlink.net> said:
>Ooh...sorry, I should have said that the Update button was the first
>thing I tried to fix the auto-connect thing. Didn't work. Tried it
>again just now (3rd or 4th time now) but still didn't work.
Cat:
I've seen this behaviour as well, both at fp15 (latest 16bit tcpip stack
fixes) and with ECS (tcpip 4.3). It's particularly bad with Windows
machines, but I've seen it as well when connecting with OS/2 machines. The
workaround I use is a script segment in startup.cmd that would look
something like this:
net start peer
logon /v:local
net use x: \\machine\resource
The first line will start file & print, the second brings up the logon
window and the third starts the connection. Replace "x" with the drive
letter you want to use, and the machine and resource name would be the
connecting resource. It may not be elegant, but it works. Also, you'd want
to remove the "start peer" object from the startup folder.
As for your video problem, I think you should try some of the earlier ATI
drivers (mach64, rage, etc.). But be prepared to revert to vga on boot up,
and don't try pushing refresh rate limits. Video is one of the few areas
where you can actually damage things.
Cathy Sullivan
cmh...@umich.edu wrote:
> In <3B824DF7...@earthlink.net>, on 08/21/01
> at 11:59 AM, Cathy Sullivan <catm...@earthlink.net> said:
>
> >Ooh...sorry, I should have said that the Update button was the first
> >thing I tried to fix the auto-connect thing. Didn't work. Tried it
> >again just now (3rd or 4th time now) but still didn't work.
>
> Cat:
>
> I've seen this behaviour as well, both at fp15 (latest 16bit tcpip stack
> fixes) and with ECS (tcpip 4.3). It's particularly bad with Windows
> machines,
I've seen this problem with Windows machines, particularly in multi-platform
networks when all users are trying to log on at the same time using hubs
instead of switches...like when a server has just come back on-line after a
crash.
> but I've seen it as well when connecting with OS/2 machines.
My home "test and train" network is the only one I've worked with that has
OS/2 on it, though I've had OS/2 machines under my professional support. This
is the first time it's been a problem. I was on FP12 before Puff, and had no
trouble with automatic network connections prior to this incident. (I had to
replace my NIC last night. I guess it has been failing since the
surge/spike...not sure what happened, but the UPS sang a very unhappy song and
OS/2 couldn't control mouse cursor placement. Rebooting to recover ended the
system. Good NIC...to continue to work after that!)
I am on the 16-bit TCP/IP stack. I read that you should not go to the 32-bit
stack unless the machine works as a TCP/IP server. Having no further
information than that statement, there *are* some critical parts of my home
workstation that I am unwilling to futz with an awful lot when I don't have
what I consider to be adequate information.
> The workaround I use is a script segment in startup.cmd that would look
> something like this:
>
> net start peer
> logon /v:local
> net use x: \\machine\resource
>
> The first line will start file & print, the second brings up the logon
> window and the third starts the connection. Replace "x" with the drive
> letter you want to use, and the machine and resource name would be the
> connecting resource. It may not be elegant, but it works. Also, you'd want
> to remove the "start peer" object from the startup folder.
Not only is it not elegant and extremely efficient, it is a blast from the
past. All the old "dos" networking connections used to start pretty much the
same way...Novell 2/3/4 DOS and Windows clients, LANtastic clients...but I'm
dating myself...
I only have TCP/IP Startup in the Start Up folder. I click on a Logon shadow
on my desktop for the connection. Even though my machine has no network
password, is always on, always connected to the internet via DSL, I'm behind a
router and firewall so I could have the machine auto-logon from the
startup.cmd file. But Windows machines tend to hang when trying to do too
much on bootup, so I go easy on OS/2 also.
>
>
> As for your video problem, I think you should try some of the earlier ATI
> drivers (mach64, rage, etc.). But be prepared to revert to vga on boot up,
> and don't try pushing refresh rate limits. Video is one of the few areas
> where you can actually damage things.
>
This I do know. I was present when someone puffed his monitor in just this
way...dreadful, frightening ,sizzling, crackling sounds...you can't' get to
the power switch fast enough.
I also know about reverting to VGA, but I've smoked enough PC vapor for a
while and damage to the hardware is the reason I have not been futzing with
the machine in favor of patience...waiting for word from ATI regarding
compatibilities. I wrote to their tech support last night for any assistance
they might be willing to give *before* I get back into my usual independent
("cat") mode.
I really don't care about anything but 800 x 600 resolution (I can almost see
it without my glasses ;-) ), straight video with good color. I can zoom in
to 2000% percent with Colorworks if I need to. As long as the refresh rate is
high enough so that I am not watching the screen re-draw, keeping eyestrain to
a minimum, I care not how much faster it is. I lived in lovely Germany for
several years, and watching "50-cycle light bulb quiver" is no more my
favorite modus operandi than watching each character appear on the screen from
CompuServe at 300 baud!
- Cat
Bill "Wild Willy" Kredentser
> cmh...@umich.edu wrote:
> > In <3B824DF7...@earthlink.net>, on 08/21/01
> > at 11:59 AM, Cathy Sullivan <catm...@earthlink.net> said:
> startup.cmd file. But Windows machines tend to hang when trying to do too
> much on bootup, so I go easy on OS/2 also.
Agreed. Even on my office system, which is permanently connected to our
corporate LAN, I don't do the Peer startup from STARTUP.CMD. I have a
Program Reference Object in my Startup folder pointing to a REXX script
that starts with a SysSleep for 15 seconds, then it does the NET command &
LOGON. The SysSleep allows the Desktop to come up & all the icons to do
their usual flickering during startup. The delay interval would vary
depending on CPU speed & what else you start at the same time. At home,
on my dial up, of course, I don't even start Peer unless I'm dialed into
work, and even then, I don't always start Peer, so it's a manually
executed script even then.
--
WW
Team OS/2 Cincinnati & PROUD OF IT!
William L. Hartzell
Cathy Sullivan wrote:
>
I always have been in favor of using the optional command files that
TCPSTART.CMD provides. I'm speaking of B4TCP.CMD and TCPEXIT.CMD. I
use the B4TCP.CMD to place those modifications to the stack that one
cannot place in STARTUP.CMD. The biggie here is starting the firewall.
Next, I let the servers start in TCPSTART.CMD, if any. Then, I use the
TCPEXIT.CMD to start all those stack using programs. I've found that it
is faster on the startup of the desktop and the included applications to
sequenced these startups. Don't use of STARTUP.CMD and the STARTUP
folder to start things just when the system can do nothing with them,
like starting PEER. PEER cannot start until the stack is stable, but if
it is in STARTUP.CMD it is consuming resources that could be better used
elsewhere, like starting the desktop. I've found that I can have PEER
up just after I click Logon for AIM, if I am fast enough, else PEER is
waiting me. Ditto if you place net LOGON as the last item in the
TCPEXIT.CMD file, instead of using AIM for example. BTW, the 32-bit
stack is standard on the latest releases of Warp. The firewall is in
the 32-bit stack. I'm including copies of my two above mentioned files
for your perusal. Don't get me wrong, I do use the STARTUP folder to
start my UPS monitoring daemon and to start my USB monitoring daemon,
and some others. Plus, it is necessary to include the TCPSTART.CMD.
:-) I don't use STARTUP.CMD because so many of IBM's, et al, installers
do. PS. I've let TCPEXIT.CMD become a catch-all for cleaning up the
temp files and a few other house hold duties, which are tag on the end.
My B4TCP.CMD
-----
inetcfg -s tcprwinsize 65536
inetcfg -s tcpswinsize 65536
inetcfg -s keepalive 60
inetcfg -s synattack 1
inetcfg -s syncookie 1
inetcfg -s timestmp 1
cfgfilt -u -i
inetcfg -s firewall 1
start /b /n /min c:\mptn\bin\fssd.exe
----------
My TCPEXIT.CMD
----
start /c /min c:\ibmlan\netprog\netstcmd.cmd start peer
SETLOCAL
set user="William L. Hartzell"
start /b /min /n d:\tcpipapps\identd\identd.exe
start /b /min /n d:\tcpipapps\tcp-leds\tcpleds.exe
start /b /min /n d:\tcpipapps\time-nist\nistime.exe -S
ENDLOCAL
start /b /min C:\SVA\BIN\AGENT\SVASTART.CMD
start /min D:\TCPIPAPPS\AIM\AIM.CMD
SETLOCAL
D:
CD \TCPIPAPPS\PMDC
start /min D:\TCPIPAPPS\PMDC\pmdc.exe
ENDLOCAL
start /min c:\ibmlan\netprog\netmsg.exe
SETLOCAL
d:
CD \TCPIPAPPS\DTOC
SET HOSTNAME=c390320-a.grlnd1.tx.home.com
start /min D:\TCPIPAPPS\DTOC\startup.exe
ENDLOCAL
start /min /n c:\netfin\systmdi.exe
start /min /n C:\NETFIN\NETFBASE.EXE
detach del %tmp%\* /n
detach del %temp%\* /n
detach c:\os2\apps\space32 j
-------
Enjoy. If you decide to update your stack to 32-bit, I do have a sample
firewall filter rule set and instructions that you can modify to fit
your system.
Sorry, I cannot help on the ATI video card.
--
Bill
<Okay, you win>