66 replies to this topic

[Oleg_II]

MedEvil
No need to invent, it's made with BartPE or NativeEx

Using WB (just indicate the path to the source CD):

1. Create folder structure, extract and copy needed files to the target directory (complitely possible and even easy).

2. Create "raw" regestry HIVE files from 5 INF files (Peter says it is possible).

3. There is a file SYSSETUP.INF from which most other OS components are installed (for example IE, Mplayer, speach support, etc.). They are installed during GUI installation stage (you see something like "Installing components"). Edit this file (delete some lines) and add needed settings from corresponding INF files directly into "raw" regestry (like they were already installed).
There are probably some more INF files (for example from SYSOC.INF) settings for which can be injected into "raw" regestry too (like the setup procedure installed them). It's possible, but need a lot of work.

In other words - inject as many settings from the working system as needed but don't touch hardware. Windows standard setup procedure will run but as folders are already created, files are already copied, most components are already installed and their installation INF files already cleaned (or even deleted from general installation INF files like SYSSETUP.INF and SYSOC.INF), setup will be faster - only installing hardware step in fact will take place and time (some hardware may be pre-installed too?).

That's just my thoughts, I may be wrong

[MedEvil]

MedEvil
No need to invent, it's made with BartPE or NativeEx

Using WB (just indicate the path to the source CD):

1. Create folder structure, extract and copy needed files to the target directory (complitely possible and even easy).

If i understand you right, you wanna copy to the HDD, sort of a partly pre-completed Xp-setup, to save time during the graphical setup, right?
But before the graphical setup, during the normal text setup, is it when the hal and kernel are detected and set. And for this you would need a replacement.
PE does not do that detecting, PE runs with the most common HAL and Kernel. The same the text setup uses to start.

[Oleg_II]

If i understand you right, you wanna copy to the HDD, sort of a partly pre-completed Xp-setup, to save time during the graphical setup, right?

In general, right

But before the graphical setup, during the normal text setup, is it when the hal and kernel are detected and set. And for this you would need a replacement.

Nope. Text setup won't be ommited completely. What will be ommited: creating folder structure and copying files (needed some file editing, for example, just delete all lines under SourceDisksFiles section and in a few more places - TXTSETUP.SIF won't copy files - copying is ommited and setup is shorter for 2-3 minutes for full installation).
Detecting HAL and Kernel will stay in place.

PE does not do that detecting, PE runs with the most common HAL and Kernel. The same the text setup uses to start.

HAL and Kernel are the same as in original system but all of them can be choosen during startup. I strongly believe if it is possible for PE that it should be possible for 'standard' OS.

[Oleg_II]

By the way, I may be wrong again but there is no real HAL and Kernel installation in text setup mode - they may be detected and needed files are placed in system32 but no regestry settings is made about it (?). Regestry is just assembled from INF files at this stage (?).

Who prevent us to place ALL common HAL files into system32 folder at this stage like it is in PE builds?

[MedEvil]

By the way, I may be wrong again but there is no real HAL and Kernel installation in text setup mode - they may be detected and needed files are placed in system32 but no regestry settings is made about it (?). Regestry is just assembled from INF files at this stage (?).

Who prevent us to place ALL common HAL files into system32 folder at this stage like it is in PE builds?

Good luck with your project!

[was_jaclaz]

May I remind you all about the "independent" project monohouse announced a long time ago? :
http://z3.invisionfr...hp?showtopic=97

(mostly based on BoldFortune hacks)

Though right now it is "on hold" in the last few months some nice work has been made on it:
http://newmanoa.ath.cx/

I believe that there are some good things in it, though it could be a problem finding and "extracting" them...


I'll mail him and see if he wish to share some of his findings.

jaclaz

P.S.: New location of this project:
http://manoa.flnet.org/

[gdogg]

Microwinx might be a good resource to compare file to reach an average 50Mb project.

gdogg uses a nlite profile to slim the windows source and then applies some reduction after the OS is installed.

He's also using minlogon.

The project can be found here: http://microwinx.com

You can download the project itself from here: http://web.archive.o...m/download.php# (click on the "Click Here To Accept This Agreement" checkbox) - a password will appear because the zipped file is password protected - try mirror 7 - still works.

You can also find instructions for nlite and microwinx here: http://www.microwinx.../nliteguide.php

