• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Falcon4

  • Rank
    teh Fighting Falcon™
  • Birthday 09/16/1976

Contact Methods

  • Website URL
  1. That is extremely weird! Yeah, I'm out of ideas... If I come up with anything else, I'll post... but in the meantime, I hope someone else knows what's up!
  2. Woa, dude, attach next time =) There's your problem area right there. All of these are selected to be integrated. Didn't you notice these when you went to the Drivers screen? =\ edit: Wait a minute, that doesn't make sense either. You did integrate those, yet International is still in there for the nVidia drivers... Do you completely delete the folder between uses?
  3. That's very strange! Thanks for the screenshots, they do help. It looks like nLite is integrating all the folders for any INF files that were chosen... a standard practice, but taken a bit far. It also looks like a lot more drivers were integrated... Mind posting your last_session.ini file for this build?
  4. Dude, TreeSize will give you all the information you need. Expand the branches until you find the problem area. Before running nLite check the size of your source folder as well! I don't think it's a bug in nLite so much as not knowing what you're putting in the folder to start... please, use TreeSize and figure out the problem... I don't have that problem with my nLites so... not much more I can do to help! What's the largest folder TreeSize comes up with in the structure?
  5. *rewinds* Yeep! *squeek toy* Ding! Oooh, well, that puts things in a completely different perspective. Tweaks still aren't that hot but the components and patches are. I'll have a look around and evaluate yourself as a novice user as soon as I... well... wake up.
  6. First huge note: your TCP/IP patch is set way too high! Way!! Too high! Holy crap! 20 or 30 is OK. 16 million? Let's see who crashes first... Looks like you pretty much completely misused nLite and created a "bastard Windows". Something so jumbled and unusable... you're not typing it on there now, are you? =\ Word to the wise... nLite is not a user-friendly tool. It's very capable of creating very, very unusable, unreasonable setups if you simply check all the options you see. You didn't remove any components and you applied pretty much all the tweaks that had a checkbox. Most of those tweaks are for specialized applications, like me, who used nLite to create a streamlined, stripped server version of Windows XP Pro. They would do no good for a day-to-day system. When you run nLite, clear your schedule. DO NOT rush it. You can NOT undo changes later, you have to start all over if you messed something up. Look at each option, each checkbox, understand what it means, and decide if you want to use it or not. It's not like a program where it puts the checkboxes there "just to show what it can do", but to give you the chance to choose what you really want. Of extremely notable interest are these tweaks I singled out, which are probably responsible for a majority of any problems you may be experiencing... not all related to your network but to your user-experience as a whole. IMO these "tweaks" should be all either marked as "Advanced" or completely removed. Boot and Shutdown-Auto-End tasks immediately Boot and Shutdown-Auto-Kill hung applications immediately Boot and Shutdown-Auto-Kill hung services immediately File Open/Save Dialog-Disable File MRU-List File Open/Save Dialog-Preset Places Bar to: C: D: E: DESKTOP LAN File Open/Save Dialog-Remove Back Button Network-Set TCP/IP Priority to 1 Privacy-Disable Last accessed Timestamp on files Privacy-Disable Tracking of most used programs Security-Ctrl-Alt-Del is required at Classic Logon Security-Disable Windows Script Host (WSH) Take a look at that last line. Disable Windows Script Host? So many driver installations rely on that component - as far as I know- that it's no surprise things aren't working at all. The two "Privacy" entries really have nothing to do with privacy and just prevent you from using Windows XP to its full potential. They have no performance impact. The file open/save tweaks are also a huge step backward in UI innovation, IMO. And the three boot/shutdown options listed will cause you to lose data on a regular basis. I do have to give you an attaboy for not checking "Disable balloon popups". So basically, start with another copy of Windows, and a clean slate, and this time, integrate Boooggy's WUZero Update Pack (I think you can search that here), remove some components (reading and thinking about each one), apply patches in moderation (I use 20 or 30 for my patch, Enabled theme patch, Disabled SFC), and apply tweaks in moderation as well. Know what each does, and what the consequences of each are, before using it. Good luck on your next build - and if you do have any questions about a step of the nLitening process, please don't hesitate to ask!
  7. Did you place the original driver files in the root of your CD, for example? Where were the files located when you included them? I don't know exactly how nLite traces the folder tree, but it could be looping back on itself... Also, try running TreeSize Free over the final nLite folder and see what's eating up the space!
  8. Good disclaimer, bad tweaker advice though... but I do agree none the less. If you don't know what you're doing or why it would/wouldn't work, and are worried about your data, don't screw with it. It's not possible to blow out a controller or motherboard by doing this, but you VERY WELL CAN accidentally slip a pin on the power connector (as I've done several times) and very likely blow out your hard drive by crossing the positive and negative across the two negative pins. Molex is a really shoddy standard IMO... djnando: Strange, the switches are supposed to set the drive active and everything... it may be that the drive geometry or controller setup of your source computer may not match the destination computer... in which case you might want to try Googling around (or asking around... anyone?) for a way to get around this limitation. Usually the symptoms of this are a corrupted screen and a whole lockup (reading from the wrong sector)... not just "operating system not found". Try booting your main computer from that destination drive, and see if it comes up with the same problem. You may also try removing your main hard drive, "faking" a Setup from the original Windows CD onto the destination drive to set it up exactly how it wants it, then after file-copying is complete in textmode, put your main hard drive back in and booting it, then reformatting the destination drive and trying it again. It should work this time - if it doesn't, it's DEFINITELY a geometry/controller mismatch between the computers. CptMurphy: Actually this method is designed for systems that are stuck between a "rock and a hard place". If you have no CD drives for that computer but you can pull the drive out and use it elsewhere (e.g. ghetto setups, or systems with odd specs). I don't know about "hot swappable" hard drives... what I was referring to was me, personally, being able to insert and remove my destination drive countless times while figuring out and building this guide. I do not mean to - and never did - tell people to remove their drive while the computer was running. Hope I didn't confuse too many people with that short phrase... if it did, I'll take it out. edit: Eyy, boooggy!! Nice to see you reading my guide! I used your update pack (as usual)! LOL! Nice work
  9. -X-: Oh, hell, of course it's not supported! This whole method isn't supported, nLite isn't supported, nothing's supported... we're the rebels. If it works, great... if not, don't complain! B) Also, the drive I was working with was a 5v laptop hard drive into a laptop... those are pretty cool about the power thing. 95% of the problems with hot-plugging IDE are from the power drop caused by plugging the new hard drive in, which knocks the other drive(s) out for a split second, just long enough to reset the bus and make the drives unusable until a reboot. IMO this should be easy enough to work around at the driver level, but MS doesn't support this. Simple solution is to plug into a non-critical power cable (one with CD drives on it, for example) and hope for the best. djnando: What's your setup? After you ran winnt32 with the switches, what did you get? I got a message about not being able to upgrade this version of Windows, chose New Installation, entered my CD-key, left the rest of the options default, then it proceeded to "Copying installation files" and closed. Be sure you entered the right drive letter, the drive you chose is the active and primary partiiton on the drive, and that the drive is properly formatted. Usually "Operating system not found" occurs when you have the wrong drive selected, or it's not properly formatted.
  10. Install a drive: Plug it in, hit "Scan for hardware changes" in Device Manager. Drive is found and installed. Remove a drive: Remove the drive from Device Manager, and provided you didn't get a "restart your computer" dialog, it's safe to unplug. Isn't that hotplugging?
  11. Yeah, preformat as NTFS. Or you can use FAT32 but that kinda defeats the purpose. I'm not sure if it'll work the same way with Win2K's winnt32.exe, but it's always worth a shot... I think I copied those switches from the Win2K switches page, so it should work. It won't work with WinNT though, since that was a 100% DOS-mode installation with NTFS conversion anyway. It might also make USB drives boot... maybe!
  12. *deep sigh* That was a huge fiasco. Merging nLite's files with what winnt32 created? Disaster! Here is, finally, after countless failures and changes (thank god for IDE hotplugging in WinXP), how to make Windows Setup boot - just like it boots from the CD - from the hard drive itself. Prerequisites: - "Manual Install and Upgrade" kept - A hard drive. Period. No CD or floppy needed (as the system I was doing this on had no CD, floppy, network, or USB-boot). Start by completing your nLitened version. This method works 100% with your nLitened versions - but Unattended is slightly broken in the textmode portion. It still comes up with "Welcome to Setup" and a few other screens. During setup under FullUnattended, it still asks for date/time, which was unexpected but I don't know if that's normal or not. Once you have your nLitened version ready, pre-format your destination drive (obviously can't be your main drive, C). Run this command (from Run) - where {nLite} is your nLited output folder, {drive} is like D, F, M, etc... whatever drive letter your destination drive is: {nLite}\i386\winnt32.exe /syspart:{drive} /tempdrive:{drive} /noreboot Fill it out with your details, whatever... not completely necessary since you'll be editing that file in a minute, but it's the only way to satisfy Setup to get to the next step. Setup will copy your source nLite files to special folders on the destination drive, write the boot sector to the drive, set it active, and otherwise bootable. In somewhat technical theory, the drive's ready to roll. But if you stop here, your drive will install as drive D:, F:, M:, or whatever it was when you set it up! Nobody likes a F:\Windows. So continue on to fix this irritating oversight of Microsoft's and integrate parts of your nLite Unattended setup! Open {drive}\$WIN_NT$.~BT\WINNT.SIF Open {nLite}\i386\WINNT.SIF In the drive's WINNT.SIF file will be several fewer lines than the nLite folder's file. Merge the two together by comparing sections. Add the sections that aren't there and take lines from sections that match and put them into the drive's file. Example: {nLite} [section] this=that cool=yes ultra="mega lolness!" falcon4=awesome [anothersection] extreme="true" {drive} [section] cool=yes OriTyp="3" EulaComplete="1" winntupgrade="no" win9xupgrade="no" Final drive file: {drive} [section] cool=yes OriTyp="3" EulaComplete="1" winntupgrade="no" win9xupgrade="no" this=that ultra="mega lolness!" falcon4=awesome [anothersection] extreme="true" Note that I tool the original {drive} file and added the contents of the {nLite} file without duplicating them. IMPORTANT!!! Now, find the line OriSrc in the {drive} file. It will currently match the original location you copied the files from - your nLite folder. This will not work in the new system! Change it to be "C:\$WIN_NT$.~LS\", exactly. Unless you're certain your resulting drive letter will be something other than C, which we're working to avoid here. Once your OriSrc line is like so: OriSrc="C:\$WIN_NT$.~LS\" Save the Drive's WINNT.SIF file and close it. Delete the {drive}$WIN_NT$.~BT\MIGRATE.INF file. It contains data that will set your drive letter to the old letter (what you did above is the workaround for the problem that doing this produces). Remove the drive, boot it up, and you're... *taco bell pose* Good to go! Enjoy!
  13. C:\Users\Falcon>tinyget -t -srv:xpero.msfn.org -uri:/screenshots/setupwelcome.jp g bLoadSecurity WWWConnect::Connect("xpero.msfn.org","80") IP = "" source port: 1790 REQUEST: ************** GET /screenshots/setupwelcome.jpg HTTP/1.1 Host: xpero.msfn.org Accept: */* RESPONSE: ************** HTTP/1.1 200 OK Date: Sun, 20 Aug 2006 09:28:14 GMT Server: Apache Last-Modified: Tue, 06 Sep 2005 19:08:24 GMT ETag: "450c44-c31a-431de928" Accept-Ranges: bytes Content-Length: 49946 Connection: close Content-Type: image/vnd.wap.wbmp If you want to force download, use application/x-force-download (IIRC)... but that content-type is totally wrong. Always makes Firefox download the image then show it, which is really a pain in the a**... Just fyi.
  14. Awesome!! I'm gonna try that now, and hope it'll cope with the broken header. Also primarily hoping it'll be able to cope with the fact that I'd be booted from a LiveCD on a read-only file system... which may be a bit of a stretch if it doesn't load the driver from the media. It'll be fun. Thanks!! ed: I'm booted from a Ubuntu LiveCD right now since only Linux has proper drivers for my WLAN card... stupid Intel can't make drivers for their own crap, what's up with that?
  15. I decided to give Linux another try. 2 days, got sick of it already. XGL was nice but the bugs are just too much. Microsoft has NOTHING on Linux's bugs. Incredible. Before installing Linux I used UBCD4Win to cd-boot my computer and used DiskTools ImageMaker (an ancient program, it seems) to create an image of my 20gb NTFS Windows drive onto a 40gb NTFS USB drive. It's one whole file and is actually extremely accurate, except the first 32kb, which seem to be corrupted by the ego-boosted program that put some DiskTools info in the header. So when ImageMaker finally went to restore the drive, I was left with a partition-less disk with junk data. I've tried restoring the first 32kb from a working configuration (started installing Windows, let it partition the drive like I had it, saved those 32kb, restored the drive again, restored the 32kb) and it still didn't work. Let me tell you how pleased I am with this program. In Linux I was able to mount that image as a logical partition if I skipped the first 32kb. But there is no such thing for Windows, to just "create" a virtual device out of thin air. I've decided I could do the "half installation" then just copy the data back as files from the image (using the CD, of course). But where do I get that software, that makes the virtual drive from an image? Basically I need something that's like Alcohol or Daemon, except that it makes hard drives, not CD drives. There should be such a thing... but what's it called?