Jump to content

Virindi

Member
  • Posts

    69
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Virindi

  1. I have added an email address: hflists AT xpcreate . wiretapped . us ... that, perhaps, should be used to send in new updates for hotfix lists. -J
  2. *cough*
  3. Hi, The thing I've found is that: - For microsoft.com website translations, usually the two letter language abbreviation is used (but sometimes three). However, for the actual hotfixes, they use the three letter language code. Ex: http://support.microsoft.com/default.aspx?scid=kb;ger;828741 http://support.microsoft.com/default.aspx?scid=kb;sv;828741 http://support.microsoft.com/default.aspx?scid=kb;fr;828741 - For hotfixes, I have not seen one yet (unless it was multilanguage / language independent) that did not use the three letter code, like: WindowsXP-KB828741-x86-ENU.EXE I think the important thing here is the contents of the PRODSPEC.INI file, which should be easy for someone to send GM (unless of course they don't think it's worth the effort to allow their language to be supported ) hehee. -V
  4. Virindi

    XPCREATE

    In XPCREATE.ini, comment out the DLURL line with a semicolon and then place a blank DLURL= below it, like: ;DLURL=http://xpcreate.wiretapped.us/ DLURL= Then when you'd like to download source again, delete the blank DLURL= line and uncomment the original. -V
  5. Excellent - thank you -J
  6. Hi all, Someone posted a free program that took a "before" snapshot and then an "after" snapshot of the registry - and would output just the changes it detected. I ended up wiping my drive a while back, and can't remember the name of that program. I just want to edit the registry during an unattended install to change the update frequency of SAVCE to daily instead of weekly Any help is appreciated - the board search function returned 30+ pages of results :\ -J
  7. You should probably read the rest of the thread before asking something like that
  8. The download list for Windows 2000 Pro English has been added, although I am not in a position to test it right now. Perhaps someone who actually uses Windows 2000 Pro can see if it works. -J
  9. All download-list languages SHOULD be finished Friday, but no definate promises. I would say Thursday, but it's going to take some time to download all the hotfixes in each language to create MD5 sums -V
  10. I have a question that someone may be able to answer... ok here is the path for english: [removed; figured it out] when it comes to the "detected language version", is there a list of correct abbreviations for each language? [removed; figured it out] Volunteers that could collect download links for patches (in any language besides english), or at least test other languages after the lists are posted this Thursday or Friday, would be nice -J
  11. Fixed; thanks! I have one other idea that I will work on for a bit and then send you a PM about - I'm sure you've thoguht of it already, but it's the logistics that's the killer. hehe.
  12. [edited]: A direct link is not necessary; XPCREATE will find the file by itself. See the post below by GreenMachine. I'm not sure how I'm going to maintain multiple language versions of this, but I am putting some thought into it. Regardless, I'm willing to host the file for general use. For now it is just the English version, but I am in the process of completing all the other languages, and should have them up by Friday.
  13. One thing I noticed last night after playing around with XPlode (v1.0.5; haven't tried the current version yet) is that if you forget to close an XML statement, it has the same generic error... such as: Error opening XML file: C:\XPlode\XPlode.xml Invalid XML syntax. Check UNICODE encoding? Is there a way for the XPlode engine to parse through and make sure all <statement> have a closing </statement> ? I noticed my mistake after about 5 minutes of looking through the (very long) XML file I had made, but anyway.. hehe. Xplode is awesome, btw. Thank you. -J
  14. (One?) new update for today: Download Link Security Update for Windows XP (KB840374) Download size: 854 KB, < 1 minute A security issue has been identified that could allow an attacker to compromise a computer running Windows and gain complete control over it. You can help protect your computer by installing this update from Microsoft. After you install this item, you may have to restart your computer. Read more... ---------- [edit: the second link was indeed an update from Feb 10th, and somehow didn't get slipstreamed into my test cd. Oops].
  15. I'm not sure if that's a valid product key - but if it is, I would suggest removing/replacing it. -J
  16. Thanks for the reply - the extra set of eyes really helped. This worked: C:\>secedit /configure /db secedit.sdb /cfg customxp.inf /quiet >nul Then, I wanted to force the system to apply the new policy immediately (hopefully when cmdlines.txt is read, so way before the user logs in). It turns out they have moved away from secedit and to "gpupdate" to force applying policy: C:\>gpupdate /force Refreshing Policy... User Policy Refresh has completed. Computer Policy Refresh has completed. I didn't want any output text, so I changed it a tiny bit to: C:\>gpupdate /force >nul I'm going to try putting the appropriate commands and paths into cmdlines.txt, to see if this works out. It looks like it will! Thanks again for the reply. -J
  17. Hi all, I'd like to apply a local security policy template, sometime during install. Here's what I've dug up so far: 1) To create a security template, I found instructions here: http://appdeploy.com/tips/detail.asp?id=22 2) After creating and saving said template, I found it in: C:\WINDOWS\security\templates\CustomXP.inf 3) I copied the policy template to \temp, and tried following the instructions to apply the template: http://appdeploy.com/tips/detail.asp?id=23 Here is where I'm running into problems; every time I try to apply the template, it doesn't appear to work - it just pops up with the help menu. c:\> Secedit /configure /db secedit.sdb /cfg"c:\temp\customxp.inf" /silent >nul c:\> Secedit /refreshpolicy machine_policy /enforce /quiet I think if I can get these steps to work, I can maybe put this in cmdlines.txt and have it auto-apply the local security policy template during install. If there is someone out there that is more familiar with policies, I would really appreciate some help with this -J
×
×
  • Create New...