berrick

Thanks for the reply, A real shame! is it still possible to get hold of a copy of Xpcreate?

Hi everyone, I too would like to know what has happened to GreenMachine and if it is still possible to download XpCreate. So if any peepz can help please PM me. Thanks in advance

thnxs for the replies, I have found my silly mistake Just to round up for those that may be looking for answers..... 1st i wouldn't recommend using this just put your logon script in the "%allusersprofile%\Start Menu\Programs\Startup" folder Points to remeber when setting up logon scripts for local users you can use any directory you like really but need to share it as netlogon this directory is read only - so bare in mind when writing script, this was my mistake Case closed, problem solved many thanks

thnxs for the reply but as i stated these are stand alone not on network. used by multiple users

Hi all, Hoping someone can assist I have some stand alone XP pro pc's that i want to run scripts at logon, however my first thought, using the logon script part of the users profile properties wont work. I know i can use mmc to load local policy etc and do it that way, and it works, but it should also work as i describe in the first part of this thread, the fact its not is bugging me now that i have to find out what i'm doing wrong. One error i did get was to state that the path i used was not relative!! Using . or %systemdrive% then the rest of the path cure's this error but the script still dont run. Any ideas???

DOnt matter have sorted problem. Me and my puter arent on good terms at the moment Spot the problem $OEM$ $0EM$

Simple question really, can you use cmdlines.txt to run runonceex.cmd etc when creating AUCD? many thnxz

[url="http://unattended.msfn.org/intermediate/drivers/raid.htm"]http://unattended.msfn.org/intermediate/drivers/raid.htm[/url] this method mainly or setup a network share then this method works. Bare in mind most modern mobo's will boot from sata drive just like if using IDE. You only need the raid drivers loaded if you using a raid level on drives your booting from

set this optoin in win.sif to "no" UnattendedInstall="Yes" it should then allow the use of the F6 key and allow everything else to function as per your unattended cd according to the winnt.sif file

Are they domain users with no local profile? if so you could temp add them to the local admin group via a script then remove after the install, you can also use (the mostly forgotten) RUNAS command from a batch file as part of the install the only problem with RUNAS is that you would need to use a third party app to pass the the admin password to RUNAS

Since my last post in this topic i have tried unsuccesfully to create another uacd using this method..... (M$ make me a fibber again!!). I tried everything still no go, so i checked M$ web site and found this interesting article [url="http://support.microsoft.com/default.aspx?scid=kb;en-us;234536"]"You cannot perform an unattended installation of mass storage drivers when you run the Setup program from the Windows CD"[/url]. This would certianly confirm why the method described here seems so hit n miss when used from CD. The only succesful repeatable method I have found from UACD is the txtsetup.sif method.

not sure about the touchpad driver issue but in the unattended cd guide there is a download section where you can find a little util to change video settings

**DOH** having bad day just to clear up a few points raised in this post... from experience $OEM$\TEXTMODE\ Is the only place you need to add the files for installation from a CD *.cat files are for WHQL [b]dsik1[/b] refers to a "tagfile" not a directory and is required to identify the correct diskette is inserted when ask for by setup. For correctness it should be included on the CD but will work if not. Under the [MassStorageDrivers] heading in the winnt.sif file you have to include "IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL" else you will get a BSOD at some point after first reboot. The other enteries MUST match those take from the TXTsetup.oem file. The backslah at the end of this line is important d1 = "NVIDIA RAID DRIVER (SCSI)",\disk1,\ this is why Directory = \ Directory on the diskette where the installation files are located. The directory must be specified as a full path from the root and must not specify a drive. This must be a period if you have partitioned or formatted your hard drive with (FAT) or FAT32 file system and you initiate setup with Winnt.exe from DOS or a backslash If you have partitioned or formatted your hard drive with the NTFS and you initiate Windows Setup with Winnt32.exe (like with an uacd), You will get an error if you get it wrong! Error message illegal or missing file type specified in [Files.scsi.yourhardware] is as a result of a known issue - see [url="http://support.microsoft.com/kb/275334/"]KB275334[/url] [quote]Okay you need to open up your txtsetup.oem file (notepad or any text editor will do) and change any reference to "DLL = " to "INF = " (thanks to rcordorica for figuring this out). For some reason textsetup chokes on these entries. These entries should be easy to find and replace in the file. Save the modified file and close it. Again if you don't have any "DLL = " references in your txtsetup.oem then you don't need to change anything and you read this entire section of the guide for nothing[/quote] distibution folders refer to the directory structure used to carry out unattended CD installs or installs from a network share. The structure is identical apart from one important fact, on a uacd the distribution folders are not under the i386 dirctory but are on a network share. I hope this does not come over wrong but am in a rush Any how did a complete guide to the txtsetup.oem and what each bit means etc if any1 is interested i will post it, as you can install other drivers this way! I even think another member has an extensive post on how to do it hope this is helpful

