VB6 MSCOMM wroks on one PC and not another

[skimask]

Oh there's tons of idiot errors message since i own Windows (my first was 3.0), such as "this program has perform an illegal operation and will be shut down" etc etc.. huh.. who thought to code it

Do you still have a PC running anything earlier than XP?
One of the bugs that was with Windows from 95 thru ME, it finally got fixed was that stupid 'stuck menu' bug. You'd open up a folder, pull down a menu, without clicking anything, move the mouse off the open folder/menu, open up a 2nd folder, and the menu that you pulled down in the first folder would be stuck, even after you closed the original folder. And the only way to get rid of it short of a reboot, was to kill Explorer and reopen it thru Ctrl-Alt-Del.

[JD123]

Do you still have a PC running anything earlier than XP?
One of the bugs that was with Windows from 95 thru ME, it finally got fixed was that stupid 'stuck menu' bug. You'd open up a folder, pull down a menu, without clicking anything, move the mouse off the open folder/menu, open up a 2nd folder, and the menu that you pulled down in the first folder would be stuck, even after you closed the original folder. And the only way to get rid of it short of a reboot, was to kill Explorer and reopen it thru Ctrl-Alt-Del.

Funny you should mention this. I'm using a 1 month old XP computer with a clean install, nothing extra installed, no internet and only enough programs to do PIC's - it's a dedicated PIC computer. Last night I had the same hanging menu problem. I was hoping a clean computer would stop things like this.

[skimask]

Funny you should mention this. I'm using a 1 month old XP computer with a clean install, nothing extra installed, no internet and only enough programs to do PIC's - it's a dedicated PIC computer. Last night I had the same hanging menu problem. I was hoping a clean computer would stop things like this.

I haven't been able to duplicate the hanging menu thing in XP, but then again, it's XP SP2 (or is it 3 now?). I don't remember if the bug still existed in XP (raw) or SP1. Something tells me it was still there, but I'm not 100% on that.