Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Lamer

  • Rank

Profile Information

  • OS
    none specified
  1. I had tried using the Windows file sharing crap, but it was pretty messed up and I only got it to work once before losing it. It also uses many services I disable. The easiest way I currently have is to just set up an FTP server. FileZilla has a pretty easy to manage one. Just remember to make an exception for it in Windows Firewall. Then all you need is the IP address, make a user name, and set a home folder under the user settings. The other PC uses the IP address and a copy of FileZilla client.
  2. Yeah, uhh, it's telling you what it defragments. You're just applying your own program's stuff to others like it's definitive. By no means? Ok dude, I guess you have convinced yourself beyond reason. You didn't tell me what to do. You simply described my viewpoint as a logical fallacy based on self-delusion. Based on this very limited description, I have concluded that you know very little about how the metadata is placed, how much of it there is, or what kind of effect it has on the system. Basically you are blowing boot-time defragging way out of proportion here.
  3. Point noted, and promptly discarded. You draw an unreasonable conclusion here, and it appears that you don't even know exactly what is getting defragmented or why you would need to defragment those things. Or I guess "occassion" really means "times that could possibly never occur or would only happen in certain situations". Perhaps you have just conviced yourself that the magic of boot-time defragging is more than what reality carries. Hmm, or could it be that your current defragging program just sucks? The world may never know.
  4. A couple typos in the removal section: Network --> "Comtrol" Operating System Option --> Application Compatibility Patch --> "popoup" And why is it reporting that Windows Server 2003 only allows 10 open connections for TCP/IP? The default box value was 16777215. But I don't want nLite to touch the file AT ALL. Last time I ran nLite 1.0.1 it did something funky and I got an error about tcpip.sys during the install, so I put back the original file onto the disc. Looks like I'll be doing the same thing this time just in case.
  5. Diskeeper really turned me off with versions 9 and 10. First the ugly interface, then the extremely confusing menus and options that made it hard to find what you needed and how to use certain features. O&O Defrag is great; has a good interface, and does a good job. It doesn't have a boot option, but maybe it's unnecessary. I need to try out PerfectDisk 8. Version 7 was decent, but didn't seem to defragment as many things as the others.
  6. It just needs documentation.
  7. 1. Nope; stable. 2. As I say, it just stays blank, even if I click around before hitting next and after going back and forth in the steps. 3. Just does. If 1.2 works differently then I guess it's not really an issue. +Whoa, funny thing just occurred. I was going to type a random number into the box but hit H and another unhandled exception popped up. Apparently it doesn't like letters. I can hit continue but it's a little unnerving. // yeah, just waiting for stability
  8. Not sure what you're talking about. I was using Server 2003 and it reported the current number as over 2 million or whatever, but it was going to lower it to the tweak's max of 16-something. I'm guessing it only defaults back to a number it can handle, but not so in this case as it was out of range.
  9. Well shit, it happened again and this time I didn't leave it open for a while. I think I found the problem, though, because I got it to work. I guess when you don't enter any value for the TCP/IP patch (i.e. if you delete the value), then it screws up. But I was using Windows Server 2003 so I don't need to patch it in the first place.
  10. I've gotten this error twice now, and it seems to happen when I leave nLite open for a while at the last step where it asks if you want to start processing (and I then click Yes). I don't know if I should let it continue or not, so I just quit and run the same preset again. "Microsoft .NET Framework Unhandled exception has occured in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immeidately. Inpute string was not in a correct format." See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.FormatException: Input string was not in a correct format. at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) at .'.(Object , EventArgs ) at System.Windows.Forms.Control.OnEnter(EventArgs e) at System.Windows.Forms.Control.NotifyEnter() at System.Windows.Forms.ContainerControl.UpdateFocusedControl() ************** Loaded Assemblies ************** mscorlib Assembly Version: Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/Programs/nLite/v2.0.50727/mscorlib.dll ---------------------------------------- nLite Assembly Version: Win32 Version: CodeBase: file:///C:/Programs/nLite/nLite.exe ---------------------------------------- System Assembly Version: Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/Programs/nLite/System.DLL ---------------------------------------- nLite Assembly Version: Win32 Version: CodeBase: file:///C:/Programs/nLite/nLite.exe ---------------------------------------- System.Windows.Forms Assembly Version: Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/Programs/nLite/System.Windows.Forms.DLL ---------------------------------------- System.Drawing Assembly Version: Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/Programs/nLite/System.Drawing.DLL ---------------------------------------- nlgw Assembly Version: Win32 Version: CodeBase: file:///C:/Programs/nLite/nLite.exe ---------------------------------------- Accessibility Assembly Version: Win32 Version: 2.0.50727.42 (RTM.050727-4200) CodeBase: file:///C:/Programs/nLite/Accessibility.DLL ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
  11. Lamer

    N-Lite Login problem

    Isn't this information in winnt.sif? Well at least part of it is. Here is a tweak from a version of Windows that had a bunch of stuff added to it: useraccounts.cmd net user AccountName /add net localgroup Administrators AccountName /add net accounts /maxpwage:unlimited REGEDIT /S autologon.reg EXITautologon.reg Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "DefaultUserName"="AccountName" "DefaultPassword"="" "AutoAdminLogon"="1" Just alter the 3 AccountName parts and add a pass if you want. Mine has these in a $OEM$ folder, I don't know if putting this line into cmdlines.txt will run it ("useraccounts.cmd"), but if not I guess you could add it to the RunOnce part of nLite or something.
  12. So I see it has some stuff for 2003 SP2 compatibility. I just tried using nLite with SP2 and got a ton of missing file errors I had to esc out of. Will this fix that? And are there any problems it fixes that I should be wary of while using 1.0.1? Note: there is a new "refresh" of the beta; v2786.
  13. I don't get it. If they're so advanced at this stuff (as hinted by their incredulity over not having cleanup cmds), then uhh why not just counter it with another scripted command list to copy the files next?
  14. I saw this problem on a couple computers. I don't know or remember they were the exact same kind of problem but only one of them was nLited and that one was fixed by installing IE7.
  • Create New...