CompuServe Messages

#TAD modules

    16-Jun-90 22:00:46
Sb: #17351-#TAD modules
Fm: David Kieltyka 73200,3553
To: ASDG 76004,1765
Perry, Many thanks for replacing the GIF loader. Man, that thing is fast! It used to take about 20 minutes converting GIF images to IFF using GIFtoTMP and TMPtoRGB. Your GIF loader does the job in under a minute. It also handles interlaced GIF images properly, which TMPtoRGB does not. I didn't bother with the installation program, as I knew which files I needed and where they needed to go. But let me check. Hmmm…it doesn't work from Workbench…opens up a WShell console window, reports "Unknown Command Execute," and then aborts. But it does work from WShell itself. That's odd…. Well, I've been messing around a bit and I've found the culprit. It's the SetExecute program provided with WShell. SetExecute patches Execute(), I think, to look for RunWSH rather than Run. Apparently this causes a problem with scriptfiles using dot commands, like your Install, when they're invoked from Workbench. I've removed SetExecute from my startup-sequence; I now recall having a similar problem with ProPage 1.31's installation script and never figuring out what the problem was. Perhaps that other person you mention also uses SetExecute. I've heard that ARP Execute has problems with certain scriptfiles as well. BTW, I ran DiskChk (comes with CrossDOS) on that GIF loader disk last night. It reports that blocks 71-417 are bad. I just pitched the disk. 8^) Also BTW, thanks for the correction regarding ScanLab/100. -Dave