China DOS Union

My system is XP. I want to use a script to create an.ini file to implement the function of automatically executing the script at startup in Group Policy. But the text of the.ini file written by echo something >1.ini has all become garbled due to different encoding mechanisms. While first using echo something >1.txt and then renaming it to 1.ini, the text is the same when opened. And after placing it in C:\WINDOWS\system32\GroupPolicy\Machine\Scripts, I can see the file I added in the Group Policy Editor, but the system does not execute it.
How should I solve this? Please ask all the experts for guidance.

[ Last edited by willsort on 2006-6-14 at 16:54 ]

In my previous tests (xp sp1), simply adding an ini file cannot achieve the purpose of starting up at boot. Generally, modifying the registry directly works much better for this kind of self-startup method.

Windows Registry Editor Version 5.00





"Script"="C:\\Documents and Settings\\Administrator\\Desktop\\myscript.bat"

"Parameters"=""

After adding the startup here, not only can't it be viewed with msconfig, but even wmic startup can't find its trace. My previous method was using Gpresult /v | findstr "Name" |findstr /v "Site" | findstr /v "Domain" (the test environment was sp1 at that time, and the method of using two findstrs was quite funny). In fact, as long as you check whether there are Startup or shutdown under scripts in the registry, you can know whether there are scripts that start up at boot or run at shutdown.

Thanks, moderator. I'll test it when I have time. :)
I really don't know how many methods for self-startup I still don't know, heh heh

3742668:
Is it effective in WIN2000? There is no State under [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\! What should I do?