Scourge of War Boards

No, I am not using shortcuts at all for troubleshooting. I have not used a shortcut with SOWGB since the trouble started. I am running from the exe. file and checking the version very carefully.

I run the testing with admin rights.

Just finished running memory tests... will continue to look although I am running out of things to look at.

For the sake of trying, try to run the .exe under different compatibility modes to say that you tried tem.

If you do happen to run out of options or things to try I would say bite the bullet, uninstall both versions, send in your support to have your serial deactivated on NSD's activation server, and follow the few steps I posted earlier.

Later.

Okay, I just had a thought about how to install a whole new version, and keep it isolated from the rest of the system, and it uses it's own registry. It will give you a chance to try out a fresh install without having your systems registry entries involved. I have used this software before to troubleshoot other programs, it has helped me to narrow down the problem.

Have you ever heard of a program called Sandboxie?

Download link: http://www.sandboxie.com/

I will try to show you how to do this, I just have to find my version of SOWgb to install, I know it's here somewhere.

If you have never tried using Sandboxie before, I'll try to guide you through this step by step. Just let me know if you decide to go this route...

Later.

Well that is not going to work. I just installed SOWgb in Sandboxie, it is actually breaching the confines of sandboxie, and is using the contents of my real install of sow. That is troubling because this is not suppose to happen....

So, give up on that idea, you could give it a try if all else fails.

I leave it too the Master, Norb knows more about this stuff than I will ever know.

later, and good luck.

Norb, or Team Members

This is related to the new SDK

It appears that only three files were changed in the SDK

1) demoscreens – not concerned about this one
2) gui
3) mscreens

Now, it appears that only one line was added in the gui file – which line would that be?

Also - it appears that approximately 55 lines that were added to the mscreens file.

Question – if the columns are staying the same within these files, why not just list the changes \ amendments.

This approach seems to cause a constant change within the mods, and it is also quite irritating trying to figure out what changed and why.

Why can’t you only list the changes \ additions – so that this process of constantly updating the mods are a lot better.

Explained another way – if only one line changed in the gui why not just post that one line – this is a lot better than trying to edit a hundred lines in a custom gui file.

If fifty-five lines changed in the mscreens why not just post a file that only have these changes – then we \ modders – are only looking at a simple Copy and Paste – to keep these files compatible.

davinci

Davinci wrote:

If fifty-five lines changed in the mscreens why not just post a file that only have these changes – then we \ modders – are only looking at a simple Copy and Paste – to keep these files compatible

Wouldn't that confuse the new modder? Which files would they use? What if there were 3 or 4 updates in rapid succession? Would you have a master and then partial revisions.

If you've ever done an incremental or differential backup versus a full one you'll understand what I'm talking about.

Or in Norb's case, it would be similar to version control on source code.

I say post the new file and document the changes. Or note the new additions with a comment and date within the file itself

ADukes wrote:

www.winmerge.org/

Now look what you did, D. You woke the Sleeping Dragon. :ohmy:

I actually downloaded and used that software when we were working on the Large Courier Screen issue. It works great.

http://winmerge.org/

Thanks, ADukes – very much appreciated!

Wouldn't that confuse the new modder? Which files would they use? What if there were 3 or 4 updates in rapid succession? Would you have a master and then partial revisions.

That’s my point born – I’m completely confused, one of these files has over fifteen-hundred lines of entries!

davinci

The Winmerge program is great because it because it will show you the differences within two files. It's like the grep command in Unix but intelligible to us mere mortals. :huh:

The Winmerge program is great because it because it will show you the differences within two files. It's like the grep command in Unix but intelligible to us mere mortals. :huh:

Dude! You really need to go to bed! :laugh: