jcarle

Honestly, you don't even need the setupp.ini file as far as I know.

WUD (http://wud.jcarle.com/ http://www.msfn.org/board/index.php?showforum=147) is also regularily updated and can be used with nLite.

The COA and the product key are what determine the legality of your installation, not the media used to install it.

100 milimeters = 10 centimeters = 0.1 meters = 0.01 decameters = 0.001 hectormeters = 0.0001 kilometers. What you probably meant was: 1000 milimeters = 100 centimeters = 10 decimeters = 1 meters = 0.1 decameters = 0.01 hectormeters = 0.001 kilometers.

First off... awesome. Thanks Memnoch. Great work. Which startup is this created in? All Users or the individual user's account? Just curious... wondering if the "restricted" user can just right-click delete the shortcut in the startup account. So in otherwords, send the s*** my way, eh? I wonder what ever happened to the original poster... haven't seen him reply in this thread, which ironically, was the reason for developing the session manager.

I would never entrust my data to Biostar.

I guess in Canada we're spoiled since more then half the population uses high-speed cable modems.

Wow... they actually make that s***?

I have personally never seen a router with a DSL modem built in.

Well, if you create the user account on the local machine, MS FTP should allow you to login without full domain information. Although I don't know enough about Active Directory to know if you can create local accounts as well as those on AD.

Doom 3, F.E.A.R.

It has to remain REG_DWORD. As for Hex conversion: Func toHex($dec) If $dec < 16 Then Return Hex($dec,1) Else Return toHex($dec/16) & toHex(Mod($dec,16)) EndIf EndFunc And from Hex to Decimal: $dec = Dec("49E9AB20")

Every woman's favorite chipmunk?

Let's just wait and see what nmX.Memnoch has brewing. If he's finished his installer or not...

Yes. A good example of that is SP1 vs SP2 in regards to USB 2.0 support and HDAA (High Definition Audio Architecture) support.

Well, in this case HKLM always has precedance... so it's almost the same.

They better sure as hell make sure it's surely slipstreamable!

You need not worry. This is very very small data. The "session log" is a single byte. I'm not storing information in quantities like an application event log or a report or anything huge like that. First, identity is written out as machine_name\username\ always when there is no domain, when there is a domain, you'll know because I don't have a domain to test it on. I've completely reworked the registry handling. Now... it works like this... Read HKLM for settings, if not found, read HKCU, if not found, write out default settings to HKCU and use those. In otherwords, it never writes to HKLM and only to HKCU, however if HKLM settings exists, they will override those of HKCU. HKLM settings are in HKLM\SOFTWARE\SessionManager\(machine_name/domain)\(user)\ HKCU settings are in HKCU\SOFTWARE\SessionManager\ And that should do it. SessionManager.zip

I never use restricted accounts so I didn't know... in that case... I need to change the way the program works because it also creates the session logs in HKLM. I'll rework it so it works around HKCU instead.

Sure. Go nuts. I just lack time to do it all.

I remember IBM's attempt at PCI with MicroChannel Architecture (MCA). Now THAT was something special and rare!

Don't forget your motherboard must be PCI-Express 2.0 as well

All you do is run the attached program at startup during the login of each user. I would suggest putting it in HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run so that they can't just delete the icon. Thanks To simplify the task for you and others who may be interested with this program but aren't comfortable playing with the registry, I've updated the attachment in the post above. The attachment now includes a folder with 5 files: SessionManager.exe - The program executable Install.bat - A batch file to copy the executable to C:\Windows\system32 Remove.bat - A batch file to remove the executable from C:\Windows\system32 Add To Startup.reg - A registry file which you can import to set the session manager to run from the current user Remove From Startup.reg - A registry file which you can import to remove the session manager from the current user Basically, if you throw this on say a USB stick or something, all you need to do after is run Install.bat to copy the program file, login as the user you want to limit, run Add To Startup.reg. Logout and login into any other additional users you want to limit and run Add To Startup.reg again. Don't forget, this is nowhere near hack proof. But it's sufficient to act as an aid when your kids aren't old enough to go through the registry and system files.

To use the UL file, simply place the file in the same directory as the WUD executable, usually C:\Program Files\Windows Updates Downloader\

I wrote a little utility for you... took me about 2 hours. (I was avoiding my real work ) It does exactly what you want and it's very effective. (I got logged out while writing this post because I forgot to turn it off while I was writing this.) All you do is run the attached program at startup during the login of each user. I would suggest putting it in HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run so that they can't just delete the icon. Remember, this program is only effective if the application is actually run. It will automatically keep a session log in the registry of how many times they've logged it. It will also automatically create the default limits of 3 logins per day at 30 mins per session. You need to run the program from a user's account at least once to create the default settings. Once the default settings are created, you can change them for a specific user. Say one of your sisters was grounded, well you could put her LoginsPermitted down to 0. If someone else was allowed longer sessions, say 60 minutes, you could change the SessionLength value to 60. All settings are found in the registry in HKEY_LOCAL_MACHINE\SOFTWARE\SessionManager. At the 2 minute mark, it will beep once. At the 1 minute mark, it will beep 3 times and the timer changes to dark red. At the end of the session, the person will be logged out. No matter what the person is doing. Hope it solves your problem and that it works well for you. I had fun making it. Oh and one last thing. You MUST have .NET 2.0 installed on your machine for this to run. -- file removed (see posts below) --