For those who consider themselves brave, and for those who have an instance of Windows 2000/XP/Vista (though Vista is untested, it *SHOULD* work just fine),
This is ~2Mbyte download in which contains the QEMU runtime and related utilities, (inside .\QEMU directory), wget.exe, gzip.exe, and tar.exe (and related .dll's) (.\util), a
home.img file (.\data) that is made available at run time (though it isn't automagically formatted and mounted as of yet -- I've got all of the code working, just need to figure out how to merge this into the rPath build process), and two batch files --
launch.bat and nuxleus.bat.
Once the archive is unpacked, if you run "launch.bat" the process of accessing, unpacking, and installing the KQEMU accelerator will begin, as well as the accessing, unpacking, conversion, installation, and startup of the nuXleus image file will begin.
The process goes something like this,
- Access, unpack, install KQEMU accelerator.
- Access, unpack, and convert the nuXleus .img file to QCOW format (significant space savings (the .img.gz file will unpack to ~
1.7gigs, the QCOW image will weigh in at just over 300megs)
- Move the QCOW image into the .\image directory and delete the 1.7gig .img file
- Create an image overlay of the QCOW image -- what this does, in essence, is creates a new file called
nuxleus.ovl which is matched up with the nuxlues.qcow image. Any and all updates and changes to the system actually take place on the overlay file, leaving the original qcow file untouched. This allows nicely in regards to reverting back to the base system if something goes awry -- just delete the
nuxleus.qcow image and the next time launch.bat is run, it will notice that it doesn't exist and create a new one.
- After asking if you are ready, launch the nuXleus instance.
password: no password
This is simply a first take test. I am pulling this into a ClickOnce app for Windows, a .dmg file for Mac, and a Python setup.py file for Linux, but want to work through any and all issues with Windows setup first using as simple of a setup process as possible that allows anybody who understands how a Windows batch file works to hack as they might see fit with ease and convenience.
PLEASE NOTE: I am working on getting the size of the image file down to
a MUCH more manageable size of ~20megs. (basically the
-- I have the first half finished (up to Saxon.NET) and am working on
finishing out the integration of CherryPy, 4Suite and Amplee as we
speak) -- That said, at the moment, I have this set to access an image
which is approximately 93 megs. MUCH bigger than will be the final
image, but as mentioned, I am still working on the final image, so for
now this will at very least provide something for you to play with.
Please report any issues to http://nuxleus.com/dev/
or inline to this thread.
Thanks in advance for any and all help you all can give in getting this process perfected and the launch of the first official nuXleus beta out the door!
M. David Petersonhttp://mdavid.name