SolidWorks & 64 bit

Maximum integer, signed vs. unsigned.

Does the "patch" & "switch" in some way change the data type MS is using in the OS (or perhaps the machine's BIOS) for memory addresses?

Point is, the 2 GB & 4 GB memory limits are a result of a 32 bit machine, not the fault of the applications software (SW in this case).

Reply to
Cliff Huprich
Loading thread data ...

The sign is irrelevant when speaking of memory addresses. It's all the same when allocating memory. You are just as likely to get address

0xF0FFFFFF as 0x00FFFFFF

No. It simply allocates less of the 4Gb for the OS. Normally Windows reserves 2Gb for itself. The hack lets you address 3 Gb, which means that 1 Gb formerly reserved for the OS is made available.

The 4Gb limit is the result of a 32 bit machine. The 2Gb limit is wholly artificial and imposed by Windows itself. For example, the out of the box Linux kernel has a 3Gb/1Gb split. If you have 1-4 Gb of physical RAM, you can actually compile the kernel to address all 4Gb (minus what the kernel actually reqires).

Jim S.

Reply to
Jim Sculley

PolyTech Forum website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.