Help on moving to Win64 bit system?

[Sharon]

I'm thinking to move from WinXP 32bit to Windows 2003 Server 64 bit.
But first I have some unclear issues that would like to clarify in here
using your kind help:
(1) Can I take a driver (like the Coerce Frame Grabber Driver) that is used
for Windows XP 32 bit and use it on the 64 bit system?
(2) Assuming the answer to (1) is true - Can I use the 32 bit driver from
within a 64 bit application?
Do I need to write mixed code in my application, I mean; does my application
should be build from mixed components (DLL's), some of them 32bit, and some
of them 64 bit?
How will the mixed 32/64 components will interface with each other?
(3) On a 64bit system; How a 32bit executable should communicate with a
64bit executable? Does the C#/.NET remoting and TCP will work to communicate
between the two?
(4) What is the maximum continuous memory chunk limit per process in a Win64
bit system (with and without the linkage switch and Boot.ini switch)?
(5) What is different between WinXP 64bit and Windows 2003 Server 64 bit?
-------------
Thanks a lot
Sharon

[Peter Bromberg [C# MVP]]

Sharon,
1) All drivers for Windows 2003 Server 64bit must be 64 bit drivers. I use
x64 version, and so far the only driver I haven't been able to find is the
bluetooth USB, but I suspect I could hack the one from the Windows XP 64 bit
x64 version.

2) No, you cannot use a 32 bit driver. A 32 bit application, yes.

3) Not sure how a 32 bit app might communicate with a 64 bit app.

4) for memory architecture, go here:

http://support.microsoft.com/default...;EN-US;q294418

5) difference between XP and Server 64 bit versions is virtually identical
to the differences between the associated 32 bit versions.

Peter
--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Sharon" wrote:

I'm thinking to move from WinXP 32bit to Windows 2003 Server 64 bit.
But first I have some unclear issues that would like to clarify in here
using your kind help:
(1) Can I take a driver (like the Coerce Frame Grabber Driver) that is used
for Windows XP 32 bit and use it on the 64 bit system?
(2) Assuming the answer to (1) is true - Can I use the 32 bit driver from
within a 64 bit application?
Do I need to write mixed code in my application, I mean; does my application
should be build from mixed components (DLL's), some of them 32bit, and some
of them 64 bit?
How will the mixed 32/64 components will interface with each other?
(3) On a 64bit system; How a 32bit executable should communicate with a
64bit executable? Does the C#/.NET remoting and TCP will work to communicate
between the two?
(4) What is the maximum continuous memory chunk limit per process in a Win64
bit system (with and without the linkage switch and Boot.ini switch)?
(5) What is different between WinXP 64bit and Windows 2003 Server 64 bit?
-------------
Thanks a lot
Sharon

[Sharon]

Thanks a lot for the info.

But I still couldn't find an answer to the thread question: What is the
maximum continuous memory chunk limit per process in a Win64
bit system (with and without the linkage switch and Boot.ini switch)?

The article you mentioned does not say what is the maximum continuous memory
chunk limit per process in a Win64 bit system.
--
Thanks
Sharon

[Willy Denoyette [MVP]]

"Sharon" <Sh*****@newsgr oups.nospam> wrote in message
news:58******** *************** ***********@mic rosoft.com...
| Thanks a lot for the info.
|
| But I still couldn't find an answer to the thread question: What is the
| maximum continuous memory chunk limit per process in a Win64
| bit system (with and without the linkage switch and Boot.ini switch)?
|
| The article you mentioned does not say what is the maximum continuous
memory
| chunk limit per process in a Win64 bit system.
|
|
| --
| Thanks
| Sharon

There is no such thing as "maximum contiguous memory chunk" defined at the
process level, there is only a maximum user virtual address space (VAS) per
process.
The maximum user VAS for X86 Windows is 2GB or 3GB (/4GT tuning), and ~8TB
for X64.
The size of the largest chunk of contiguous memory available in the VAS is
subject to the amount of fragmentation. This is true for both X86 and X64,
of course finding a contiguous chunk of 10GB on X64 won't be an issue with
such a huge VAS.
Willy.

[Kevin Yu [MSFT]]

Hi Sharon,

If you're working on a managed app, there is no problem using the remoting
or TCP.

theoretically speaking, a 64-bit process can use as much as 8TB memory. So
the maximum memeory chunk is 8TB. However, some spaces will be taken by the
code segment. Also, if some block has been assigned in the middle of the
chunk, you will note get 8TB continuous chunk.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

[Sharon]

Thank you all for your prompt info.

Kevin - When you say "there is no problem using the remoting or TCP.", are
you referring to my third question regarding the communication between 32bit
process and a 64bit process?

Furthermore; Can a win32 DLL can communicate with win64 DLL and vice versa?

--------
Thanks
Sharon

[Willy Denoyette [MVP]]

"Sharon" <Sh*****@newsgr oups.nospam> wrote in message
news:52******** *************** ***********@mic rosoft.com...
| Thank you all for your prompt info.
|
| Kevin - When you say "there is no problem using the remoting or TCP.", are
| you referring to my third question regarding the communication between
32bit
| process and a 64bit process?
|
| Furthermore; Can a win32 DLL can communicate with win64 DLL and vice
versa?
|
|
|
| --------
| Thanks
| Sharon

64 bit applications can only load 64 bit DLL's, 32 bit applications can only
load 32 bit (non COM) DLL's.
For inter-process communication, you can use any IPC mechanism available in
windows. That means you can use COM+, DCOM, RPC, and the lower level IPC
protocols like named pipes and sockets as IPC mechanism between 64 bit and
32 bit applications. As Kevin said, managed applications can use remoting as
interop channel between 64bit and 32 bit managed applications.
Willy.

[Sharon]

If I'm using a 32bit machine (hardware: CPU, drivers etc.) as my development
PC; Can I use this PC (with installed VS2005) to compile code for 64bit to be
executed on another 64bit PC?
Or must I also compile the code on a 64 bit machine?

---------
Thanks
Sharon

[Sharon]

If I'm using a 32bit machine (hardware: CPU, drivers etc.) as my development
PC; Can I use this PC (with installed VS2005) to compile code for 64bit to be
executed on another 64bit PC?
Or must I also compile the code on a 64 bit machine?

---------
Thanks
Sharon

[Willy Denoyette [MVP]]

"Sharon" <Sh*****@newsgr oups.nospam> wrote in message
news:B8******** *************** ***********@mic rosoft.com...
| If I'm using a 32bit machine (hardware: CPU, drivers etc.) as my
development
| PC; Can I use this PC (with installed VS2005) to compile code for 64bit to
be
| executed on another 64bit PC?
| Or must I also compile the code on a 64 bit machine?
|
| ---------
| Thanks
| Sharon

VS 2005 PRO can be used to compile native C++ as 64 bit, but you need a 64
bit OS to run or debug.
Managed code JIT compiles to 32 bit code on 32 bit platforms and to 64 bit
code on 64 bit platforms (OS and Framework).
Willy.