kof94

I come in peace (I thought I'd better write that first since it seams quite heated around here). I actually like your installer. It's quick and easy to use, exactly what I need for my multi-boot disc to start the Windows upgrade installers. I have two requests though. 1. Would it be possable to add an option to change the title text to fit with what ever purpose the disc was for. Obviously you would want to keep the copywrite bit or even add to it since you made the installer. 2. Work on creating a way of copying..........wait for it........... five digit codes ...........in to five boxes............ can you see were I'm going with this?!! Either that or anyway other way you can make it easier to input serials with out pen and paper, since I'm just gonna add them to the display area on the installer for now. I know the second request is probably gonna be a ball ache so if you can't do it, it doesn't matter. I'm still gonna use this installer cos I like it. Keep up the good work.

Has anyone got this working from the cd image using the"Recovery Manager" folder. I've tried and tried to get this working including using LiquidSage's guide but still no joy. EDIT: Don't worry, sussed it. Jotnar's method is the only way I've got this to work.

Thanks alot for that, I'll test it out today and get back with a result. EDIT: How do I make a working .ima large enough to include all the disks. Not been having much luck with UltraISO. I keep getting errors.

Wait 5-10 minutes after install completes before restarting your machine you'll notice the 'D' folder slowing gets cleaned away. You just need to be patient! If you reboot before this process has finished the folder will stay and probably all the .inf's in your WINDOWS/INF folder aswell.

Yeah, sorry forgot post a complete resolve to this. It has nothing to do with Bashrat's DP's at all. The problem resides in your winnt.sif. Have a look at this thread, It's easier than me typing it all over again. Local Admin logon Error If you want me to elabourate on everthing I did, including OOBEINFO.INI drop me a post here. I'll re-subscribe this thread to email so I remember to reply. I'll probably post a reply at the above thread, since this is no longer DP orientated. Hope this helps.

Hi ya'll, I've been searching around trying to find how to add DOS 6.22 to my multi-boot. There's quite abit on this dotted around but nothing really definitive and above all simple when it comes to installation. I was wondering is there a way of auto swapping disks on the dvd i.e. when it asks for the next disc you just hit enter and it carries on loading. I know the diskemu module in cdshell will support two discs at once but I can't figure out how this works or weather this will help at all. Especially since it's three disks and then the sup disc. The only other way I could see of doing it is combining/editing the disks into one .img and just memdisking it but I'm definitely lost on that one. If anyones done this and wants to share the info or if you've got any ideas/suggestions I'd greatly appreciate it. Thanks in advance.

In pro I found that it worked fine aswell, it's just in home I had trouble so I'm assuming that ocp1000 must be using home. What are you using RayOk? I used the same source you used as a ref aswell but added some tweaks of my own and instead of putting it in the OEM folders I cabbed it and added it to the i386 folder (works better). Still can't get the auto update page to bog off though, using winnt.sif or oobeinfo.ini, any ideas?... apart from hacking the page apart that is.

I've been working on this for a week or so now on XP Home SP2. The problem I had was you can't logon as local admin in home with out being in safe mode. So as you can imagine this caused me alot of problems when the unattended install tried to logon at the end of the install. Your problem is in Winnt.sif, remove this value: AdminPassword = * (or any password you've set) this is under [GuiUnattended]. If you read the info in ref.chm in Support/Tools/DEPLOY.CAB on your XP disc you will find that if you set this value to * the installer will try to logon once as local admin. If you set a password then it will always logon as local admin. In this case you need to set a AutoLogonCount = 1 under the same heading if you only wish to log on once. As a bit of extra advice I've not set any admin name or computer name and I've also set my unattended mode to ReadOnly. This way the only stuff you have to set during install is the user info. I would, however, imagine that you could get away with just removing the AdminPassword value and setting ReadOnly (if you set FullUnattended this all falls over) as the UnattendedMode and still filling in your user info. Just as abit more info. If you then wish to get rid of all the "welcome to windows" rubbish and have all that stuff unattended as well, have a look at oobeinfo.ini. It works quite well and is less damaging than the OOBE removal included in nLite. I would go into this but I've probably given you more info than what you wanted anyway. If you do want to know more I'll keep an eye on this thread for afew days and I'll elaborate if needed. Anyway, hope all this helps and good luck.

Delete Me Please!

I know, I did just that, works fine now. I was Just answering my own post really, I wasn't trying to be sarcastic or anything. Since I started somthing different I thought I'd better finish it, just incase someone was lookin for the same prob. Found more info on my logon prob though maybe not directly related.... see this: Logon Error After Unattended Install It talks about XP SP1 but hay it's a start at an explanation besides when has Microsoft ever got it completly right?!! Anyway as a final note on this post I've fixed both probs now, I think, so I'll stop putting this post to the top of the pile and let everyone else air there probs :-) Thanks all.

Ok I know this isn't related to my original prob that is now solved but if anyone read my last post I'd just like to point them to the following post as my new problem has nothing to do with the driver packs. Just if anyone wondered! framedyn.dll missing after driverpacks slip

Ok, here we go! I've downloaded a complete new set of driverpacks and the new Base 5.11.8. I made an unattended source (added winnt.sif and nothing else) and slipped the driverpacks and installed it on my test hdd. No logon problem, it's gone. Yippeee However, I decided to test Bashrat's theory about the admin password. So I made two identical installs, the first with and the second without a password. First one went fine but the second time I got a message saying framedyn.dll needed reinstalling followed by an error box about srclient.dll. I know I've read a post about this problem but I can't find it again so I'm sorry to raise this again but if you could someone point me in the right direction I'd greatly appreciate it. Just to recap: *I can't see what I've done different apart from the admin password. *I have used a fresh source of XP Home SP2 with winnt.sif added for unattended install. *I am using all the new driverapacks (well as of 23.30 GMT yesterday) and Base 5.11.8. *I am using M2, GUIRunOnce and KtD (N) Hope thats enough. Oh and should I make a new post for this since my probs changed, I am new to this so I don't know. Cheers all.

5.11.3 and 5.11.6 are definatly the only two versions of Base I've used. I've tried doing this in a variety of ways including setting up an unattended install without nlite or RyanVM updates, still does it. However if I don't use the driverpacks and do any of the above, no problems. I read a post this morning, somewhere in the forum, that explained that if you remove certain services using nlite it can have adverse effects. This would make sence, since I now just disable the messenger service instead of removing it completly. At the same time though, I decided to use RyanVM's Integrator instead of nlite for the addons. So I don't know which one sorted it but the extended install time went away. I was still using the old version of Base at this point and didn't have my logon prob then. I'll try setting an admin password and see what happens. But I don't think it will sort it since you can't logon as local Admin' (unless your in Safe Mode) in XP Home. This probably why I don't get the same problem with Pro aswell. Anyway thanks for all your suggestions, I do appreciate it. I'll hopfully get back tomorrow with a result. Cheers.

Anyone out there....?

"unable to log you on account restriction" If your using home and try to log on as local admin thats what you get in a warning box and thats exactly what I'm getting and the end of my unattended install when I have bts driverpacks integrated with Base 5.11.6. Just to clarify, it happens at just the time when you expect command prompt to pop-up and start integrating the drivers at neer the end of the windows installation process. And remember, this didn't happen in version 5.11.3 (apart from a three hour install time but that doesn't happen any more).

Anyone else want to have ago at this I'm really stuck here?

I think your first answer could be right. I get a screen with classic logon and "adminstrator" as user name and somthing to the effect of "logon violation..." in a warning box. It then drops back to the welcome screen and my default "User" logon. I am assuming its the driver packs trying to install and failing because I havn't seen this before and the only thing I've changed is the Base and the driverpacks. And, of course, it happens just when the command promt (GuiRunOnce) screen would usually appear. Oh, and the driverpacks don't install exept for the mass storage textmode setup, if I didn't say before sorry.

This is the first time I've ever used a forum so I'm sorry if I get any thing wrong. I've only recently got into unattended installs and I havn't really hit any walls til now. I've been adding all the driverpacks to XP Home (yes I know XP Home) using Base 5.11.3. I've had no problems with this version using Method 2, GuiRunOnce and either KtD set to yes or no. Since the release of Base version 5.11.6 I've had an administator logon error when it comes to intergrating the driverpacks at the end of XP's Install. I've read as much as I can on this forum but noone else seams to have posted this problem. I haven't changed any thing else about my install exept the driverpack versions and Base 5.11.6 and I've stuck to the same process of: RyanVM updates/addons->nlite->Driverpacks. I know XP Home will not let you login as administrator unless your in safe mode and I know that the temp directory for Base 5.11.6 is different to 5.11.3, could that be the problem? I don't want to start picking apart the integrator mainly because when it comes to code I'm a novice and I could come even more unstuck if I don't know what the problem is for sure and I'm not pointed in roughly the right direction Just to clarify this is the versions of driver packs I'm now using: Chipset V5111 CPU V506 Graphics A V511 Graphics B V5111 LAN V511 Mass Storage V510 Sound A + B V511 WLAN V511 Sorry I've been an id*** and deleted the ones I was previously using so I can't post them. I hope this is enough info and thanks for your time. ------------ SOLUTION ------------ post #17