Jump to content

Pistolero

Member
  • Posts

    37
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Pistolero

  1. I am quite the thespian, I'm told :-P I start with a folder with only my $OEM$ and Applications sub-folders. I then copy both the I386 and the DOTNETFX folders, along with any files in the root of the CD from my clean, freshly downloaded from MS Licensing XP Pro SP2 VLK ISO mounted with Daemon Tools. Once the copy is done, I fire up nLite. Choose my options, addons (I always put RyanVM's files at the very top of the list), Unattended info, patches, tweaks, and then process. I then make my ISO to test with VMWare. Wait, wait, and then watch it fail miserably and shatter my already brittle faith in humanity with only 14 minutes left to get to safety and installed bliss. You should be able to reproduce as most of the addons are freely available on the 'net (except the CyberMacGyver ones... them are mine. And the error still happens without them) Hey, how's that for true drama? I should probably get a job as a soap writer :-)
  2. Sure. Here goes the file. This issue happens all the time with the default engines from 1.2.1 on up to 1.3RC2. The error does not happen when using the alternate mkisofs engine. Also, pretty interestingly enough, the MD5 file hashes are not the same when compared between the default engine-mkisofs ISOs: Default= 1635C5326AACB60A579F2F5E466C7458 mkisofs= F0101DB3195B098A6A1E147871837389 So I guess the txtsetup.sif file itself is not corrupted as I can mount the ISO and read it without a problem, but instead there is an error in the way the default engine handles ISOs bigger than 3.5GB or something... TXTSETUP.rar
  3. Hi Nuhi, I have been experiencing this exact same issue with every 1.3 release to date (please look at screenie for more info). Once this happens, you end up with an empty desktop upon first logon and no apps work at all. It always happens at the same spot. Please note, however, that this same setup (only with RyanVM's 2.15a update as the new 2.16 doesn't work with older nLite versions anymore) works flawlessly when I nLite with version 1.0.1. I hope this helps get this bug squashed once and for all. Also, there appears to be an issue with the built-in ISO creator as it also always gives me the error about the invalid line upon CD boot. mkisofs seems to work fine, however. I am also attaching my Last Session INI file for reference. Thanks a bunch! LAST_SESSION.rar
  4. ISO created with default engine in RC2 fails right out of the box upon boot, as well: Any ideas, Nuhi? Thanks!
  5. Hi Nuhi, I keep getting this annoying and quite fatal error, every single time with every 1.3 version so far: After this, it's game over... Nothing will load upon logon... Windows will look like the apotheosis of all deserts. Any ideas on how to fix this? Also, you may want to look into the ISO building sub-routines... the default engine ALWAYS spits out a corrupted ISO for me (is there a size limit? Mine ends up being 4.18GB) Thanks!
  6. Hi all, Hopefully someone can help me. I need to have US English (default - Code 0409) and Mexican Spanish (secondary - code 080a - I think?) as input languages. Below is the [RegionalSettings] section of my WINNT.SIF file... for some reason, I just cannot get Spanish to be installed along with English: [RegionalSettings] SystemLocale = "0409" UserLocale = "0409" UserLocale_DefaultUser = "0409" InputLocale= "0409,080a" InputLocale_DefaultUser = "0409,080a" What should be the correct way to specify the input languages I want, keeping in mind I want English (United States) with its default keyboard layout as the default and primary input language, and Spanish (Mexico) with its default keyboard layout (Latin American)? Thanks!
  7. Hello given up, Pretty much the only thing you can do at this point is take the tower to a computer shop and have them clean it up and reinstall the OS on it. Preferrably a mom-n-pop outfit so you don't get charged an arm and a leg for the work. Hope this helps! Pistolero.
  8. Try making a new nLite'd CD, but this time DO NOT integrate ANY drivers, other than Mass Storage and Network. See if that helps.
  9. I have succeeded in exporting the reg key responsible for allowing a Media Center 2005 install to join a domain, and I would love to be able to import it to the registry before it becomes read only. Is there a way to do this during Text Mode setup (just like SETUPREG.HIV), or early during GUI mode? Or is there another way to write to this READ ONLY key before it becomes so?: "HKEY_LOCAL_MACHINE\SYSTEM\WPA\MedCtrUpg\IsLegacyMCE" REG_DWORD from 0 to 1 Any help would be greatly appreciated!
  10. Thanks, Nuhi. Also, quick question: I have noticed that even if I edit the WINNT32.SIF file manually aftr nLite is done with its thing, my manual changes don't stick (Setup appears to ignore them)... does nLite instruct Windows setup to look for settings elsewhere? I ask because I wish to keep using 1.2 beta, but I want to be able to add the creds to join a domain manually. Thanks!
  11. This happens even when there is no entry in the WORKGROUP field... I can type in the domain name, but the "Username" and "Password" fields remain inaccessible: Any ideas?
  12. How to specify credentials to add machine to domain if the user name and password fields are grayed out in the Network ID tab? Thanks!
×
×
  • Create New...