Running on a Windows machine?

More
3 years 6 months ago #6996 by Parnassus
Replied by Parnassus on topic Running on a Windows machine?
It's not a problem with protocol.c? Why aren't the errors showing up in other files?
Severity	Code	Description	Project	File	Line	Suppression State
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	376	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	379	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	381	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	387	
Error	C2065	'SE': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	387	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	482	
Error	C2065	'SB': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	486	
Error	C2065	'DO': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	491	
Error	C2065	'DONT': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	492	
Error	C2065	'WILL': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	493	
Error	C2065	'WONT': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	494	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	499	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	500	
Error	C2051	case expression not constant	TBA3.68	...\tbamud-3.68\src\protocol.c	486	
Error	C2051	case expression not constant	TBA3.68	...\tbamud-3.68\src\protocol.c	491	
Error	C2051	case expression not constant	TBA3.68	...\tbamud-3.68\src\protocol.c	492	
Error	C2051	case expression not constant	TBA3.68	...\tbamud-3.68\src\protocol.c	493	
Error	C2051	case expression not constant	TBA3.68	...\tbamud-3.68\src\protocol.c	494	
Error	C2051	case expression not constant	TBA3.68	...\tbamud-3.68\src\protocol.c	499	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	870	
Error	C2065	'DO': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	870	
Error	C2065	'TELOPT_TTYPE': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	870	
Error	C2099	initializer is not a constant	TBA3.68	...\tbamud-3.68\src\protocol.c	870	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1000	
Error	C2065	'WILL': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1000	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1005	
Error	C2065	'DO': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1005	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1081	
Error	C2065	'SB': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1081	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1083	
Error	C2065	'SE': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1083	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1088	
Error	C2065	'SB': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1088	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1090	
Error	C2065	'SE': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1090	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1098	
Error	C2065	'SB': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1098	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1100	
Error	C2065	'SE': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1100	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1105	
Error	C2065	'SB': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1105	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1107	
Error	C2065	'SE': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1107	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1149	
Error	C2065	'SB': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1149	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1150	
Error	C2065	'SE': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1150	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1155	
Error	C2065	'SB': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1155	
Error	C2065	'SE': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1155	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1197	
Error	C2065	'SB': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1197	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1198	
Error	C2065	'SE': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1198	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1210	
Error	C2065	'SB': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1210	
Error	C2065	'SE': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1210	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1490	
Error	C2065	'SB': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1490	
Error	C2065	'TELOPT_TTYPE': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1490	
Error	C2065	'SE': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1490	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1491	
Error	C2065	'DO': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1491	
Error	C2065	'TELOPT_NAWS': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1491	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1492	
Error	C2065	'DO': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1492	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1493	
Error	C2065	'WILL': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1493	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1494	
Error	C2065	'WILL': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1494	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1495	
Error	C2065	'DO': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1495	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1496	
Error	C2065	'WILL': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1496	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1497	
Error	C2065	'DO': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1497	
Error	C2065	'TELOPT_TTYPE': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1538	
Error	C2065	'WILL': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1539	
Error	C2065	'WONT': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1549	
Error	C2065	'TELOPT_NAWS': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1566	
Error	C2065	'WILL': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1567	
Error	C2065	'WONT': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1569	
Error	C2065	'WILL': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1576	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1578	
Error	C2065	'SB': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1578	
Error	C2065	'SE': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1578	
Error	C2065	'WONT': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1582	
Error	C2065	'DO': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1589	
Error	C2065	'DONT': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1596	
Error	C2065	'DO': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1603	
Error	C2065	'DONT': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1605	
Error	C2065	'DO': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1612	
Error	C2065	'DONT': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1617	
Error	C2065	'DO': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1627	
Error	C2065	'DONT': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1629	
Error	C2065	'WILL': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1636	
Error	C2065	'DO': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1636	
Error	C2065	'IAC': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1639	
Error	C2065	'SB': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1639	
Error	C2065	'SE': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1639	
Error	C2065	'WONT': undeclared identifier	TBA3.68	...\tbamud-3.68\src\protocol.c	1647	
Error	C1003	error count exceeds 100; stopping compilation	TBA3.68	...\tbamud-3.68\src\protocol.c	1647	
Severity	Code	Description	Project	File	Line	Suppression State
Warning	C4018	'<=': signed/unsigned mismatch	TBA3.68	...\tbamud-3.68\src\protocol.c	1391	
Warning	C4013	'alloca' undefined; assuming extern returning int	TBA3.68	...\tbamud-3.68\src\protocol.c	1394	
Warning	C4047	'initializing': 'char *' differs in levels of indirection from 'int'	TBA3.68	...\tbamud-3.68\src\protocol.c	1394
(I threw in 3/9 warnings, just for fun)

