Downloaded current version and despite installing it to the U3 stick, local drive and also trying to Run from Temp Dir (so all the options) I receive a Windows error
Application Error:
The application failed to initialize properley (0xc0000135). Click OK to terminate the application.
Windows XP Pro Version 2002 SP2
Any ideas?
Many Thanks,
Nigel
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Do you have the .NET framework installed?
The Shortcut Creator requires the .NET framework.
The most common cause for errors is not having it installed.
-----------------------------------------------------------------------------------------------
Because they stand on a wall and say nothing is going to hurt you tonight. Not on my watch.
"Because they stand on a wall and say, 'Nothing is going to hurt you tonight. Not on my watch.'" (A Few Good Men)
Coincidence is God's way of remaining anonymous.(Albert Einstein)
Aha, the lack of .net was the issue. Works fine now.
I was assuming nothing was required as it was a U3 app but to be fair it is an app to support other apps on U3 and maybe is not required to be fully self contained
Thanks again and it does exactly what it says on the tin.
Nigel
I figured that since U3 only works on 2000 and up.
And 2000 and up should have .NET if they are up to date on patches that using .NET would work. Most people don't run into the problem.
I did start working on a VB6 version but it still has bugs, didn't have the time to update it.
Possibly after June I will have time to start on the VB6 version again.
-----------------------------------------------------------------------------------------------
Because they stand on a wall and say nothing is going to hurt you tonight. Not on my watch.
"Because they stand on a wall and say, 'Nothing is going to hurt you tonight. Not on my watch.'" (A Few Good Men)
Coincidence is God's way of remaining anonymous.(Albert Einstein)
Most computers don't have .NET installed. It shows up as an optional update in Windows Update, which most people *NEVER* install.
Most people only actually install .NET when they encounter an app that requires it. And most apps don't require .NET.
Sometimes, the impossible can become possible, if you're awesome!
John's right. It's optional.
_____________________________
I felt so different without a signature.
I guess I was mistaken. I thought it was listed in the recommended updates. The ones that get pushed if you have automatic updates turned on.
-----------------------------------------------------------------------------------------------
Because they stand on a wall and say nothing is going to hurt you tonight. Not on my watch.
"Because they stand on a wall and say, 'Nothing is going to hurt you tonight. Not on my watch.'" (A Few Good Men)
Coincidence is God's way of remaining anonymous.(Albert Einstein)
Within Microsoft Update (and Windows Update), there are 3 different levels of updates:
- High Priority
- Software (Optional)
- Hardware (Optional)
On my main development PC, .NET is sitting uninstalled right under Software (Optional)... where it's gonna stay. Windows 2000 does not include any version of .NET (1.1 and 2.0 show up under Software (Optional)). Windows XP may include 1.1 within Service Pack 2 (but I'm not sure about that). Windows Vista includes .NET 3.0, which unlike other versions is backwards compatible to 2.0, but does not include .NET 1.1.
In short, distributing a .NET app is like distributing a Java app. You need to assume that the PC does *NOT* have .NET (or at least the proper version) and link to it from your webpage (if distributed online) or package the installer (if doing physical distribution). Unless you're dealing with Vista *ONLY* which is the only Windows OS that will always have a specific version of .NET installed on it.
Sometimes, the impossible can become possible, if you're awesome!
I think its having Servicepack 2 that causes it to move to the high priority update list. Although not 100% sure on this.
Going to install SP2 in a VM this week just to see.
But I will also update the page for the creator to make it more clear that it needs .NET and provide a link to the installer.
Hopefully after June I can finish the VB6 version.
Thanks for taking the time to provide the information/explanation.
-----------------------------------------------------------------------------------------------
Because they stand on a wall and say nothing is going to hurt you tonight. Not on my watch.
"Because they stand on a wall and say, 'Nothing is going to hurt you tonight. Not on my watch.'" (A Few Good Men)
Coincidence is God's way of remaining anonymous.(Albert Einstein)
Only having it actually installed causes patches to it to show up in the high security list (there have been several security issues with .NET). So, having 1.1 installed causes the 1.1 SP to show up as a high priority update. Otherwise, it just sits in the Software (Optional) category.
Sometimes, the impossible can become possible, if you're awesome!
Good to know, thanks for the info.
-----------------------------------------------------------------------------------------------
Because they stand on a wall and say nothing is going to hurt you tonight. Not on my watch.
"Because they stand on a wall and say, 'Nothing is going to hurt you tonight. Not on my watch.'" (A Few Good Men)
Coincidence is God's way of remaining anonymous.(Albert Einstein)