6.0 Install -- WDSCI-L

Glutton for punishment that I am I installed 6.0 today. Not thismorning, not this afternoon, today. I.e., it took awhile. But that wasto be expected. I just have a CD drive at work so I couldn't use thequick DVD.

Also, I did take the time to read the Installation and Migration stuff.Originally I thought I would uninstall 5.1.2, but decided to run inparallel for awhile.

The install went pretty smooth. I did download the latest updates.Seemed about as big as the original CD's. We're on a T1 so don't trythis on a dial-up.

As the migration manual suggested, I saved my original workspace. When6.0 started, I pointed it to the original 5.1.2 workspace. Don't knowif it was that or something else, but I got an error (sorry, forgot towrite it down). 6.0 came up anyway. The second time I started 6.0, noerror (same workspace).

Downloaded the Softlanding plug-ins. Went smoothly. Odd thing (andit's probably just me), but in the "Spooled Files" if I right click andselect the 'View' option a box pops up with what I'm guessing would bewhere the report would display, but zilch. However, if I double-clickon it, the spool file comes up in a Text Editor box. I'll have to diginto these a bit more.


I didn't install HATS and most of the other stuff, but -

I did try to install CODE. Got an error message: "A previous version ofWDSc exists on the system. Please click cancel and uninstall theexisting product." Maybe the migration or installation manuals saidsomething about this, but I missed it if it did. No biggie as I justuse it for designing reports.

Tried to install the DB2/UDB Express Edition. Nothing. When theinstaller didn't kick in, I tried using "My Computer" but it said toinsert a disk into drive D: (Yes, the CD was in drive D:).

I don't use WDSc for web stuff, webfacing, etc. Mostly just RSE. I didpull up a couple of programs and do some stuff. Only a cursory test,you understand, but all of the tools I'm used to worked without ahitch. It still takes forever to load (1 gb memory at 2.6 ghz), but noworse, it seems, than 5.1.2. And, except for the original error, whichhasn't re-occurred, (see above) no problems yet.