thammerling

wow... our lenovo rep is a spaz... and i'm not much better. I hate the **** machines. turns out it wasn't a m52 at all, but an m55e, they shipped us the wrong machine and because these lenovo's have such screwy model naming conventions i had no clue it wasn't an m52. oh well, we had an older image for the m55e, so i just used that and washed my hands of it (we only have _1_ m52 in our district... i'm not wasting my time on this anymore specially because we switched vendors to dell). thanks for your help

bump... still have this issue (i forgot about it, because i just stashed the computer in a closet... but now ppl are asking about it again *lol*) anyone? bueler bueler?

Base HAL is ACPI I have no clue if it has the TPM security chip, how would i find that out? processor is a core 2 duo The drive is SATA. Thanks again for any help you can give, T

Alrighty, I have a sysprep image which works on many many many different models of PCs. from a p3 650Mhz machine to a brand spanking new dell amd 64 bit system. It will install and run on 9 different models so far. the problem is with some IBM lenovo computers. When i lay the image down on one of these Lenovo's (they happen to be IBM M52's) the image is put on properly, and upon restart I get the windows "splash screen" that is shown just before mini-setup starts, and then the computer reboots before going into mini-setup. and it will just keep looping like that. I'm kind of baffled, because this image has worked very well on so many different machines. any help is greatly appreciated. Taylor

It would appear that mini-setup was deleting the autologon key. I had to merge a reg file with the autologon key in it back into the registry using runonce (this will run during mini-setup... i can't get cmdlines to work for the life of me. ) T

ok, I have tested these settings out on a machine that had already been imaged, and I got it working. However, once i changed the registry in the image, and pushed the image out to a machine it did not work. I then compared the settings in the registry on the newly imaged machine to what should have been there, and found that the AutoAdminLogon in the winlogon key was missing. I think this has something to do with the fact that this image is a sysprep image. I think somewhere in mini-setup the AutoAdminLogon is being removed... not 100% sure on that, but i think. I'll keep this thread updated with my progress. T

I'm not 100% sure. I've been a windows guy for the past 6 years, and am just getting into novell, so please bear with me. I would like the computer to autologin as if the "workstation only" box was checked using the local administrator account. I believe that this is the same as "Auto login to NT and disable login to NDS", but I don't want to disable login to NDS permanently, just for the first autologin. another side note, we don't have an active directory domain at all, I would be authenticating against the local box. I will read the documentation (although i'm pretty sure it is what I have already tried... I must just be doing something wrong...) Taylor

First let me start off by giving you all a little background on what my situation is. I am working on making a sysprepped Master Image for my employer. The computers are all XP sp2, and are using the Novell Client for Windows 4.91 SP2. It is working 99.99%, the only problem being I cannot get Autologin to work at all. I would like the computer to autologin as the LOCAL administrator. I have tried many many many different things, and have had no success at all any help would be greatly appreciated. Taylor

hrm... I have that deploy cab, and when i look in ref.chm I find this To run Cmdlines.txt during Mini-Setup In the distribution folder, create: %SYSTEMDRIVE%\Sysprep\i386\$OEM$ Copy Cmdlines.txt to the %SYSTEMDRIVE%\Sysprep\i386\$OEM$ folder. In Sysprep.inf, add: [unattended] InstallFilesPath = C:\Sysprep\i386 Run Sysprep. Either way, I have tried it with the cmdlines.txt in both $oem$'s and at the root of the sysprep folder, and none have worked. I'm stumped! I found this how-to, and it seems like i'm doing everything right... i'm boggled! http://www.geocities.com/kilian0072002/sysprep/sysprep.html

bugger, my bad, i'm a tad slow. I am in fact using xp Sp2. BJ, can you link to the documentation for xp sp2 commandlines.txt? (seeing as how i'm a spaz and read the documentation for 2k) T

http://support.microsoft.com/kb/238955 that is one of the pieces of documentation I have read.

can you please post a link to that documentation? I have always read it has to be in the $oem$ folder

I put my cmdlines.txt and my DriverInstall.bat in BOTH of the $oem$ folders.

Starting from scratch and making sure the cmdlines.txt was in there didn't help a scootch Still hoping someone can save me T

a quick update, while I am waiting to hear back from the ppl of this forum, i'm starting from scratch so that i have my cmdlines.txt in place when i reseal the box... T