1 reply to this topic

[genetix]

Well, seems my skills kinda ran out or well I did build few cmd's and launched them at system reboot, but having hard time keeping them up and they are bad solution as my brains just (at least after 12 hours of installations) just can't think how to do it better.

 

Project Specification:

 

Devices:

* IDE / AHCI /RAID / USB (basically any real hardware that loads at system registry as storage)

 

What would application / driver need to do:

1. Load up right before system shutdown after user action is done to shut down (or alternatively work as a shutdown button).

2. Detect any newly installed driver / service / device from registry keys:

HKLM\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase
HKLM\SYSTEM\CurrentControlSet\services

Ask if 'start' data OR group needs modifications before system is shut down. Drop bar list of Start: 0-4 and full groups list read from:

HKLM\SYSTEM\CurrentControlSet\Control\ServiceGroupOrder
List (REG_MULTI_SZ)

Now this could be developed quite a bit more.. Oflline modifications same application from user selected source registry mounted from other Windows OS and general display of all in order from above 'List' key would be nice on same application (similar to application 'LoadOrd', but with modification possibility).

 

"Offtopic" maybe:

Now, I made cmd which:

1. lists all current entries.

2. caches amount of entries.

3. Matches the list

 

but it is just bad idea I can see it already. Any help on even lowest level Visual Basic would be helpful.

Edited by genetix, 21 August 2013 - 05:43 AM.

[genetix]

Hmm, would like to add that, for this application / driver somekind of configuration file ini or cfg or something would be nice which would at least have few sections like:

 

* User modified hardlock entries (which maybe could be detected by load order. This could be complished by considering first devices in for example "Boot Bus extender"'s as devices which are absolutely needed for booting up).

* And maybe some kind other section simply defining what media is used for booting. RAM/UFD/HDD/Mobile Phone perhaps even including requirements for that kind of booting scenario (which I can help with if needed). Kinda protected section by selected device.

 

Anyway, my explaining the need is kinda weak, if someone actually wants to give this one a shot simply ask direct questions by identifyer like '1.' '2.' '3.' and I will answer back same style.