I have read on a few newsgroups that fix pack 17 can cause problems, and one explicitly mentioned that ISDEL task. The suggestion made was to scrap that fix pack, I think 10 was recommended and 17 not.

Don

In <4mrsp4$i2b@news.duke.edu>, gronke@acpub.duke.edu (Paul Gronke) writes: >Has anyone installed SAS 6.11 on OS/2? The installation program >crashes whenever I try to change the default directory. After I >change the directory on the opening screen, the program closes down >and I have a rogue process, ISDEL, listed on my process list. I have >to kill this manually. > >If I choose CUSTOM install and try again to select a different target >directory, the same thing happens. > >The program apparently will install in TYPICAL, but I don't have 293 >megabytes of space on my D: drive (nor do I want to dump 293 megs of >SAS onto my box!). > >The only way I can install is to run CUSTOM/CLIENT as if I was always >going to run SAS off of the CD-Rom. Unfortunately, since this is a >site licensed copy, I have to give the disk back. > >Any help, experiences with installing SAS 6.11 on OS/2 appreciated. > >Current setup: > >Micron P-90 (micronics MB), 16 meg RAM, SCSI hard drive (1.2 gig, >BusLogic controller), running OS/2 Warp (not connect) with fix pak 17 >installed. SAS 6.10 already running. > >-- >gronke@acpub.duke.edu >Paul Gronke

============================================================================== =

Don Stanley DSTANLE@IBM.NET Information Power Limited SAS Institute Quality Partners Wellington NEW ZEALAND

Author : Beyond The Obvious With SAS Screen Control Language Currently Writing : Effective Use Of The Frame Entry In SAS Software (Working title)

another chapter bites the dust ...