gdogg released his project as free sometime, but got upset (don't know why) with some other members on msfn and decided to pull the plug some time ago.
There's also bold fortune's guide here: http://www.bold-fortune.com/forums with some good tips to when you dig for some details about something.

Good luck!

Hey, I have just been really busy right now. I have moved on to other things and have the potential to be employment for a hardware company.

I am interested in this project still, but I will need some help from some users who can use win builder to convert it over for , maybe the possibility to be added to winbuilder.

If anyone wants to volunteer, send me a PM.


Greg

[Brito]

Glad to see you back and well!!

[windrv]

Any updates?

[windrv]

Little Angel is released today at http://www.disklessangel.com

It introduces a new paradigm and a new way of minimizing/componetizing/customizing windows.

Ordinary users with little programming skills can start customizing their version of windows using Little Angel.

More advanced tools could be designed for such purposes; including enhancements with WB.

EDIT: by jaclaz

Please do see the clarification here:
http://www.boot-land...?...ic=3082&hl=

[Brito]

Hi Windrv!

I've visited your download site but the documentation inside the new app isn't very elucidative (yet), I have the impression it can be used to profile the needed files at boot time and help creating a minimal image (is this right?) - but would you please post a new topic dedicated just to little angel explaining it a bit more in detail and aditional feedback from other user experiences?

Another request: would it still be possible to have a trial version without time limits?

We've talked about it some time ago, do you think it can be done?

[windrv]

Little Angel (LA/la) is a package separate and different from Diskless Angel.

LA is intended for users to make customized windows image(s) for their use; including sization, componetization, universalization, etc.

LA can be used alone or with DA. Using by itself, it can help make customized windows image(s) running the normal way on hard disk; using with DA, users can take the customized windows image(s) to boot and run in virtual memory.

The basic image done (from booting up to settling down) is about 260MB. So using with DA, you can easily boot and run it up in a computer with only 512MB memory.

Little Angel Demo is good for trial of 30 days. It is fully functional for use.

As suggested, I shall open a new topic discussing what possibilities it offers and how it can be used.


EDIT: by jaclaz

The new topic is here::
http://www.boot-land...?...c=3082&st=0

[Oleg_II]

Ok. This topic is for universal system, right? And Diskless Angel is restricted to one specific computer so it's not exactly for this purpose.

For XP and Win2003 it can't be replaced by a couple of files from Win2003 (and maybe even not - maybe XP files will be enough, at least, as appeared, ramdisk.sys from Win2003 is not needed) which can deal with 500MB compressed image that is about 1GB of files and can be used on any computer available.

Let's concentrate on the topic and find the regestry settings for this universal system

[was_jaclaz]

SERVICE POST:

[quote name='Oleg_II' post='21401' date='Sep 25 2007, 11:22 AM']Let's concentrate on the topic and find the regestry settings for this universal system [/quote]

Right, as said:
[quote]The new topic is here:
http://www.boot-land...?...ic=3082&hl=

@All
I moved all posts related to whys and becauses of the licensing terms of Diskless Angel and Little Angel there.

Post THERE anything related to it.

jaclaz

[windrv]

Ok. This topic is for universal system, right? And Diskless Angel is restricted to one specific computer so it's not exactly for this purpose.

For XP and Win2003 it can't be replaced by a couple of files from Win2003 (and maybe even not - maybe XP files will be enough, at least, as appeared, ramdisk.sys from Win2003 is not needed) which can deal with 500MB compressed image that is about 1GB of files and can be used on any computer available.

Let's concentrate on the topic and find the regestry settings for this universal system

Yes, you have found what you need and do it yourself please. So don't bother to pressurize us on releasing it free anymore.

So what is your idea about how to do an universal system? Any enlightenment?

[oopsboy]

My two cents, why not have a minium PE, with Hardware ID scanning, when boot up, normally should have internet connection, detect the hardware ID, download the driver from internet repository, during the process, you can pick and choose the driver you want to install.

The driver archive can sit on server somewhere, or can be packed into CD. Everyone pay a license fee to use the archive and server.

[sbaeder]

My two cents, why not have a minium PE, with Hardware ID scanning, when boot up, normally should have internet connection, detect the hardware ID, download the driver from internet repository, during the process, you can pick and choose the driver you want to install.

The driver archive can sit on server somewhere, or can be packed into CD. Everyone pay a license fee to use the archive and server.

I think this already exists For example, in the Win7PE_SE project, we have scripts to access the driver packs. They can be loaded onto the CD/USB - OR downloaded from the internet (assuming you at least put all the necessary drivers to get the NIC running )

If you did that, then the driverpacks site has the files you need, etc. Win7PE_SE also allows you to "install" software into the running PE, so it would allow installing a driver, etc. and could run in a VM...

So, what is there really left to do???