Page 1 of 1

Problems with Windows 7 64bit

Posted: Sat Apr 10, 2010 12:09 pm
by linjiayun
Hi!
I have 4.00 GB RAM. I have two operating systems, Windows XP 32bit and Windows 7 64bit. I installed Vsuite Ramdisk (Server Edition) 4.5 and now I have a problem.
In Windows 7 64bit, I can not choose "Enable OS Invisible Physical Memory" in the "Options" page. Maybe you want to ask, "Why you want to choose this? You are already running 64bit system." My answer: My mother board is really weak and it only support 3.00 GB RAM. Although I have 64bit system, it says: 4.00 GB (3.00 GB usable).
I also installed your software in Windows XP 32bit, I can choose "Enable OS Invisible Physical Memory" there and I can use all my 4.00 GB RAM in Windows XP 32bit. I want to do the same thing in Windows 7 64bit.
Please help me! Thanks!

Re: Problems with Windows 7 64bit

Posted: Sat Apr 10, 2010 12:22 pm
by Support
Hi,

Quite weird...

Yes, as you said, the 64-bit Windows shall be able to use 4GB ram. That's why we disable the Invisible Memory options. It is the first time that I see this kind of case. I am afraid that it may not be safe to enable Invisible Memory on 32-bit XP because it seems that your hardware may not support some features...

If possible, could you tell me the type of your motherboard?

Re: Problems with Windows 7 64bit

Posted: Sat Apr 10, 2010 1:07 pm
by linjiayun
Hi!
I just hope you can enable Invisible Memory options in all your versions in the future.
I enable Invisible Memory in my Windows XP 32bit and everything is fine. It seems it is safe.
I do not know what kind of information you want to know about my motherboard, now, I give you some. If you need more, just tell me.
Hope you can help me. Thanks!

Motherboard
CPU Type Mobile DualCore Intel Pentium T2310, 1466 MHz (11 x 133)
Motherboard Name Asus F5000Vl Series Notebook
Motherboard Chipset SiS M671DX
System Memory 3072 MB (DDR2-667 DDR2 SDRAM)
DIMM1: Kingston 9905295-055.A00LF 2 GB DDR2-667 DDR2 SDRAM (5-5-5-15 @ 333 MHz) (4-4-4-12 @ 266 MHz) (3-3-3-9 @ 200 MHz)
DIMM2: A-Data MIOPE1B163BZ 2 GB DDR2-667 DDR2 SDRAM (5-5-5-15 @ 333 MHz) (4-4-4-12 @ 266 MHz) (3-3-3-9 @ 200 MHz)
BIOS Type AMI (12/25/07)

Motherboard Properties
Motherboard ID 63-208-0000010-00101111-122507-SiS671$F5VL0002_BIOS DATE: 12/25/07 VER: 213
Motherboard Name Asus F5000Vl Series Notebook

Front Side Bus Properties
Bus Type Intel AGTL+
Bus Width 64-bit
Real Clock 133 MHz (QDR)
Effective Clock 533 MHz
Bandwidth 4265 MB/s

Memory Bus Properties
Bus Type DDR2 SDRAM
Bus Width 64-bit
DRAM:FSB Ratio 10:4
Real Clock 333 MHz (DDR)
Effective Clock 666 MHz
Bandwidth 5331 MB/s

Chipset Bus Properties
Bus Type SiS MuTIOL
Bus Width 16-bit

South Bridge Properties
South Bridge SiS 968
Revision 01

North Bridge Properties
North Bridge SiS M671DX
Supported FSB Speeds FSB533, FSB800
Supported Memory Types DDR2-400 SDRAM, DDR2-533 SDRAM, DDR2-667 SDRAM
Maximum Memory Amount 4 GB
Revision 00

Memory Timings
CAS Latency (CL) 5T
RAS To CAS Delay (tRCD) 5T
RAS Precharge (tRP) 5T
RAS Active Time (tRAS) 15T
Row Refresh Cycle Time (tRFC) 43T
RAS To RAS Delay (tRRD) 4T
Write Recovery Time (tWR) 5T
Write To Read Delay (tWTR) 3T
Read To Precharge Delay (tRTP) 1T
Additive Latency (tAL) 0T
Refresh Period (tREF) 7.8 us

Memory Slots
DRAM Slot #1 2 GB (DDR2-667 DDR2 SDRAM)
DRAM Slot #2 2 GB (DDR2-667 DDR2 SDRAM)

Re: Problems with Windows 7 64bit

Posted: Sat Apr 10, 2010 1:28 pm
by Support
Hi,

Thank you for the information.

just a surmise, is this problem possibly caused by the incompatibility of SDRAM? I find you use two different brands of SDRAM, which may have the compatibility problem. Or perhaps one of the SDRAM bars has problems?

Re: Problems with Windows 7 64bit

Posted: Sat Apr 10, 2010 2:28 pm
by linjiayun
Hi!
Thank you!
I think it is because of hardware problems too now... Maybe I can only use 3.00 GB RAM on this computer...
Sorry, I made a mistake. I suddenely realize that I can only use 3.00 GB in Windows XP too.
In Windows XP, My RAMDisk is 2.00 GB and I put 1.00 GB virtual memory in it. So, in task manager, It shows: Commit Charge: 2313M / 3934M.
Thank you anyway.