I skimmed through your post and the only issue i can think of that could have a bearing on your problem is that windows XP prior to SP1a wouldnt support HD with capacities larger then 140Gb. Though this normally results in the op sys only seeing the 1st 140Gb of your larger disks Suggest you slipstream SP!a or SP2 hope it helps

DOH! DOH! just a quick update..... raid was enabled in bios but you have to F10 and add drives to raid. This cured the "install source not available" error. Unfortunately I still cant boot from uacd with drivers on cd as still get "txtsetup.oem caused unsupported error (18) at line 1747". Dont get any problems if i use std cd and press f6 Any one got any ideas...... Bâshrat the Sneaky ?

Interesting, I get the same problem with a GigaByte mobo! and i have tried everything i can think of to correct this situation and cant. I'm trying to install the drivers during txt part of unattended install using the M$ way which i have done before, i even get the same problem if i take the diskette with the drivers on (the drivers supposidly for this very task) and try to update the driver from the op sys. I can get the driver installed if i use the fancy front end that came with the mobo but that is no good for this project. Ahhhh.... i hear you cry just use this front end with the silent install switch! I tried; and.... it fails. The installshield setup works without switches but if switches are supplied either fails to run or skips vital options! At one point i thought i had cracked it as i got the install to error with "serivce installation section of inf invalid" which was due to a .sys file not being copied to the drivers directory but since then i only get the "installation source is not available" message. Surely it would be no skin of the manufactures nose to supply all the drivers so those that want to integrate them can do easily as well as package them for joe pubic (yes i did say pubic) If some one has the definitive answer to this i would be very grateful or other suggestions. Would using winistall le be of use (never tried this package before) or is there other ways to reverse the installshield configs?

Hi; Hope some can point out whats wrong. Im trying to add the drivers as part of the txtsetup, i have read various posts and info from other sources but still cant get it to work. I always get an error "textsetup.oem caused an unexpected error (18) at line ......." I cant see an error in the txtsetup.oem file and all file are (as far as what i read tell me) in the relevant directories. i have listed the txtsetup.oem below, any pointers much appreciated ; ; [section] ; key = value1,value2,... ; ; ; The hash ('#') or semicolon (';') introduces a comment. ; Strings with embedded spaces, commas, or hashes should be double-quoted ; ; This section lists all disks in the disk set. ; ; <description> is a descriptive name for a disk, used when ; prompting for the disk ; <tagfile> is a file whose presence allows setup to recognize ; that the disk is inserted. ; <directory> is where the files are located on the disk. ; [Disks] d1 = "NVIDIA RAID DRIVER (SCSI)",\disk1,\ ; This section lists the default selection for each 'required' ; hardware component. If a line is not present for a component, ; the default defaults to the first item in the [<component_name>] ; section (see below). ; ; <component_name> is one of computer, display, keyboard, mouse, scsi ; <id> is a unique <within the component> string to be associated ; with an option. [Defaults] scsi = RAIDCLASS ; This section lists the options available for a particular component. ; ; <id> is the unique string for the option ; <description> is a text string, presented to the user in a menu ; <key_name> gives the name of the key to be created for the component in ; HKEY_LOCAL_MACHINE\ControlSet001\Services [scsi] RAIDCLASS = "NVIDIA RAID CLASS DRIVER (required)" BUSDRV = "NVIDIA nForce Storage Controller (required)" ; This section lists the files that should be copied if the user ; selects a particular component option. ; ; <file_type> is one of driver, port, class, dll, hal, inf, or detect. ; See below. ; <source_disk> identifies where the file is to be copied from, and must ; match en entry in the [Disks] section. ; <filename> is the name of the file. This will be appended to the ; directory specified for the disk in the [Disks] section to form the ; full path of the file on the disk. ; <driverkey> this is the name that will show under the services\driver key ; this should be the same name as the driver that is being installed. [Files.scsi.RAIDCLASS] driver = d1,nvraid.sys,RAIDCLASS inf = d1,nvraid.inf dll = d1,nvraidco.dll catalog = d1,nvata.cat [Files.scsi.BUSDRV] driver = d1,nvatabus.sys,BUSDRV inf = d1,nvraid.inf dll = d1,idecoi.dll catalog = d1,nvata.cat ; This section specifies values to be set in the registry for ; particular component options. Required values in the services\xxx ; key are created automatically -- use this section to specify additional ; keys to be created in services\xxx and values in services\xxx and ; services\xxx\yyy. ; ; This section must be filled out for storage controllers that ; are PNP adapters like PCI and ISA PNP adapters. Failure to do this ; can cause the driver to fail to load. Must also add the section ; [HardwareIds.scsi.ID] to identify the supported ID's. ; ; <value_name> specifies the value to be set within the key ; <value_type> is a string like REG_DWORD. See below. ; <value> specifies the actual value; its format depends on <value_type> ; [Config.RAIDCLASS] [Config.BUSDRV] ; A HardwareIds.scsi.Service section specifies the hardware IDs of ; the devices that a particular mass-storage driver supports. ; ; [HardwareIds.scsi.Service] ; id = "deviceID","service" ; ; HardwareIds.scsi.Service ; Service specifies the service to be installed. ; ; <deviceId > Specifies the device ID for a mass-storage device. ; <service > Specifies the service to be installed for the device. ;The following example excerpt shows a HardwareIds.scsi.Service section for a disk device: ; [HardwareIds.scsi.RAIDCLASS] id = "GenNvRaidDisk","nvraid" id = "*_NVRAIDBUS","nvraid" id = "*NVRAIDBUS","nvraid" [HardwareIds.scsi.BUSDRV] id = "PCI\VEN_10DE&DEV_008E", "nvatabus" id = "PCI\VEN_10DE&DEV_0085", "nvatabus" id = "PCI\VEN_10DE&DEV_00D5", "nvatabus" id = "PCI\VEN_10DE&DEV_00EE", "nvatabus" id = "PCI\VEN_10DE&DEV_00E3", "nvatabus" id = "PCI\VEN_10DE&DEV_00E5", "nvatabus" id = "PCI\VEN_10DE&DEV_0035", "nvatabus" id = "PCI\VEN_10DE&DEV_0036", "nvatabus" id = "PCI\VEN_10DE&DEV_003E", "nvatabus" id = "PCI\VEN_10DE&DEV_0053", "nvatabus" id = "PCI\VEN_10DE&DEV_0054", "nvatabus" id = "PCI\VEN_10DE&DEV_0055", "nvatabus"

