Windows XP Pro x64 and RunUO

[Marlberg]

I have just built a fairly decent box for my shard admin.
It has the following on it
AMD 64 X2 4200 Manchester Dual Core Processor
4 Gigabytes of Low Latency RAM (2.5)
One XFX nVidia 6800GS with 256MB of DDR3 RAM
4 WD2500 SATA II 7200 HDD in a RAID 0+1 Array
Windows XP Pro x64 on logical Drive C:\> 30GB Logical Partition
Drive D:\> is formatted NTFS but no OS "yet" also 30GB Logical Partition just waiting to see if I need Windows XP Pro 32 on it
and Drive E:\> is a 390 GB Logical partition for our Data Drive

Now we want to run RunUO and almost nothing else other than OS and driver software on this box for the shard.

What I need to know is are we going to be able to run RunUO on Drive C?
The 64bit partition?

Will WOW64 and RunUO actually get along together?
The WOW64 should allow the 32bit application to Run just fine but I dont know. Anyone that has had experiences with this please comment.

If it wont run I need to know that too. I can always try to tweak Win 32's Registry by adding the /3GB switch but if I can take advantage of 64 I would like to.

I also have the ability to recompile the source if necessary under the 2.0 Framework.

I REally would like one of the Devs input on this as well as any of the members who have had experience with 32 on 64 bit systems

[bzk90]

windows xp pro is a bastard OS, just use 32bit for now

[Marlberg]

Originally Posted by bzk90

windows xp pro is a bastard OS, just use 32bit for now

I dont mind problems and I dont mind workarounds and I would appreciate someone who has actually worked with it and run uo success or failure to reply and reply with something meaningful please. scurrilous posts do me no good.

[Marlberg]

Originally Posted by Seanchen.net

Recompile the core using the x64 .NET Framework 2.0 and you won't have to use the emulator.

Anything I should know before I recompile? like are unsafe pointers going to need to be redone with managed code?

[daat99]

Originally Posted by Marlberg

Anything I should know before I recompile? like are unsafe pointers going to need to be redone with managed code?

Just make sure you read this before you recompile the core:
Using a Modified Core.

[tophyr]

You may have trouble with packets, I'm not sure how they handle serializing their data offhand but if they use unsafe code AND rely on an int being 4 bytes, you'll have issues.

Unsafe blocks in general don't require changes unless they weren't coded properly for portability in the first place. I haven't looked at RunUO's unsafe parts.. just make sure they use sizeof() everywhere they should. Judging just by the system you built and the issues you asked about, I'm betting you know enough about programming to be able to use pointers properly, but if you have any issues you can PM me if you like, I've got even more C/C++ experience than I do C#.

[Marlberg]

Originally Posted by tophyr

You may have trouble with packets, I'm not sure how they handle serializing their data offhand but if they use unsafe code AND rely on an int being 4 bytes, you'll have issues.

Unsafe blocks in general don't require changes unless they weren't coded properly for portability in the first place. I haven't looked at RunUO's unsafe parts.. just make sure they use sizeof() everywhere they should. Judging just by the system you built and the issues you asked about, I'm betting you know enough about programming to be able to use pointers properly, but if you have any issues you can PM me if you like, I've got even more C/C++ experience than I do C#.

Yeah I have a "little c#" I write for Wachovia during the day. Windows Services using C# and managed C++ Web Services using C# and XML and of Course SQL Server Sybase and Oracle on a Uni Platform
But im always on the lookout for people that know more than me so that I can learn from them.

Ive taken a look at the core source code and it looks like the source that is unsafe can be made safe by using arrays and structs in most cases instead of pointers. it may incur some extra overhead but with the beast I built that Shouldnt be a problem.

Ill have to give it more than a cursory glance though to be sure.

[Rhetorical]Now I wonder If I can port it to Visual Studio 2005 Pro edition...[/Rhetorical]

[Ravatar]

Originally Posted by tophyr

You may have trouble with packets, I'm not sure how they handle serializing their data offhand but if they use unsafe code AND rely on an int being 4 bytes, you'll have issues.

Unsafe blocks in general don't require changes unless they weren't coded properly for portability in the first place. I haven't looked at RunUO's unsafe parts.. just make sure they use sizeof() everywhere they should. Judging just by the system you built and the issues you asked about, I'm betting you know enough about programming to be able to use pointers properly, but if you have any issues you can PM me if you like, I've got even more C/C++ experience than I do C#.

int's are still 4 bytes, pointers are what has changed

[blkdrac]

The reason why RunUO wont run on x64 is because it require's .NET v1.1, and the lowest that x64 has available to it is .NET v2.0

It has been stated that the next release of RunUO will run on .NET v2.0.

Soooo... unless ya wanna recompile the core files (which is a pain LOL) it's best to just wait.

Just my 2 cents worth of info... and I am sure someone will complain about it LOL

[Marlberg]

Originally Posted by blkdrac

The reason why RunUO wont run on x64 is because it require's .NET v1.1, and the lowest that x64 has available to it is .NET v2.0

It has been stated that the next release of RunUO will run on .NET v2.0.

Soooo... unless ya wanna recompile the core files (which is a pain LOL) it's best to just wait.

Just my 2 cents worth of info... and I am sure someone will complain about it LOL

Fortunately for me I do have three things going for me here.
1. I am quite willing AND capable of recompiling the core.
2. I dont find porting code from one platform to another a PAIN! I actually find writing and rewriting code a joy! Its what we do right? we are natures better mouse. The old fashioned mousetrap doesnt get us because we are smatter than it is.
3. I have available to me a Volume Licenses Universal Subscription to MSDN. I get all of MS products when they are released. I have several ways I can run and if all else fails. I can of course recompile under 2.0

[Marlberg]

Originally Posted by blkdrac

The reason why RunUO wont run on x64 is because it require's .NET v1.1, and the lowest that x64 has available to it is .NET v2.0

Actually I find that if you look hard enough even the impossible to do can be done given that you are willing to try.

Case in point RunUO is up and Running on the computer spec'd at the begining of this thread ON Windows XP Pro x64. It is running under the WOW64 subsystem (Program Files (x86) directory instead of Program Files)

Its runnig very smooth all of the ram is being addressed and usable and I DID NOT have to recompile under 2.0 the only change we had to make was the for the IIS Services for which there exists an article on how to make the .NET Framework 1.1 run on a 64 bit OS. the article is URL="http://support.microsoft.com/default.aspx?scid=kb;en-us;894435"]here.[/url]

This article also goes on to explane that you need to run the following command in order to run .net framewor 1.1 on IIS 6 on Windows XP Pro x64:

1. Click Start, click Run, type cmd, and then click OK.
2. Type the following command to enable the 32-bit mode:

cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1 

3. Type the following command to install the version of ASP.NET 1.1 and to install the script maps at the IIS root and under:
%SYSTEMROOT%\Microsoft.NET\Framework\v1.1.4322\asp net_regiis.exe -i

Our Shard Perilous Dragon is doing quite well at the moment stop by and chat with us