Posted 13 February 2007 - 01:29 PM
QEMU on Windows Version 0.9.0 Fabrice Bellard http://www.h7.dion.ne.jp/~qemu-win/
7-Zip 4.57 © Igor Pavlov http://www.7-zip.org
dd for windows John Newbigin http://www.chrysocome.net/dd
- cfadisk.sys http://www.911cd.net...showtopic=14292
- RegDACL.exe http://www.heysoft.d.../f_sw_rt_en.htm
- flashnul.exe http://shounen.ru/soft/flashnul/
Antivirus, explorer(user) etc. should not interfere in work virtual machine (Qemu)
Web server - [url="http://mobileos.boot-land.net""]http://mobileos.boot-land.net"[/url]
Somebody already tasted this OS?
Scripts which are at this forum almost approach MobileOS
I think, that it can replace Preinstallation Environment.
Posted 20 February 2007 - 11:40 PM
I'll try it next weekend, looks really good!
Posted 22 February 2007 - 12:43 AM
I am confident, that i will manage to create sometime automated method based by scripts Winbuilder. I hope for reciprocal efforts
Posted 22 February 2007 - 12:01 PM
They create a XP based build (not PE) also sized around 50Mb, it's not using explorer shell or anything else added, but the result is very similar to our liveXP project and it will surely be easier to tweak with all the experience gathered from PE environments.
Don't be afraid to place any doubts you have regarding the script syntax or anything else in wich you need help - This is a really promissing project..
Posted 27 February 2007 - 01:00 PM
In projects a plenty of the information (in registry) included in installation CD contains.
Maybe to an release version 1.0 it will be possible .
Posted 27 February 2007 - 01:44 PM
Do you need support for reading INF file from MS format?
Never thought about it, but I can give it a try - but it will take a while since I already have a few other code sections needed to be recoded and modified. Then I'll definitively help you better on this task!
Posted 28 February 2007 - 12:37 AM
Do you need support for reading INF file from MS format?
Windows XP registry contains ~10Mb keys which basically are read from inf files.
Bart has directed us not at that way.
Posted 28 February 2007 - 10:07 AM
This way it would be 100% ms compatible since we'd be using their INF engine - I would surely take a lot of time to get a good working result and this way seems faster to test this theory on real builds.
Posted 28 February 2007 - 11:08 PM
For the beginning it most suitable variant.
Wouldn't it be simpler to load the XP hive from the running project onto the local registry and then modify the paths on the INF files to match the loaded hive?
Posted 09 March 2007 - 03:27 AM
This is something I've been playing with for two years...
Regular XP as a runtime image!
Do you have it EWF enabled yet?
I'll be curious to see your project continue.
Both PE and regular Windows developers have reduced their platforms to 15MB each, they're very similar.
Posted 09 March 2007 - 11:04 AM
One thing: why is nlite required to slim the source?
We can copy only the needed files and remove unneeded entries from txtsetup.sif ourselves with wb, and the installation process can be simulated with qemu - I can help you with this process if you need.
Imagine it this way: We create the modded windows source as an ISO and proceed to use it as boot image on qemu - it's possible to generate an answer file that will provide all needed steps in an unatended fashion install on the emulated disk.
The serial number needed to install windows *must* be provided by the user itself - this can either be added from a script box inserted into the unnatended answer file, or user will input when windows is installing.
After the installation is complete, the registry patch is added and files.7z is created fresh - at this point I'm not sure on the best approach to copy files.7z from the guest OS - perhaps using network support, but on systems with firewall activated or even vista would make it hard to work as expected. Can't we use the disk image itself as source and mount it on our host OS since we can always create a fresh image disk on each build? This would also make it easier to manipulate files.
In either case, a small app - (using autoIt for example) can do these tasks unnatended, and order the system to shutdown, wich will cause qemu to close itself and allow the script processing to continue.
A message box asks the user if the created image is working correctly and proceed with the rest of build process.
End result is a completely unnatended XP hardware independent OS done with efficiency...
In my opinion, this would be a mobile solution I would use all day long...
Posted 09 March 2007 - 12:06 PM
Posted 12 March 2007 - 12:21 AM
I not use Longhorn.
Thank you for idea. Еventually we find way to simplify this process .
However if will appear the script , simplifying making MobileOS I will glad .
Posted 12 March 2007 - 02:44 AM
I've been looking at how the registry must be modified so that we can make a hdd install straight from the source cd. DigitalProductIDs must be added and other things too, but it's very possible.
Obviously we can benifit from Nuhi's knowledge by studying a small nlited XP. I want to do something similar to what euhenio is doing using nlited xp but using just the source cd. The end result to be a generic hardware vhd image you could restore to bare metal or boot into RAM from cd/dvd/hdd.
Communication may by a little tricky but I 'd like to help with this project if I can.
Posted 12 March 2007 - 03:41 AM
I found that for universal system some files should be extracted from DRIVER.CAB and placed in system32 and system32\drivers folders - it is possible to find out which files from WinBuilder stable build.
Some SATA/RAID drivers can be added to MobileOS for this purpose too.
Some pre-made regestry tweaks like USB support can be added for universal system too.
The only problem is in creating working Registry. The only way I see is to take regestry files from user's working system and edit them in WinBuilder - delete and add some keys with pre-made scripts.
Where to take these scripts? Compare full installation XP regestry with nLited or xplited regestry (maybe with both) and finding which keys should be added and which deleted to achive the goal.
nLited system seems to be smaller. xplited system seems to be more stable. IMHO.
Some regestry settings maybe taken from BartPE hives aslo.
If generic Regestry creating is possible any programs and language support can be added by a user through regular scripts during building.
NIKZZZZ from Ru-Board created new utility for saving image of running in RAM system. That could be very usefull because as we know any changes in MobileOS can't be saved after reboot. And this can be usefull for capturing the system itself (I have not tested it yet).
PS Just thought of it: maybe some functions in XP can be replaced by free alternatives like native netwoking replaced with PENetwork GUI? That way some more files and regestry settings can be deleted.
Posted 12 March 2007 - 06:44 AM
There's a guy, Bold Fortune, he made batch files which reduce an installed XP system, however, I'm leaning toward a nlite based project because of the small size that users have achived. I've been running nlite throughout the day to work out a few bugs and make sure the new version is working ok. Actually, I've reverted to v1.2.1 which has produced a stable build I'm running on a VM now. Taget size is about 135MB for the setup i386 with most fuctions still in tact, any smaller and the loss of funtionality is too great. When done, hopefully tomarrow, I'll start building my list to generate scripts.
Thanks for reporting your success!
Wouldn't it be nice to run the image out of RAM if you want to?
The end project might use a DOS based install, or even a mini Linux, to load OR restore the XPSP2 system image made from the install CD.
Posted 12 March 2007 - 06:54 AM
If you need CHM files openning I can give you work around (works fine) or you can use a free program xCHM (works fine with English).
I open video files with Mplayer that doesn't need video playback support (self containing).
DirectX with sound support, printing, scanning, new devices drivers installation and, all kind of internet connections - all works fine.
No IE, OE, Task scheduler, MS Help (CHM files can be opened fine though with a small addition
PS No need for install at all - when you prepare the build just place it on virtual drive created with BootSDI.script I don't even think we should concentrate on installing - it's just for achiving the fewest files set for working system with the most functionality. When using WB we only need extact and place into Target sub-folders needed files from the source CD and find out how to create the Regestry in WB.
I run this image right now and writing this from RAM
PPS And I forgot to mention that you can delete a lot of files from installed system too: .LOG, .TMP, .PNF, .EVT, .OLD, etc. - it was about 10MB in my system! Some fonts should be revised if they are really used After extracting some files from DRIVER.CAB and SP2.CAB they also can be deleted. No need for DLL Cache. And so on.
Posted 12 March 2007 - 07:39 AM
I already know where to export most all of the DigitalProductIDs, WPA, WGA.. (etc.) entries from in the registry.
It will be easy for me to start building a script and concentrate on the registry patching once the nlite build is imaged and ready for building lists. thx!
...and now I'm posting from the nlited system that just finished installing, It's about 20-30MB. bigger than yours, but still very fast even in a VM!
No IE front end, but the engine was left so I'm using explorer to surf the net before going to sleep. I'll try your presets tomarrow.
here I am ..
Posted 12 March 2007 - 08:13 AM
I think that this also will be difficult - some people needs IE, some want to have Task scheduller, some will need OOB or even Old CDPlayer...
Would it be better not to stick with ALL functionality but with some features that are difficult to reproduce in PE systems like WiFi with security, printing and scanning? Most of other features including HTML rendering can be added with regular scripts during the build.
Posted 12 March 2007 - 09:04 AM
Interesting and promissing but not right now
Posted 12 March 2007 - 12:41 PM
It works for most drivers and I think it can be usefull in MobileOS project.
The WB plugin for this is very easy - just copy two files and extract one from the source CD. I'm attaching mine and if somebody wants he/she may adjust it for better look and functionality
As for universal mass storage driver... I'm not an IT specialist, I'm just transfering Yurkesha's opinion about it
Posted 12 March 2007 - 03:36 PM
Later today I will. reproduce your build...100MB. is a good target size!!!
We'll obviously need to load generic drivers for most hardware, jaclaz is excellent to have around isn't he? thanks for the info!!
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users