Please Log in or Create an account to join the conversation.

More
3 years 5 months ago #7185 by Krell
Replied by Krell on topic Running on a Windows machine?
Wow Parna,

I'm sorry to hear that you were having so much trouble. Hopefully you got your new computer up with tba running.

Please Log in or Create an account to join the conversation.

More
3 years 4 months ago #7271 by Parnassus
Replied by Parnassus on topic Running on a Windows machine?
Sorry for the late response. I've been lazy lately! Well, Fade gave really good instructions as well as a TBA zip. This zip was for version 3.57. I then realized that the most recent version 3.68. When I tried that, I couldn't get it to work. Since Thomas felt it would be better to run under Cygwin, I kept to the 3.57. My cygwin version seems to want me to reinstall Cygwin but I don't want to do that on a borrowed computer. My MSVC version works off my removable hard-drive so I'm happier with that. I'm hoping that it will continue working when I plug it into another computer.

I'd hoped I'd have my new computer by now but that didn't work out as planned and now it looks as if I'll wait for spring to get it. This borrowed laptop and my removable h-d are working fine. If I were doing more with my TBA, I'd work harder to get the current copy working but it's not worth the time at this point.

Thanks for worrying about me, Krell :)

Please Log in or Create an account to join the conversation.

  • Sascha
  • Sascha's Avatar Topic Author
  • Offline
  • Elite Member
  • Elite Member
More
3 years 4 months ago #7274 by Sascha
Replied by Sascha on topic Running on a Windows machine?
Sounds like you have your hands full! I know that we're all looking forward to you replacing your machine and jumping back in. You always have such solid answers and creative ideas.

Will you stand against the coming Storm? After the Breaking: STORMRIDERS MUD - atbmud.dune.net port 4000

Please Log in or Create an account to join the conversation.

More
3 years 4 months ago #7287 by Parnassus
Replied by Parnassus on topic Running on a Windows machine?
I appreciate your kind words, Sasha. But even when my computer is working, I find I run through cycles when I'm helpful and when I'm not. There are a few things going on now that just make it a bit harder. I'm expecting to get past this around spring and by 2019, I'm expecting to have even more free time. In fact, thinking about 2019 is probably slowing me down a bit :)

I hope everyone is having a nice season and looking forward to the new year!

Please Log in or Create an account to join the conversation.

More
2 years 10 months ago #8136 by Parnassus
Replied by Parnassus on topic Running on a Windows machine?

Unfortunately something is still not right after one does this - the mud has a bug with these settings causing it to crash after a couple of minutes. I have still not been able to pin it down - apparently somewhere we're either clobbering memory or freeing something we're not supposed to. This doesn't happen on linux or when compiled in cygwin, so it might be some library included by visual studio that's causing it.

So, I recommend that instead of going through all that trouble, you run tbamud under cygwin.


Okay, here I am, half a year later, thinking I should dust off that 3.57 and play with it a bit in hopes that it would encourage me to do a bit of work on my zones. However, it was before any of my zones went in so I decided to add my zones in manually.

That's when I found that the nice download zones section is gone now. So...in my simple-minded way, I grabbed the lib\world section of the 3.66 and swapped it out. I expected to get bugs but figured it would sort of maybe work in a general sort of way, right? I was sort of surprised to see that older zones (I expected that all the bugs would be in the newer zones because of new code that would be missing) suddenly had a bunch of mobs that were flagged NOT DEAD YET! Anyway, the mud started up and off we went! ...until it crashed... But still, not unexpected, right? So I started looking around for information about start-ups and DGB and crashes and anything that would help me figure out what was conflicting.

I read Thomas' post a few times when it struck me that the situation sounded very familiar. I swapped back the old lib\world and there were no crashes. "AHA!" I told myself. "Maybe it's not the code, maybe it's the zones!"

