Digg this topic Add to my del.icio.us Submit to SlashDot 31 Pages V  < 1 2 3 4 > »   
Reply to this topicStart new topic
> MobileOS
thunn
post Mar 9 2007, 03:27 AM
Post #11


Advanced Member
***

Group: .script developer
Posts: 373
Joined: 27-July 06
From: Queens, New York
Member No.: 75


United States


Thanks for project script! Looks very interesting.
This is something I've been playing with for two years...
Regular XP as a runtime image!
Do you have it EWF enabled yet?
(IMG:http://www.boot-land.net/forums/style_emoticons/default/smile.gif)
I'll be curious to see your project continue. (IMG:http://www.boot-land.net/forums/style_emoticons/default/wink.gif)

Both PE and regular Windows developers have reduced their platforms to 15MB each, they're very similar.
Go to the top of the page
 
+Quote Post
Nuno Brito
post Mar 9 2007, 11:04 AM
Post #12


Advanced Member
***

Group: .script developer
Posts: 4,279
Joined: 13-July 06
From: Azores
Member No.: 1


Portugal


Thanks for this release!

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... (IMG:http://www.boot-land.net/forums/style_emoticons/default/thumbup.gif)

In my opinion, this would be a mobile solution I would use all day long... (IMG:http://www.boot-land.net/forums/style_emoticons/default/punk.gif)
Go to the top of the page
 
+Quote Post
thunn
post Mar 9 2007, 12:06 PM
Post #13


Advanced Member
***

Group: .script developer
Posts: 373
Joined: 27-July 06
From: Queens, New York
Member No.: 75


United States


You bring up some good points...why nlite? Good question to which there are many answers but you may be right. Is the XP Setup process so difficult to reproduce? I think we already know it's more flexible than we're led to believe. I'm thoroughly familiar will all pre-Vista UA practices and find all of this sparking some ideas. I have pre-scripted installs and a good bit of undocumented information on winnt.sif, but I don't even think you need all that, just a simple answer file combined with Nuno's detailed knowledge of the NT OS core should suffice. Just to make it interesting, you could use something like Longhorn 4047? (IMG:http://www.boot-land.net/forums/style_emoticons/default/smile.gif)
Go to the top of the page
 
+Quote Post
euhenio
post Mar 12 2007, 12:21 AM
Post #14


Advanced Member
***

Group: Advanced user
Posts: 128
Joined: 9-December 06
From: Minsk
Member No.: 1,777



thuun
I not use Longhorn.
Nuno Brito
Thank you for idea. Еventually we find way to simplify this process .

However if will appear the script , simplifying making MobileOS I will glad .
Go to the top of the page
 
+Quote Post
thunn
post Mar 12 2007, 02:44 AM
Post #15


Advanced Member
***

Group: .script developer
Posts: 373
Joined: 27-July 06
From: Queens, New York
Member No.: 75


United States


I was only joking.
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. (IMG:http://www.boot-land.net/forums/style_emoticons/default/smile.gif)
Go to the top of the page
 
+Quote Post
Oleg_II
post Mar 12 2007, 03:41 AM
Post #16


Advanced Member
***

Group: Advanced user
Posts: 256
Joined: 15-October 06
From: Somewhere in the East
Member No.: 787



Needed files for the system can be taken directly from source CD - make one small and stable build with nLite and you'll know the files and their locations in the build. It's no problem at all (I have this about 300MB with working printing, scanning, duil-up adsl and WiFi and think it could be reduced some more, most of my programs work and it's about 200MB on compressed NTFS image).

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.
Go to the top of the page
 
+Quote Post
thunn
post Mar 12 2007, 06:44 AM
Post #17


Advanced Member
***

Group: .script developer
Posts: 373
Joined: 27-July 06
From: Queens, New York
Member No.: 75


United States


Oleg_II,
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? (IMG:http://www.boot-land.net/forums/style_emoticons/default/wink.gif)
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.
Go to the top of the page
 
+Quote Post
Oleg_II
post Mar 12 2007, 06:54 AM
Post #18


Advanced Member
***

Group: Advanced user
Posts: 256
Joined: 15-October 06
From: Somewhere in the East
Member No.: 787



You can try my LASTSESSON.INI (nLite v1.3) and take out Chinese Simplified and Russian languages support. For now I only have one very serious bug - I can't run some MSI installers in the system (IMG:http://www.boot-land.net/forums/style_emoticons/default/confused1.gif) Everything else seems to be functioning well. New source is less then 120MB (without languages it will be about 100MB).

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 (IMG:http://www.boot-land.net/forums/style_emoticons/default/wink.gif)


PS No need for install at all - when you prepare the build just place it on virtual drive created with BootSDI.script (IMG:http://www.boot-land.net/forums/style_emoticons/default/wink.gif) 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 (IMG:http://www.boot-land.net/forums/style_emoticons/default/what.gif)

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 (IMG:http://www.boot-land.net/forums/style_emoticons/default/wink.gif) After extracting some files from DRIVER.CAB and SP2.CAB they also can be deleted. No need for DLL Cache. And so on.
Attached File(s)
Attached File  Last_Session.zip ( 6.22K ) Number of downloads: 29
 
Go to the top of the page
 
+Quote Post
thunn
post Mar 12 2007, 07:39 AM
Post #19


Advanced Member
***

Group: .script developer
Posts: 373
Joined: 27-July 06
From: Queens, New York
Member No.: 75


United States


That's right, no install, just restore or load!
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. (IMG:http://www.boot-land.net/forums/style_emoticons/default/smile.gif) I'll try your presets tomarrow.

here I am (IMG:http://www.boot-land.net/forums/style_emoticons/default/wink.gif) ..
(IMG:http://thuun.boot-land.net/img/xpcore.png)
Attached File(s)
Attached File  PrintFolders.7z ( 34.81K ) Number of downloads: 26
 
Go to the top of the page
 
+Quote Post
Oleg_II
post Mar 12 2007, 08:13 AM
Post #20


Advanced Member
***

Group: Advanced user
Posts: 256
Joined: 15-October 06
From: Somewhere in the East
Member No.: 787



More 30MB - it's a half of WinBuilder stable build with network support and some appz! (IMG:http://www.boot-land.net/forums/style_emoticons/default/wink.gif)

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.
Go to the top of the page
 
+Quote Post

31 Pages V  < 1 2 3 4 > » 
Fast ReplyReply to this topicStart new topic

Members Who Viewed Topic Today ()

 

RSS Lo-Fi Version Time is now: 27th October 2007 - 11:09 AM

MKPortal ©2003-2006 mkportal.it