We have GlobalModule.exe developed using VB .NET. It works good in windows XP and windows7. But in windows8 we often get the error 'Global module has stopped working' .can any one please suggest me any reason behind it.it again works well when we close and reopen it...thank you
Try changing compatibility mode and run it as administrator
Related
Bear with me please, since I don't know that much about Windows – I'm trying to set up UWF (Unified Writing Filter) here on my mac through a Parallels installation of Windows 10. I found out how to enable UWF through the Control Pane, which I did. I then restarted the Virtual Machine. When I then tried to configure it through the powershell or command prompt (both run in admin mode), I got no response whatsoever. The uwfmgr.exe is there under c:\windows\system32, but like I said, it doesn't do anything when I run it. No response – but also, no error.
Can anyone help me with this?
I had the same issue and solved it by downloading the latest ISO for 10 Enterprise.
It seems you need a Windows 10 Enterprise edition for this to work. Just re-activating windows with an Enterprise key makes uwfmgr.exe print stuff again. Just testing, whether it works as well.
This was tested on Windows 10, V1809.
I just recently upgraded to Windows 10 and ever since I have upgraded I can't get into VB6. I keep getting the System Registry error. I have googled and tried about everything and nothing seems to work. Running VB6 as Administrator is not an option, don't ask but we can't have admin to our computers we have to be logged in as users. The way we use to fix it was to trick Windows 7 log on as Admin run VB6 as Admin then switch me back to user and it worked, but this no longer works. Does anyone have any suggestions that currently have VB6 working as a user and not admin? I really don't want to resort to have to run it out of my virtual machine :( Thanks in advance!
Amanda,
I know it is 3 years later and I wonder what you did. and my solution may be late.
I moved VB6 Enterprise to a Windows10 machine, I did not upgrade the machine to Win10 with the IDE. However to make it work for some of my clients with Win10 machines I:
Back up all the VB6 files, folder and directories.
Using control panel in Win10, uninstall VB6 app. That's right, uninstall!
Using the original install disk, running it as an Administrator, install the program.
If the program has been updated to a later version, you need to get a copy of the latest version and copy over the one that was installed.
Or, Sweet Talk your IT guy into making you a new install disk with the latest version you are supposed to be running.
Go to the folder where the exe file is installed, Right Click on it and open the Properties, and go to the Compatibility tab.
Choose run as an administrator, and also click the Run this program in compatibility mode for Windows XP Service Pack3, or if it shows Latest version of Windows XP try that. You may need to check with your IT department.
Warning: if the VB6 program uses any non-Microsoft tools you may need to register them by hand.
I suspect this has already been worked out for you, but I put it here for anyone that may stumble across it, needing it.
I am trying to get my application to start at startup. So far i have tested it on windows xp and windows 7 and it works like a charm. But in windows 8.1 the shortcut is in the startup directory C:\Users\Administrator\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup but it does not start.
If i check with the task manager under the start up tab the application is there and is enabled. But it just doesn't start on start up.
Can anybody please assist?
Update 1:
I have found the problem. I marked the application to run as administrator. When i removed that privileges the application started at start up. Why would this interfere? i ran it as administrator in windows 7. and since have tested it on windows 8 and also had to set it to run as administrator, even then it worked. Only in 8.1 did it cause the software not to start up.
Does anybody know why?
UPDATE 2:
OK to be clearer on the above mentioned update. and comments.
The program works fine. Nothing is wrong with it.
When it is checked to run as administrator it does not auto start. When the admin rights are removed. It does auto start.
I have done a simple test to see if the software even launches and it does not so logging wont help. I set a message to appear if the application launches so before anything is processed i get notified. Before there can be any errors in code it will tell me.
SO the problem is not the coding in the program. The problem clearly is windows 8.1 which does not let my application auto launch on start up when it has admin rights.
It transpires that the issue is that you wish the program to run elevated which results in a UAC dialog being shown. Windows blocks autostart programs that requested elevation. You report a difference between Windows 7 and Windows 8 but I suspect that the real difference is your UAC settings on the two machines.
This is discussed in more detail in these links:
https://superuser.com/questions/536990/run-as-administrator-prevents-applications-from-autostart
http://botsikas.blogspot.co.uk/2010/05/autostart-application-that-requires-uac.html
http://www.sevenforums.com/installation-setup/182612-getting-programs-run-startup-uac.html
http://www.techrepublic.com/blog/windows-and-office/make-vista-launch-uac-restricted-programs-at-startup-with-task-scheduler/
In all cases, the recommendation is to use the task scheduler to cache admin credentials and so avoid facing the UAC dialog.
I have made an application in visual studio 2010 on a windows xp computer. When I compile the release version and run it on a windows xp computer, it runs fine.
When I on the other hand try to run it on windows 7 I get the "This program has stopped working" error message. Running the application in compatibility mode doesn't change anything. Can someone tell me what I can try to do?
Thanks.
With the information you provide, it might be a windows 7 vs xp problem or that you don't find any resource that you are looking for. If I were you I would:
Get sure that app was compiled by any cpu
Check windows error log to see if there is any message
Run app as administrator
Use error handling (try/catch) to see exceptions by showing them in UI or logging to a text file.
EDITED: TRY-CATCH example
Try
//CODE
Catch ex As Exception
Dim writer As New StreamWriter("C:\MyLog.log", True, System.Text.Encoding.ASCII)
writer.WriteLine(ex.Message)
writer.Close()
End Try
I ran across this issue also. As my solution was completely different, I thought I would share just in case someone else found it relevant.
My problem was that in my project references I had two references to Adobe Acrobat DLL files. I was getting the error on my new client machine because it didn't have Adobe Reader installed (which installs the DLL's that my project references). Once I installed Adobe Reader, my program installed properly.
The interesting part of debugging this is that no TRY/CATCH block would have caught it. Apparently the check for reference happens before the code is run. You literally just get the generic message "ProgramName has stopped working".
Just FYI...
I am trying to run an old Clipper application. It runs fine on Win 7 32bit but when I try using the DOSBox 0.74 it crashes with the following error:
Exit to error: CPU_SetSegGeneral: Stack segment zero
Are there some settings I forget to set when running the DOSBox?
I need to be able to run this app in DOSBox as it appears to be only portable solution that would work on any Win 7, being it 32 or 64bit.
If no apparent solution is known for this problem maybe you can tell me what alternatives I have to run a Clipper 5.3 application on a Win 7 64-bit Home edition?
EDIT:
I tried it on Win 7 Home 64 bit with the very same result. What can I do?
I used clipper many years ago, clipper does cause problems because incorrect config.sys configuration, specially the setting "FILES" must be big enough (let´s say 200) for your application, but "original" dosbox does not provide a way to adjust this setting.
Try the patch from http://www.shdon.com/blog/2009/09/05/adjustable-files-setting-in-dosbox
This patch allows to configure FILES adding a new setting on dosbox options file
Steps:
Backup dosbox.exe and replace it with the patched version
Edit the dosbox options file and add FILES=200 to the [DOS] section
Try it and post the results since i don't have clipper 5.3 to test.
Wanting to close this question I will write what was the only solution thanks to which I was able to run that aged application on Win7 64bit.
It was VMLite XP Mode.
I simply followed the steps described in their how to guide and it was up and running then I copied my application into the VMLite XP Mode, and it was running fine.
Finally I created, after some googling, a shortcut to my desktop and now I can easily start the application from my Win7 64bit desktop which then lunches the VMLite XP Mode which starts the application :) or something along this lines anyway, so far, it works great.