|
code
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Any known problems running VB6 application with Intel Centrino DuoWe have an application that has been in the field for over a year. I have a
customer that has a laptop with the Intel Centrino Duo processor running Win XP. The installation process completed successfully, creating all the shortcuts and required files but when he trys to run the program, nothing happens. No error messages, nothing. Any body got any ideas what may be happening here? On Tue, 21 Mar 2006 05:57:18 -0800, D Varese
<DVar***@discussions.microsoft.com> wrote: in <5E62DE60-DD9F-40C1-9B07-AD5F5AE9A***@microsoft.com> >We have an application that has been in the field for over a year. I have a NORTON anything or MCAFEE anything.>customer that has a laptop with the Intel Centrino Duo processor running Win >XP. The installation process completed successfully, creating all the >shortcuts and required files but when he trys to run the program, nothing >happens. No error messages, nothing. Any body got any ideas what may be >happening here? --- This posting is provided "AS IS" with no warranties, no guarantees, and no conferred rights. Stefan Berglund "Stefan Berglund" <sorry.no.kool***@for.me> wrote in message Yeah... it's pretty sad when the worst virus out there is called 'virus news:1dd022lgl36qirhgla1675tstrr4rcc1fj@4ax.com... >>happens. No error messages, nothing. Any body got any ideas what may be >>happening here? > > NORTON anything or MCAFEE anything. > > --- > This posting is provided "AS IS" with no warranties, no guarantees, and no > conferred rights. > > Stefan Berglund protection' eh? <g> Especially McAfee -- Ken Halter - MS-MVP-VB - Please keep all discussions in the groups.. DLL Hell problems? Try ComGuard - http://www.vbsight.com/ComGuard.htm
Show quote
Hide quote
"Stefan Berglund" <sorry.no.kool***@for.me> wrote in message Excellent point.news:1dd022lgl36qirhgla1675tstrr4rcc1fj@4ax.com... > On Tue, 21 Mar 2006 05:57:18 -0800, D Varese > <DVar***@discussions.microsoft.com> wrote: > in <5E62DE60-DD9F-40C1-9B07-AD5F5AE9A***@microsoft.com> > > >We have an application that has been in the field for over a year. I have a > >customer that has a laptop with the Intel Centrino Duo processor running Win > >XP. The installation process completed successfully, creating all the > >shortcuts and required files but when he trys to run the program, nothing > >happens. No error messages, nothing. Any body got any ideas what may be > >happening here? > > NORTON anything or MCAFEE anything. > > --- > This posting is provided "AS IS" with no warranties, no guarantees, and no conferred rights. > > Stefan Berglund I had forgotten about Norton or McAfee as I have long ago abandoned them as ever being useful on a laptop. They should be Suspect #1. -ralph "D Varese" <DVar***@discussions.microsoft.com> wrote in message Impossible to know without being there, but it is highly unlikely thenews:5E62DE60-DD9F-40C1-9B07-AD5F5AE9AA30@microsoft.com... > We have an application that has been in the field for over a year. I have a > customer that has a laptop with the Intel Centrino Duo processor running Win > XP. The installation process completed successfully, creating all the > shortcuts and required files but when he trys to run the program, nothing > happens. No error messages, nothing. Any body got any ideas what may be > happening here? "Centrino Duo" has anything to do with it. However, there are known issues with installing runtimes, MDAC, Office packages, SPs, and patches on laptops. First you have to nail down where the app is bailing during the load operation. Which isn't necessarily that easy. Have the client setup Dr. Watson or WinDbg on his system: (Doubtful it will work in this case, but always worth a try.) Win2k: http://www.microsoft.com/windows2000/en/advanced/help/default.asp?url=/windows2000/en/advanced/help/drwatson_setup.htm WinXP http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/drwatson_setup.mspx?mfr=true Inventory the components your app depends upon, and compare to what is available on the laptop. You may be getting bit by WFP (file protection), ie, everything installs fine, then Windows just ignores the setup. Anything your app installs that is 'new' (mdac, ole components, controls, etc) is suspect. Do a manual registration of all the 'new' components. ie, worry less about the the cpu and more about the OS and component environment of the laptop. hth -ralph Wouldn't an error message pop up if a component was being called for that
wasn't registered or available? Show quoteHide quote "Ralph" wrote: > > "D Varese" <DVar***@discussions.microsoft.com> wrote in message > news:5E62DE60-DD9F-40C1-9B07-AD5F5AE9AA30@microsoft.com... > > We have an application that has been in the field for over a year. I have > a > > customer that has a laptop with the Intel Centrino Duo processor running > Win > > XP. The installation process completed successfully, creating all the > > shortcuts and required files but when he trys to run the program, nothing > > happens. No error messages, nothing. Any body got any ideas what may be > > happening here? > > Impossible to know without being there, but it is highly unlikely the > "Centrino Duo" has anything to do with it. However, there are known issues > with installing runtimes, MDAC, Office packages, SPs, and patches on > laptops. > > First you have to nail down where the app is bailing during the load > operation. Which isn't necessarily that easy. > > Have the client setup Dr. Watson or WinDbg on his system: (Doubtful it will > work in this case, but always worth a try.) > Win2k: > http://www.microsoft.com/windows2000/en/advanced/help/default.asp?url=/windows2000/en/advanced/help/drwatson_setup.htm > WinXP > http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/drwatson_setup.mspx?mfr=true > > Inventory the components your app depends upon, and compare to what is > available on the laptop. You may be getting bit by WFP (file protection), > ie, everything installs fine, then Windows just ignores the setup. > > Anything your app installs that is 'new' (mdac, ole components, controls, > etc) is suspect. > > Do a manual registration of all the 'new' components. > > ie, worry less about the the cpu and more about the OS and component > environment of the laptop. > > hth > -ralph > > > > Wouldn't an error message pop up if a component was being called for that You might try running Regmon and Filemon> wasn't registered or available? > from sysinternals.com, to see what the last thing is happening before it quits. I once wrote something that "did nothing at all" on a test machine and couldn't figure it out. After running Filemon I finally figured out that the problem was that the software enumerated printer fonts at startup and if a printer was not installed it was dying without any messages. If the problem is a missing component - maybe you should see a message; I don't know about that - then it should be relatively easy to find with Filemon. You'll see a log entry where the executable ties to open a file that's not found. Then the log will end. On Wed, 22 Mar 2006 16:11:09 GMT, "mayayana"
<mayayanaX***@mindXXspring.com> wrote: > Yo - I had that one - a real Lulu>> Wouldn't an error message pop up if a component was being called for that >> wasn't registered or available? >> > You might try running Regmon and Filemon >from sysinternals.com, to see what the last thing >is happening before it quits. I once wrote something >that "did nothing at all" on a test machine >and couldn't figure it out. After running Filemon >I finally figured out that the problem was that >the software enumerated printer fonts at startup >and if a printer was not installed it was dying without >any messages. - rites of passage
Show quote
Hide quote
"D Varese" <DVar***@discussions.microsoft.com> wrote in message
http://www.microsoft.com/windows2000/en/advanced/help/default.asp?url=/windows2000/en/advanced/help/drwatson_setup.htm
news:6D987269-2DBA-4BA6-B75F-2D4AA3A97F74@microsoft.com... > Wouldn't an error message pop up if a component was being called for that > wasn't registered or available? > > "Ralph" wrote: > > > > > "D Varese" <DVar***@discussions.microsoft.com> wrote in message > > news:5E62DE60-DD9F-40C1-9B07-AD5F5AE9AA30@microsoft.com... > > > We have an application that has been in the field for over a year. I have > > a > > > customer that has a laptop with the Intel Centrino Duo processor running > > Win > > > XP. The installation process completed successfully, creating all the > > > shortcuts and required files but when he trys to run the program, nothing > > > happens. No error messages, nothing. Any body got any ideas what may be > > > happening here? > > > > Impossible to know without being there, but it is highly unlikely the > > "Centrino Duo" has anything to do with it. However, there are known issues > > with installing runtimes, MDAC, Office packages, SPs, and patches on > > laptops. > > > > First you have to nail down where the app is bailing during the load > > operation. Which isn't necessarily that easy. > > > > Have the client setup Dr. Watson or WinDbg on his system: (Doubtful it will > > work in this case, but always worth a try.) > > Win2k: > > > > WinXP
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/drwatson_setup.mspx?mfr=true
> > Show quote Hide quote > > Yes, you almost always get a 429, etc. Especially if it something the app> > Inventory the components your app depends upon, and compare to what is > > available on the laptop. You may be getting bit by WFP (file protection), > > ie, everything installs fine, then Windows just ignores the setup. > > > > Anything your app installs that is 'new' (mdac, ole components, controls, > > etc) is suspect. > > > > Do a manual registration of all the 'new' components. > > > > ie, worry less about the the cpu and more about the OS and component > > environment of the laptop. > > > > hth > > -ralph > > > > uniquely needs and is being loaded by the Windows loader. However, I have observed such situations like you mentioned. In these cases it is always something deeper in the bowels of windows. Occasionally you will find the app is actually loaded - by viewing with task manager. Which indicates that the windows loader found no fault - but the app is some bizarre state and can't be shown. The others mentioned the Virus/Spy programs - they can also cause this phenonoma. I suppose you could perhaps run some SysInternals toy. I usually attempt to run a debugger on the application and trace through everything until I find a fault. Unfortunately, I often find myself out in some common Kernal component - with little clue what all that hex is telling me. <g> When this is on a client machine you are even more limited as to what you can do. So You end up just going back to the basics. Make sure all the components are there and registered. Make sure these are the correct components for this box. What VB and VC runtimes are installed? Make sure all the permissions are there. Turn-off all Windows applications (and Virus Checkers) and re-install. Inventory the client box - what does he have you don't have? How is the profile set up? Did an Admin do something creative? Is error reporting turned off? Create a minimum program from your app, one that loads all the components, but doesn't do anything. See if it loads. If it doesn't remove stuff, until it does. Otherwise add stuff until it does fail. Ask the client if she is also experiencing unusual behavior with other apps, like Office or Outlook, etc... Borrow or steal an identical laptop and see if you can recreate the problem. yadda, yadda. Without a specific error - then it is just a bunch of guesses. It will often turn out that you will never know what the problem is. The very act of redoing installs and updates makes it go away. Unless you did some kind of unique re-compile for this customer, it is doubtful it is in your code. (However, there might be something you can change - once you identify the source) It is even more doubtful that the cpu is at fault. The layer that VB apps run at are so far removed from the cpu - that if they were failing - a ton more stuff would already be going wrong on this box. There is something on this box that is causing a problem. -ralph Had user run software and look in task manager. It is present and running
but no errors are being reported. Tried having customer disable any virus checking software, ran DrWatson. DrWatson is not reporting any errors either. Not able to get on site since customer is in Italy. Any other ideas??? Show quoteHide quote "Ralph" wrote: > > "D Varese" <DVar***@discussions.microsoft.com> wrote in message > news:6D987269-2DBA-4BA6-B75F-2D4AA3A97F74@microsoft.com... > > Wouldn't an error message pop up if a component was being called for that > > wasn't registered or available? > > > > "Ralph" wrote: > > > > > > > > "D Varese" <DVar***@discussions.microsoft.com> wrote in message > > > news:5E62DE60-DD9F-40C1-9B07-AD5F5AE9AA30@microsoft.com... > > > > We have an application that has been in the field for over a year. I > have > > > a > > > > customer that has a laptop with the Intel Centrino Duo processor > running > > > Win > > > > XP. The installation process completed successfully, creating all the > > > > shortcuts and required files but when he trys to run the program, > nothing > > > > happens. No error messages, nothing. Any body got any ideas what may > be > > > > happening here? > > > > > > Impossible to know without being there, but it is highly unlikely the > > > "Centrino Duo" has anything to do with it. However, there are known > issues > > > with installing runtimes, MDAC, Office packages, SPs, and patches on > > > laptops. > > > > > > First you have to nail down where the app is bailing during the load > > > operation. Which isn't necessarily that easy. > > > > > > Have the client setup Dr. Watson or WinDbg on his system: (Doubtful it > will > > > work in this case, but always worth a try.) > > > Win2k: > > > > http://www.microsoft.com/windows2000/en/advanced/help/default.asp?url=/windows2000/en/advanced/help/drwatson_setup.htm > > > WinXP > > > > http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/drwatson_setup.mspx?mfr=true > > > > > > Inventory the components your app depends upon, and compare to what is > > > available on the laptop. You may be getting bit by WFP (file > protection), > > > ie, everything installs fine, then Windows just ignores the setup. > > > > > > Anything your app installs that is 'new' (mdac, ole components, > controls, > > > etc) is suspect. > > > > > > Do a manual registration of all the 'new' components. > > > > > > ie, worry less about the the cpu and more about the OS and component > > > environment of the laptop. > > > > > > hth > > > -ralph > > > > > > > > > Yes, you almost always get a 429, etc. Especially if it something the app > uniquely needs and is being loaded by the Windows loader. However, I have > observed such situations like you mentioned. In these cases it is always > something deeper in the bowels of windows. > > Occasionally you will find the app is actually loaded - by viewing with task > manager. Which indicates that the windows loader found no fault - but the > app is some bizarre state and can't be shown. The others mentioned the > Virus/Spy programs - they can also cause this phenonoma. > > I suppose you could perhaps run some SysInternals toy. I usually attempt to > run a debugger on the application and trace through everything until I find > a fault. Unfortunately, I often find myself out in some common Kernal > component - with little clue what all that hex is telling me. <g> When this > is on a client machine you are even more limited as to what you can do. So > You end up just going back to the basics. > > Make sure all the components are there and registered. > Make sure these are the correct components for this box. > What VB and VC runtimes are installed? > Make sure all the permissions are there. > Turn-off all Windows applications (and Virus Checkers) and re-install. > Inventory the client box - what does he have you don't have? > How is the profile set up? > Did an Admin do something creative? > Is error reporting turned off? > Create a minimum program from your app, one that loads all the components, > but doesn't do anything. See if it loads. If it doesn't remove stuff, until > it does. Otherwise add stuff until it does fail. > Ask the client if she is also experiencing unusual behavior with other apps, > like Office or Outlook, etc... > Borrow or steal an identical laptop and see if you can recreate the problem. > yadda, yadda. > > Without a specific error - then it is just a bunch of guesses. > > It will often turn out that you will never know what the problem is. The > very act of redoing installs and updates makes it go away. > > Unless you did some kind of unique re-compile for this customer, it is > doubtful it is in your code. (However, there might be something you can > change - once you identify the source) It is even more doubtful that the cpu > is at fault. The layer that VB apps run at are so far removed from the cpu - > that if they were failing - a ton more stuff would already be going wrong on > this box. There is something on this box that is causing a problem. > > -ralph > > > "D Varese" <DVar***@discussions.microsoft.com> wrote in message <snipped>news:072D1425-2DFA-4BD8-9D29-C493A795EC19@microsoft.com... > Had user run software and look in task manager. It is present and running > but no errors are being reported. Tried having customer disable any virus > checking software, ran DrWatson. DrWatson is not reporting any errors > either. Not able to get on site since customer is in Italy. Any other > ideas??? > > > "Ralph" wrote: > .... [One of the definite downsides of the new flattening of our markets.] Sorry I don't have any other ideas except for everything I and others have already suggested. Checking for a hidden benign error only had a limited chance of being useful. Always worth a shot. You might have the client take a look at the sytem logs to see if some other component is complaining. I am only offering that, because I currently have a client running a Win2k box with Dial-up. Occasionally, opening Outlook demonstrates the identical behavior you are experiencing. Outlook runs and loads (you can see a new instance in Task Manager each time you double-click the icon) but it never becomes visible. It turned out an IPS provided "turbo accelerator" was the culprit. In all cases it complained to the System Log (basically some gibberish) but it was easy to see who fault it was. And that might help. However, the only solution was to reboot Windows. The IP vendor offered no suggestions either. But at least Outlook would work again. I see in your case it doesn't make any difference. The only other option is to google the newsgroup and look for anything that might apply in your situation. This is not a common problem, but it has happened before. What is your app doing before it 'shows'? Doing anything cute before loading a form/window? Any kind of custom controls that are pretty busy before 'show'? If your client is has any patience left - you might try and create a series of apps that slowly offer functionality and controls. Hopefully, you can create several minimum apps that do 'show' and then progress to one that fails. sorry I can't be of more help. Without being there - its all a bunch of guesses. -ralph |
|||||||||||||||||||||||
Other interesting topics