CompuServe Thread

#Shell (x$, 3) Fixed

12 messages in this thread
#1227From: Don FunkOct 3, 1991 5:25 PM
Test There is 1 Reply.
#1268From: Keith Funk/Vanc.BC,CAN.Oct 3, 1991 9:09 PM
Hi Don, <<Test>>??? I've received more informative messages, but none so concise.<g> Wait, now I get it. If I receive the message, then I really am your illegitimate 4th cousin, thrice removed.<g> That must mean that Great, Great, Great Uncle Ludwig's estate has finally been settled and I get the castle in Bavaria. Well, collect your frequent flier points folks because there's going to be on helluva party at Neuschwanstein next weekend!<g> KeithF
#1283From: Ted M. YoungOct 3, 1991 11:53 PM
Keith, I really think you've got to get a hold of yourself! <g> Responding to a test message with such a diatribe means you've been spending faaar too much time trying to figure out the problem with shell. <g> Anyway, one last thing I'd like you to try. There's a program over in WINADV or WINNEW which is called WUZ or WINZIP or somesuch name. Anyway, if you could just test it out with the setup that caused problems for the VB Shell, and see if this program fails too (since it's obviously shelling to DOS to call PKZip/PKunzip). If it does, I'll be quite happy. If not, then I'm off to write a small DLL. Oh, and if you can't locate such a beast, let me know and I'll email it. – Ted There is 1 Reply.
#1293From: Keith Funk/Vanc.BC,CAN.Oct 4, 1991 12:51 AM
Hi Ted, <<I really think you've got to get a hold of yourself.>> No way!! My Mom told me that it would make me go blind!! I already wear glasses.<g> Do you think that trying WIN.ZIP would be a good test? I just read about this Win3 FrontEnd program for zipping files in a recent issue of PC Magazine. I reckon it's highly unlikely that it's written in VB. I'm pretty sure that it's a problem with VB rather than Win3. But I doubt if we will ever know for sure since the problem so far has only appeared on two computers. BTW, what's a diatribe? Sounds like a bunch of people gathered together to try and loose weight.<g> KeithF There are 2 Replies.
#1312From: Mark Novisoff/MicroHelpOct 4, 1991 5:31 AM
Keith, >My Mom told me that it would make me go blind!! Hey, c'mon, Susan is lurking…. 😉 Mark There are 2 Replies.
#1376From: Keith PleasOct 4, 1991 1:20 PM
Mark: …and Pee Wee Herman.
#1412From: Keith Funk/Vanc.BC,CAN.Oct 4, 1991 4:16 PM
Hi Mark, Sorry about that. I didn't think these days that anyone would take that old line as being offensive. I'll be more careful in future. KeithF There is 1 Reply.
#1421From: Mark Novisoff/MicroHelpOct 4, 1991 4:43 PM
Keith, I was only teasing! Didn't I put a <g> in it? Mark
#1369From: Ted M. YoungOct 4, 1991 12:45 PM
Keith, Yeah, Win.Zip would be a good test. Basically (ok, pun intended!), anything that's non-VB and does a DOS shell would be a good test. >> No way!! My Mom told me that it would make me go blind!! I already >> wear glasses.<g> Hey now, let's not get carried away, we've got mixed company in these parts (or at least I sure hope so! Hey Susan, you still around??). <g> – Ted There are 2 Replies.
#1409From: Keith Funk/Vanc.BC,CAN.Oct 4, 1991 4:16 PM
Hi Ted, WINZIP works in both Standard and Enhanced modes on my computer. KeithF
#1519From: Keith Funk/Vanc.BC,CAN.Oct 5, 1991 12:56 PM
Hi Ted, YOU HAVE FOUND THE PERFECT WORK AROUND FOR THE SHELL PROBLEM!!!!!!!!!! Not only does it cure the UAE's I've been getting, but it's good program practice as well. The trick is to *disable* the command button while the shell is executing. It works, but god only knows why. Hey, at this point who cares why.<g> I would never have found this solution where it not for the fact that you took the time to upload your test program, which I just downloaded this morning. I think you've done us all a great service. THANKS. At last we can all move onto other things. KeithF There is 1 Reply.
#1523From: Ted M. YoungOct 5, 1991 1:17 PM
Keith, You're kidding. Disabling the command button cures the problem? I guess this is one of those good news/bad news things because while it cures the problem on your machine, it doesn't tell me WHY it cures it. I care why because it means that something's going on that I don't know about and it doesn't give me the warm fuzzies to distribute a program that works for an unknown reason. The good news is that this may help MS track down the problem, though this certainly sounds like a very, very difficult problem to track down. Maybe MS will send some techies up to your machine to find the problem!<semi-grin> Anyway, when you send a problem report to MS, make sure you tell 'em the BIOS version, etc. Although I guess the MSDiag report will give 'em all they need. Again, many thanks for taking the time to do some bug hunting! – Ted