Recommended Posts

i'm going to re-write it in vb.net and hopefully add something else. for now, here's a workaround for server 2003:

1. open regedit

2. navigate to HKLM\Software\Microsoft\Windows NT\CurrentVersion

3. add a new string value called "CSDVersion" (case sensitive)

4. change the value of CSDVersion to "Service Pack 1"

that should let the program run on server 2003, but after you make your modifications, i highly suggest you remove this value, until SP1 for server 2003 comes out.

  • 1 month later...

A better system for making Windows Server accept your panel editor:

1. Download the Application Compatibility Toolkit from Microsoft. Its a great tool and you'll need it later anyway.

2. Install the ACT.

3. Open Compatibility Administrator.

4. Click Fix and use XPSP1VersionLie on the EXE.

5. Save your SDB file.

6. Register the SDB file.

7. Run the app, see if it works!

Edit: Unless you used the registry to obtain the value. In the future, use GetVersionEx.

The good thing about this is that it only makes a change for your app, and you don't have to go change the registry every time you use it.

In the next minor release, please change it to SP1 and higher. This can be done using GetVersionEx.

In VB.NET, use System.Enviroment.OSVersion.

This is a great program! I'm definitely going to have some fun with the OEM, and I'll be able to remove my dad's OEM label. (two different machines) Thank you!

  • 4 weeks later...
  • 4 weeks later...
  • 1 month later...
  • 2 weeks later...
  • 4 weeks later...
  • 2 weeks later...
radical!

you're a, no.. THE rad-mod, radish :o :) (radical radish)

lmao that is so funny to me. I work at a supermarket in produce and we have on the boxes Yammy Yams, Rudy Rudabagues (speling), Romeo Romain. lol Ill scan the pictures they are so ridicules

  • 5 weeks later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.