MSFN Forum: integrating Startup monitor as a driver? - MSFN Forum

Jump to content


If you are having issues with Windows after removing components and have come to ask for help, please attach (not paste) your Last Session.ini file to your post to facilitate quicker assistance.
Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

integrating Startup monitor as a driver? Rate Topic: -----

#1 User is offline   KapnJackSparrow 

  • Junior
  • Pip
  • Group: Members
  • Posts: 51
  • Joined: 01-August 12
  • OS:XP Pro x86
  • Country: Country Flag

Posted 24 November 2012 - 12:06 PM

Integrating Start-up monitor as a driver? I am trying to integrate mike lin's start up monitor into the control panel by installing it as a driver but nlite doesn't seem to like it, any idea on how I could do this?

I would also like to have it install the resident monitor as well but one thing at a time.

Attached File(s)


This post has been edited by KapnJackSparrow: 24 November 2012 - 12:07 PM



#2 User is offline   -X- 

  • Member
  • Group: Patrons
  • Posts: 2,046
  • Joined: 08-January 04
  • OS:XP Pro x86
  • Country: Country Flag

Posted 24 November 2012 - 01:38 PM

You cant do it that way.

Use the $OEM$ folders. Place Startup.cpl in $OEM$\$$\System32

#3 User is offline   KapnJackSparrow 

  • Junior
  • Pip
  • Group: Members
  • Posts: 51
  • Joined: 01-August 12
  • OS:XP Pro x86
  • Country: Country Flag

Posted 24 November 2012 - 10:46 PM

my installation is having problems at the moment and doesn't seem to be doing what it should be as referenced in http://www.msfn.org/...tting-settings/ and it is not installing the mlin start up monitor into the control panel. do I need a run once for this? do I need to include the inf I posted earlier as well as the cpl? (tried both neither seems to work)

After reading up on the $OEM$ folders maybe this will solve my problem with my batch file not being able to find the folders it needs during installation as referenced by this post http://www.msfn.org/...ng-a-batchfile/

or eliminate the need the batch-file entirely. the purpose of the batch-file was to copy things such as the windows folder, documents and settings containing desktop.ini files and set the read only bit on the folders by copying a folder that has been set up over top of the existing one. while this works perfectly post install I haven't been able to get it to work during the installation. would simply putting the folders needed into $OEM$\$1 solve this problem? will files placed in that folder overwrite ones that are already on the disk?

or do I need to set up a run once to do this?

This post has been edited by KapnJackSparrow: 24 November 2012 - 10:46 PM


Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

2 User(s) are reading this topic
0 members, 2 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2013 msfn.org
Privacy Policy