Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations


Everything posted by Alanoll

  1. Next time tell us EVERYTHING you did. First you blamed it on nLite, and then on Ryan's pack. After all that, it was a registry tweak YOU FOUND in someone's post.
  2. The forums are to ask questions, not the same question 5 times in new topics because you don't like the responses on the old ones
  3. EVery application in Studio is itself an MSI. Go look for them. FSCOMMAND or something like that is the folder name. As for KEY and Activation, I'm going to assume you have the Volume edition. Install it on your machine, then go to %ALLUSERSPROFILE%\Application Data\Macromedia\Licensing and copy both the Lincensing and Products folders to your Distribution. Then during setup after the Studio is installed, copy those folders back to the same location you got them from.
  4. ARE YOU KIDDING ME?! What about Did you NOT understand? I don't care if you're not getting the "attention" you're expecting. Creating more threads on the same subject just causes people to RUN AWAY! Why don't you NOT use that setting then?
  5. and I can sympathize, but one topic is ENOUGH
  6. I'm counting 1 now. @lennierv ONE TOPIC IS ENOUGH!
  7. Out of curiousity, you think posting screenshots helps? You've been told the problem with it, and nuhi is FULLY aware of this version of windows.
  8. Equivalent but not the same. It's actually a complete rewrite, so in essense it's a new program. Also, ntldr is quite a bit different from Vista's version.
  9. What about IE and Firefox? And yes, I'm aware of what the SeaMonkey is (I added this line using QuickEdit by the way)
  10. Correct me if I'm wrong, but you said he gave you money to build a machine and get it running. That makes him a customer. Consumer is anyone who buys anything, a customer is someone who buys something from someone. He bought a service from you, which makes him a customer, and as such you violated nLite's license.I'm only going to HOPE that you bought him a copy of XP as well, otherwise.... You realize that by using nLite to remove anything, you are infact REMOVING the so called bells and whisles? Not everyone is as tech savvy as you appear to be
  11. I fail to see how this is "personal use". Father's friend or not, he was your customer, and NOT YOU.
  12. and I remember seeing in the license that nLite is only for personal use. Customer is not personal.
  13. Any number of things could have happened... Perhaps there was a power outage at their hosting company. Perhaps they're moving servers Perhaps they're being DDOS'd Perhaps they're just updating their site.
  14. out of curiousity, why is that after only ONE post, you decide to make a request for someone to make some artwork for you? Now, i can maybe understand if you were at DeviantART or something who's main purpose is ART, but asking on a TECHNOLOGY FORUM?!
  15. I've seen once, someone searching for "Setup Billboard Screens".... or just reading and looking at other forums. http://unattended.msfn.org/unattended.xp/view/web/73/ http://www.msfn.org/board/index.php?showforum=92
  16. Alanoll


    Yes, you must rebuild the ISO. And are you really that dependant on nLite that you need it to edit a single text file?
  17. Alanoll


    Copy the contents to your harddrive (the current CD). Open WINNT.SIF found in your I386 folder. Edit as needed. (This is where all those Unattended settings are saved from nLite)
  18. I brought the issue of licenses for the included applications to the author's attention already.
  19. CMDLINES.TXT was probably created if you used any sort of Addons and they used it. Back in the day, it may have been used to run the nLite.inf, but as far as I'm aware, the current version doesn't make use of it at all.
  20. you could also check time stamp of files. It's not as definitive, but say you're a person that nLites but removes the nLite.inf. if when nLite does barely anything, it still atleast opens and writes around 8-9 files that can be found in the folder.
  21. Alanoll

    Unsupported OS

    [SourceDisksFiles] viamraid.sys = 1,,,,,,3_,4,1 [HardwareIdsDatabase] PCI\VEN_1106&DEV_3349 = "viamraid" PCI\VEN_1106&DEV_0591 = "viamraid" PCI\VEN_1106&DEV_3249 = "viamraid" PCI\VEN_1106&DEV_3149 = "viamraid" PCI\VEN_1106&DEV_3164 = "viamraid" [SCSI.load] viamraid = viamraid.sys,4 [SCSI] viamraid = "VIA RAID Combo Driver Diskette" Would be the appropriately lines. Then you MAKECAB the viamraid.sys file to compress it to a .sy_ file and copy it to I386. Edit TXTSETUP.SIF in the I386 folder with the above lines and you should be good
  22. Alanoll

    Unsupported OS

    Find the codes yourself. The TXTSETUP.OEM file included with the drivers is where all those Device IDs come from. Just find each unique one that's for your driver (they're usually split amongst OS [2000,XP,2003]) and add a line to TXTSETUP.SIF for each. Think of the process as more of a pattern. [SourceDisksFiles] Si3112r.sys = 1,,,,,,3_,4,1 Replace Si3112r.sys with the filename of your driver. [SCSI.load] Si3112r_XP = Si3112r.sys, 4 [scsi] Si3112r_XP = "Silicon Image SiI 3x12 SATARaid Controller for Windows XP/Server 2003" Defines a name for the drive and description, as well as tell SETUP to load the driver file. The name can be anything, but needs to be unique from any others. Usually they are because they're based off model numbers and if setup doesn't support your card, then the model isn't there. The Si3112r_XP is where the right side of the equal sign comes from to tell SETUP which driver to use for those device IDs.

  • Create New...