Therefore, I went back to Visual Studio and compiled 3.66. Sure enough, there were the mysterious crashes. I swapped out the world file for the earlier one and...WOW, no crashes. That was good enough for me! I compared the zone files of the 3.57 and the 3.66 and...um...oh, *expletive deleted*, all the changes I could see on a fast comparison were ones I'd put together! 211 wasn't in the old one but it was in the new one. Hmm, my Tarot zone. 355 and 356? Those were the Ultima that I did as an experiment because someone had asked if it were possible to port it from a ROM based base. 653 and 654? Those were my player housing zones.

I manually entered them into the old lib. First Tarot, then housing, then Ultima, restarting each time and waiting for the crash. It's now been 2 hours and the 3.66 is still running.

I still believe that it isn't Visual Studio and it isn't anything about the codebase. I don't know why it doesn't show up in linux or Cygwin but switching the world file makes 3.66 run with Visual Studio without crashes.

Next step: THE WORLD! *maniacal laugh* Or at least a trial of TBA 2018.

Please Log in or Create an account to join the conversation.

More
2 years 9 months ago #8137 by WhiskyTest
Replied by WhiskyTest on topic Running on a Windows machine?
Glad you're up and running again!
I suppose the moral of the story is ¯\_(ツ)_/¯

Please Log in or Create an account to join the conversation.

More
2 years 9 months ago #8138 by Parnassus
Replied by Parnassus on topic Running on a Windows machine?
WhiskyTest, I like your moral and totally agree with it.

Using the same 3.66 changes for Window along with the tbamud-2018.1, I made the same changes in Visual Studio. This gave me one error which I forgot to record but which went something like this:
error C2065: 'HUH': undeclared identifier

Since I couldn't find a way to fix it, I cheated and commented out the line in db.c so it looks like this:
3786 /*CONFIG_HUH = strdup(HUH);*/

This gives me a working tba2018 with 11 warnings and, when using a nonsensical command, an output like this:
> alphabet me
(null)

When I ran it with the current zones, it crashed every few minutes. I swapped out my amended world files (3.57 + Tarot, Ultima and housing) and it's been running for hours. I compared some of the file sizes and found that Whiteknight has added two zones (343 and 346 are extensions to God Complex) and changed one (274 changed Smurfs to St. Brigid) but since these were not in my crash_world files of 3.66 I didn't bother to swap them out to test them.

I'm much happier with a more up-to-date mud to play with and I can live with the (null) thing, especially since I know what it is, but I'd be even happier if someone could fix it for me :)

Please Log in or Create an account to join the conversation.

More
2 years 9 months ago #8139 by Parnassus
Replied by Parnassus on topic Running on a Windows machine?
Re: crashes

I've found that the mud will run using all the current world files except 0.obj. If I replace that one file with a copy from 3.57 all the crashes stop. I've looked at the files and done an eyeball comparison. The crash file is missing #45, a pile of gold coins.
Warning: Spoiler!

I thought that must be it and added it in manually but the crashes continued. I also found differences in #71, a Chinese finger trap and #0, a bug, was missing. After I copied in the changes, the mud still crashed. The only way I could stop the crashes was to replace the file.

This is a bit of a disappointment to me since this file has a bunch of quoted text. The problem with quoted text is that when you /fi, two spaces appear before the end quote marks. "I am the dragonbane." turns into "I am the dragonbane. "

These are all fixed in the current file but not in the old file. However, that's a small price to pay for a non-crashing mud. What I don't understand is why it only crashes under Visual Studio and not Linux or Cygwin.

Please Log in or Create an account to join the conversation.

More
2 years 9 months ago #8140 by WhiskyTest
Replied by WhiskyTest on topic Running on a Windows machine?
maybe there is some invisible formatting in 0.obj?

Try making a new empty txt file in notepad, copy the contents of 0.obj that is suspect into it, save and rename to 0.obj

Please Log in or Create an account to join the conversation.

