Hello Bootland (Reboot.pro) community,
I have now read a lot of topics over the last many days to try and figure it out. I have seen that there are a lot of tools available.
I haven't done much testing yet as I don't know where to start. I have some decent computer knowledge and can oftne figure things out myself. But i'm not an software developer or engeneer. Its self taught over serial years. I edit scripts and can write my own batch files for simple and sometome more complex stuff.
The thing I want to archive (if its even possible) is to create an img file of server 2003 x64. The I want to load this image into ram and have integrated driver for the PC i'm using. I think its kinda a like approach like
"Universal HDD Image files for XP and Windows 7"
http://reboot.pro/98...124295__st__195
But I want to archive this for a x64 system (because I got alot of ram, 8 GB). I want to load this image into ram at bootup so everything is running in my ram and on reboot every change (to the server 2003 partition) will be gone. I think this would involve using grub4dos, firadisk and some other tools. I'm kinda stuck here and don't know where to begin as I haven't made any PE or similiar yet but I want to try and see if I can archive this. I would like to have a full of a system as possible so everything should work (no major stripping), like games, see movies, internet search and use of portable software.
The reason I want to use server 2003 x64 over x86 is that I got more than the 4GB limit. Would it be clever to use x86 instead and use /PEA switch,would it work in such a setup?
Thank you for listening and I hope someone can guide me in the right direction, where to start and how to begin such a project.
Question: server 2003 x64, boot into ram
Started by
franner
, Mar 08 2011 08:47 AM
1 reply to this topic
#2
Wonko the Sane
-
- Advanced user
-
- 16066 posts
The Finder
- Location:The Outside of the Asylum (gate is closed)
-
Italy
Posted 08 March 2011 - 09:47 AM
The "Universal HDD Image files for XP and Windows 7" is about "universal" 
.
What you need/want should be simpler, i.e. you don't need multiple hardware support for the moment.
The key point is as I see it how 2003 64-bit "behaves" and which 64-bit compatible driver can use "over 4Gb" memory.
The available "test-signed" Firadisk 64 bit has been tested on Windows 7 only AFAIK and cannot say if it will work on 2003.
If I were you I would first try it as a "normal" ramdisk driver in a "normal" install and see how it behaves, before attempting to use it as "boot volume driver".
I.e., with reference to first post in the Firadisk thread, you should try what happens following the:
"Firadisk driver installation instruction for Windows XP"
and
"How to create/mount raw disk image with FiraDisk 0.0.1.12 "
before tackling any other example.
Wonko
.What you need/want should be simpler, i.e. you don't need multiple hardware support for the moment.
The key point is as I see it how 2003 64-bit "behaves" and which 64-bit compatible driver can use "over 4Gb" memory.
The available "test-signed" Firadisk 64 bit has been tested on Windows 7 only AFAIK and cannot say if it will work on 2003.
If I were you I would first try it as a "normal" ramdisk driver in a "normal" install and see how it behaves, before attempting to use it as "boot volume driver".
I.e., with reference to first post in the Firadisk thread, you should try what happens following the:
"Firadisk driver installation instruction for Windows XP"
and
"How to create/mount raw disk image with FiraDisk 0.0.1.12 "
before tackling any other example.
Wonko
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
