> I think his problem was due to using 'command.com' to ping, which is > absolutely unnecessay. I suppose he wouldn't have a problem if he just > used cmd.exe. > > BTW, while I was testing the reported problem about 'tap apps' key, I > noticed one of the bar's command is still 'command.com' in > Default.pcf. This might cause an unnecessary problem in NT-based OS's.
I did a few test, and found out that 'command.com' in WXP really slows down the response of PP, however, without any noticeable heap in CPU/Memory usage of PP. More precisely, it happens only when ntvdm.exe has its own (console) window: there have been no problems with a Win16 proggy. (BTW, the symptom reported earlier for 'tap apps' key could be related with this too) However, I think there is a work-around: when you need to run a DOS app in WXP, don't just fire 'command.com' first or a DOS app directly, always start from 'cmd.exe', I mean, trigger as follows: cmd.exe (-> command.com) -> a DOS app Maybe, the second step of 'command.com' could be skipped with a genuine DOS app, but I couldn't verify/falsify it as I don't have a genuine DOS app here. I only tested it with 'command.com', and found out no problems when I follow the step above. Sean ------------------------ Yahoo! Groups Sponsor --------------------~--> Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life. http://us.click.yahoo.com/A77XvD/vlQLAA/TtwFAA/JV_rlB/TM --------------------------------------------------------------------~-> Attention: PowerPro's Web site has moved: http://www.ppro.org Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/power-pro/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
