Jump to content











Photo
- - - - -

proposed idea for a PE with memory


  • Please log in to reply
15 replies to this topic

#1 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 26 February 2009 - 02:45 PM

One of the neat things about Knoppix is, it's ability to remember previous sessions.

A feature like this would be nice for PE too.

Having a little program, which checks at boot time the removable drives for stored session data, seems simple enough.
Also loading the saved 'documents and settings' instead of ModelRam or overlaying the two is easy, just as importing (most) saved registry data.

Though an idea, how to create a differential 'backup' of the registry hives, would be great!

--------------------------------

Now that the easy part is out of the way, on to the really interesting part.

Imagine a PE which could remember on which machine it was previously run and instead of installing all drivers via HWPnP each time new, it would just use a backuped file to import all hardware settings directly into the registry.
This would decrease boot times considerably.

Unsolved problems:
- How should the PE recognize the machine?
- How to import the settings soon enough, that the drivers become active.
- Like further above: How to create a differential backup of the system hive?


:cheers:

#2 sanbarrow

sanbarrow

    Silver Member

  • Developer
  • 788 posts
  • Location:Germany - Sauerland

Posted 27 February 2009 - 01:43 PM

Hi
most of this is already solved in MOA.

Though an idea, how to create a differential 'backup' of the registry hives, would be great!


Do you really want this ? - I don't want it - I use LODR-packs instead - serves the same purpose

#3 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 27 February 2009 - 03:24 PM

Hi
most of this is already solved in MOA.

Which exactly would be most?

Do you really want this ? - I don't want it - I use LODR-packs instead - serves the same purpose

Not really. Lets say, i change the options for program X and want to use them on the next computer/reboot. LODR packs can't do that. Since they don't store this information. They always default back to original configuration just like a clean booted PE.

:cheers:

#4 sanbarrow

sanbarrow

    Silver Member

  • Developer
  • 788 posts
  • Location:Germany - Sauerland

Posted 27 February 2009 - 10:22 PM

Lets say, i change the options for program X and want to use them on the next computer/reboot. LODR packs can't do that. Since they don't store this information.


Load program X by running the LODR-pack for program X. When you then want to inject some custom settings you simply apply another reg-patch. This could also be automated if you wanted this.
You just need to write one more batch that exports custom settings for program X.

Personally I would not want any automatic applying of patches at boot.
If i want to apply a custom patch on host XY only - I have lines like
regedit /s nmap-custom-settings.reg
regedit /s viclient-lastused-hosts.reg
in lastbatch.cmd.

As lastbatch.cmd is always used from a local path it is not applied when I boot on host YZ.
This way I easily can adjust host-specific bootup.
If I need custom drivers I just add a line to an optional custom batch that is applied before hwpnp.exe is executed.

#5 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 27 February 2009 - 11:05 PM

Of course i can create tons of reg files and import them manually.
Just as i could create a new PE. This time with the 'right' settings. :cheers:
Heck, i could even do the settings all over each time i use the app!

But i'm lazy.
I don't have a computer, so i can do things manually.
I have a computer, so it can do things automaticly!

btw. What has this to do with the topic?

The idea to store the data on the HDD of the accessed computer nicely circumvents the problem with the detection. But it's a dirty solution, to leave bits and pieces behind on a system. I don't like it especialy.


:cheers:

#6 sanbarrow

sanbarrow

    Silver Member

  • Developer
  • 788 posts
  • Location:Germany - Sauerland

Posted 27 February 2009 - 11:24 PM

Nobody said that you must store anything on computer XY - you can as well put that stuff on a portable USB-disk and there have several preconfigured environements for different machines

#7 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 28 February 2009 - 01:13 AM

I seem to have overlooked this before.

If I need custom drivers I just add a line to an optional custom batch that is applied before hwpnp.exe is executed.

I don't get this. Why would you need to run a batch, if you run hwpnp afterwards anyway?

:cheers:

#8 sanbarrow

sanbarrow

    Silver Member

  • Developer
  • 788 posts
  • Location:Germany - Sauerland

Posted 01 March 2009 - 03:58 PM

Hwpnp is an automated routine - before that is called I check for existance of a custom batch which is usually located outside of the ramloading images I use.
If that batch is found, it is called. With the batch then I can inject custom drivers like sound and video ...

#9 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 01 March 2009 - 04:18 PM

With the batch then I can inject custom drivers like sound and video ...

With injecting, i guess you mean copying the drivers from some other location to %systemdrive%?

:cheers:

#10 sanbarrow

sanbarrow

    Silver Member

  • Developer
  • 788 posts
  • Location:Germany - Sauerland

Posted 01 March 2009 - 04:50 PM

yes

#11 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 01 March 2009 - 05:36 PM

Sorry, but I have to ask this. :cheers:

Medevil, are you a programmer or not? :cheers:

If yes, what about exploring either Dokan:
http://www.boot-land...?showtopic=5116

or PhysicsFS:
http://icculus.org/physfs/


jaclaz

#12 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 01 March 2009 - 05:41 PM

I don't even want to know, why you copy drivers around in order to install them.
We two seem to live on two different planets and there is no way, we will ever agree on anything, i think.

:cheers:

#13 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 01 March 2009 - 05:49 PM

Medevil, are you a programmer or not? :cheers:

The correct answer would be, that i used to work as a programmer and think, that i still can write code. :cheers:
But writing a driver would be something completely new to me.

And now let me ask you a question. What has a free fbwf to do with the topic?

:cheers:

#14 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 01 March 2009 - 06:52 PM

The correct answer would be, that i used to work as a programmer and think, that i still can write code. :cheers:
But writing a driver would be something completely new to me.

And now let me ask you a question. What has a free fbwf to do with the topic?

:cheers:

It's not a free fbwf.

There should be no need to "write" drivers.

Only putting together some bits and odds here and there and possibly simply compiling already written code.

But programming knowledge is required.

As well it is required that you take some time to explore the whole idea of a FUSE filesystem (hopefully not needing to write a driver):
http://en.wikipedia....em_in_Userspace
when used together with a filesystem like
http://en.wikipedia....yte_File_System
or, better even:
http://www.filesyste...ct-unionfs.html

just imagine that you can have (and set by a .ini or configuration files) a number of mountpoints
i.e. a filesystem that can be built by "summing together" parts residing on different devices/directories/images/whatever

Wouldn't this be a solution? :cheers:

jaclaz

#15 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 01 March 2009 - 09:33 PM

One of us seems to be in the wrong topic. :cheers:
How exactly would any of this filesystems help to save data at shut down and import data on boot up?

But lets go over them one by one.
- Fuse - is a loadable kernel module - on NT systems all drivers are loadable, non are compiled into the kernel like in*ix systems.
- ZFS - is a file system designed by Sun Microsystems for the Solaris Operating System. To use this, NT would need a driver. To boot from it, even a special loader.
- unionfs - *ix version of NT overlay system. To get NT to do all the things *ix can do with unionfs, all fs drivers need to be rewritten since the NT driver model works completely different than the *ix one.
It might not even be possible to detach the fs from the device in NT.

Last but not least, what would be the benefit? I have even given up on fbwf years ago, since it's not needed and does not offer any advantage over a ramdisk.


:cheers:

PS: If you should ever come across a driver for NT systems, that allows the writing to CDFS as if it were FAT/NTFS, i would be very interested!

#16 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 01 March 2009 - 09:39 PM

just imagine that you can have (and set by a .ini or configuration files) a number of mountpoints
i.e. a filesystem that can be built by "summing together" parts residing on different devices/directories/images/whatever

You mean like NTFS hardlinks?

:cheers:




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users