More
2 years 9 months ago #8141 by Parnassus
Replied by Parnassus on topic Running on a Windows machine?
Thanks for the suggestion. Even though it didn't work, I was sitting here looking at the two files and I realized that I could do the same thing as I had with the zone files; swap them out bit by bit until I found what crashed and what didn't. Of course, with the zone files I started at the big numbers since I felt that the error was more likely to be in a newer zone than in the old tried-and-true. And after checking a bunch of zones, where was it? Zone 0! So I wasn't going to be tricked like that again, right? So I started at the beginning and where was the problem? #90 *sniff*
#90
ice cream 99 flake~
an ice cream~
An ice cream has been dropped here.~
~
19 0 0 0 0 ao 0 0 0 0 0 0 0
1 0 0 0
1 4 0 0 1
T 82
E
ice cream 99 flake~
   Known as the 99, it is an ice cream cornet with a stick of chocolate rammed
in. First sold in 1922 at the ice cream shop at 99 the High Street, Portobello,
Scotland.
~

Personally, I felt that the problem was going to be in that big long line that starts with 19 but after messing with it a while, it turned out to be this one: 1 4 0 0 1. The working copy was: 1 4 0 0. I thought this was odd because I figured that a missing number would be MORE likely to cause a crash. When stating the object, the values were:
Weight: 1, Value: 4, Cost/day: 0, Timer: 0, Min level: 0
This looked like the problem was in the min level but, oddly, stat shows:
Weight, Value, Cost/day, Timer, Min level
while the file shows
Weight, Value, Cost/day, Min level, Timer
which is kinda confusing.

But, yes, the problem is in the Timer. Timer is used in conjunction with a timer trigger to make something happen to the object at a certain time. In this case, the ice cream will melt in 1 minute. This probably has a bit of a random factor. When I changed the timer to 2 minutes, the mud crashed at 2 minutes and about 10 seconds. With no changes, the mud would crash in a range of almost immediately to maybe 2 minutes or so, although I never actually timed it, basically maybe 2 to 10 commands. This explains also why it never crashed on an empty mud, because the tics don't start until someone is logged in.

I still don't understand why this is only VS and not Cygwin or Linux but I'm surprised there isn't more of a problem. This ice cream is sold by the waitress in room 99. The mud starts, the waitress loads, the ice cream loads, the timer starts ticking and one minute later...BOOM! What happens in a normal mud? Why doesn't the ice cream melt in the waitress' hands? How does she manage to keep it in stock?

This seems to be the only timer that loads automatically so if you change the 1 to a 0 (or oddly even remove it) the crashes stop. You lose the benefit of the timer lesson but that's a good thing in this situation. Another timer is in my own Tarot zone where the receptionist uses it to time her conversation with a customer so that no player can go in, start talking to her and go afk, blocking anyone else from talking to her. Without that block that makes her concentrate on one player, you could talk to her and someone else could grab control and take your spot. However, in the VS version, if someone is blocking, the mud will crash. Corpses are on timers but they don't cause crashes. But just to make me boggle, Detta has a timer in object 11862, trigger 11897, that works without crashing the mud. See? I always knew she was a much better builder than I am!

So I now have an up-to-date working TBA with no HUH?, a confused receptionist, a non-melting ice cream cone and a time-bomb potential for unrealized timer progs. I still think I'm ahead :)

Please Log in or Create an account to join the conversation.

More
2 years 9 months ago #8154 by thomas
Replied by thomas on topic Running on a Windows machine?
I'm impressed by your tenacity. Very well done.

Please Log in or Create an account to join the conversation.

More
2 years 9 months ago #8157 by Parnassus
Replied by Parnassus on topic Running on a Windows machine?
I know, right? I'm really impressed with myself! I've worked out the crashes by adding waits into the dangerous triggers although that waitress in room 99 can no longer hold onto ice cream cones. Actually though, that makes sense to me. What I don't understand is how she usually holds onto something that destroys itself with a timer trigger.

Now if someone could just figure out the HUH?! thing for me, I'd be golden! :)

Please Log in or Create an account to join the conversation.

More
2 years 9 months ago #8165 by Parnassus
Replied by Parnassus on topic Running on a Windows machine?
Okay, this is a bit odd. I had some trouble with a snippet and had to roll it back. I forgot about the Huh error:
error C2065: 'HUH': undeclared identifier
and forgot to comment it out. I didn't even realize that it didn't error until I tried out the mud and got the Huh!?! in the proper places!

Anyway, for anybody who starts reading this topic from the end in hopes that there are instructions here, it would probably be more helpful to go directly to:
tbamud.com/forum/2-general/4436-running-...-using-visual-studio

Please Log in or Create an account to join the conversation.

Time to create page: 0.142 seconds