Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi all! We have been experiencing an issue on site where threads have been missing the latest postings. The platform host Vanilla are working on this issue. A workaround that has been used by some is to navigate back a page or two to re-sync the thread and this will then show latest posts. Thanks, Mike.

Registry Scripting Problem

  • 25-09-2005 3:27pm
    #1
    Hosted Moderators Posts: 7,486 ✭✭✭


    At home I have a Windows NT4 - style domain with a unix PDC, and as such i don't have group policy etc.

    I'm using WPAD so that the computers can automatically pick up the proxy settings which works well. There is one laptop which is joined to a domain in TCD, and as such the only way to automate its proxy changes is to change the registry.

    In Windows XP if I create a file like:
    REGEDIT

    [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
    "AutoConfigURL"="http://www.tcd.ie/proxy.cgi"

    it will appear to import correctly and the success message appears. however i don't find the information in the registry has been changed at all.

    If instead the file reads:
    REGEDT32

    [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
    "AutoConfigURL"="http://www.tcd.ie/proxy.cgi"

    it doesn't import at all and complains that it's not a valid script file. Anyone got any ideas?


Comments

  • Registered Users, Registered Users 2 Posts: 2,931 ✭✭✭Ginger


    Is the user you are logged in as an Administrator or the user has access to the registry.


  • Hosted Moderators Posts: 7,486 ✭✭✭Red Alert


    Yeah the user does. Actually, I stumbled upon the answer so i'll post it in case anyone needs it:

    the top line should read
    Windows Registry Editor Version 5.00

    now functions perfectly :)


Advertisement