Thats what policies are registry tweaks that can be controlled centrally via AD So why not apply these settings with a logon gpo?

This is the more technically correct way to move the My Docs folder as it will move everything to do with a users my documents including the more important stuff like the "local settings" folder which contains the application data (outlook *.pst files). I know you can move the mydocs folder and path for the default location of *.pst files but that has to be done per user from my experience (pls correct if i'm wrong) and is specific only to those folders. Also by default new users on those PC's will have their folders created in the M$ default path ie "c:\documents and settings" not the non standard (your chosen) path!

As i said earlier I'm sure it is possible to use the built in IP filtering to setup ipsec which can be controled via gpo..... BUT i havent tried it and not sure how difficult it would be to do/administor

Hmmmm! well when i was looking into this a lot of info pointed to this issue being a known problem that M$ are looking into. Some other things that may help are: problems with the tcp/ip stack problems with ipsec - one suggestion here was to goto the ipsec services change something then click ok and the problem should be sorted. Another was to Disable the Network Location Awareness Service I cant vouche for any of the above as I knew our version of APC power chute was 6.2.2 and decided it was easier to boot to safe mode and un-install it first before trying the above. Thankfully in our case this was the solution. Hope this might help DOH! i also remeber reading that KB893066 caused the same issue but if memory serves i only read about it effecting XP but worth a try

It is possible that you could have DNS issues that effect certian computers only an easy quick way to rule DNS out is to use another DNS server in the tcp/ip settings (use the dns of your isp or router if it supports it) or another way modify the hosts file on the computer in question with the url and ip of the site(s) your have problem with and see if that works.

well the ping request and the fact you get an echo reply will prove you have a physical path to the IP your pinging. I guess a tracert to prove the path these icmp requests are taking. Are you using M$ vpn or some other client? There is definately no form of firewalling active when this is happening i have been caught out in the past when unknown to me some personel f/w s/w had been installed, i could ping everything but that was it

noobie question.... why would you want to do this??

i have had wierd issues with 2k3 servers. One we could not access shares on a drive in the server even thought the permissons where correct - turning the indexing service on then back on sorted that ??? also had issues with 4 or 5 clients where everything appeared ok they could browse the internet ping each other but when you tried to attach to say the IP$ shares again gave a wierd message about permissions. Further investigation we found that all these computers hadnt jioned the domain corectly removing them then adding them corrected the problem in every case. Not sure if any of this helps as your prob only happens every 2-3 weeks.