Nakatomi2010

I'm assuming to run WPI from CDROM it's simply changing: REM Determine the WPI startup path. REM if wpi should run off the cd the replace %~dp0 with %cdrom%. set wpipath=%~dp0 to REM Determine the WPI startup path. REM if wpi should run off the cd the replace %~dp0 with %cdrom%. set wpipath=%cdrom%\install\wpi1\wpi.cmd (Or wherever it's isntalled...) then in the winnt.sif file I'd put [GUIRunOnce] Command1=%CDROM%\install\wpi1\wpi.cmd Do I need to define %CDROM% in WINNT.SIF, or will it know? Also, on a slightly unrelated note... I've been having a few install problems... When I install Adobe, because it's a .msi Microsoft Antispyware wont install and neither will Java, I'm assuming that they're all being launched in order, but why aren't they installing? I can run WPI afterwards, cancel out everything but those, and they run fine, so the coding is fine... Am I missing something?

Ah, but a lightscribe label is perfectly centered and balanced, no real risk of it flying apart, plus once color lightscribing is posible I'm sure all you'd really need to do is upgrade the firmware on it...

So, I'm getting ready to "finalize" my Multiboot DVD, which basically consists of all versions of Windows XP, and a few utilities... To usher in this DVD I plan on making a lightscribe label for it.... Was wondering if anyone else has made one,and if so what it looked like... Fishin' for a few ideas for when I create mine...

Well, hopefully this utterly and totally simplistic .bat file I made works... I basically put 'copy' infront of everything and '<Directory here> behind everything, changing MOST, but not all, os the last characters to _... I matched it against a BT I got from a previous install.... And the out.txt file I got... VERY simplistic batch file...

Nevermind, I must've typed it wrong the first time...

How do I get the complete listing?

But which files go into which directory? We technically need 2 BT's now.... Don't we, or am I not grasping something...?

ksecdd.sys = 1,,,,,,_6,4,0,0,,1,4 ntdll.dll = 1,,,,,,_7,2,0,0,,1,2 kbdus.dll = 1,,,,,,_7,2,0,0,,1,2 drvmain.sdb = 1,,,,,,_3,60,0,0 kbddv.dll = 1,,,,,,_5,2,0,0,,1,2 kbdes.dll = 1,,,,,,_5,2,0,0,,1,2 kbdgae.dll = 1,,,,,,_5,2,0,0,,1,2 kbdgr1.dll = 1,,,,,,_5,2,0,0,,1,2 kbdit142.dll = 1,,,,,,_5,2,0,0,,1,2 kbdusl.dll = 1,,,,,,_5,2,0,0,,1,2 kbdusr.dll = 1,,,,,,_5,2,0,0,,1,2 kbdusx.dll = 1,,,,,,_5,2,0,0,,1,2 ntfs.sys = 1,,,,,,_6,4,0,0,,1,4 setupreg.hiv = 1,,,,,,_3,,3 spcmdcon.sys = 1,,,,,,_7,,3,3,,1,1 biosinfo.inf = 1,,,,,,_1,20,0,0,,1,1 wkbddv.dll=55,,,,,,_5,82,0,0,kbddv.dll,1,2 wkbdes.dll=55,,,,,,_5,82,0,0,kbdes.dll,1,2 wkbdgae.dll=55,,,,,,_5,82,0,0,kbdgae.dll,1,2 wkbdgr1.dll=55,,,,,,_5,82,0,0,kbdgr1.dll,1,2 wkbdit142.dll=55,,,,,,_5,82,0,0,kbdit142.dll,1,2 wkbdus.dll=55,,,,,,_7,82,0,0,kbdus.dll,1,2 wkbdusl.dll=55,,,,,,_5,82,0,0,kbdusl.dll,1,2 wkbdusr.dll=55,,,,,,_5,82,0,0,kbdusr.dll,1,2 wkbdusx.dll=55,,,,,,_5,82,0,0,kbdusx.dll,1,2 wntdll.dll=55,,,,,,_7,82,0,0,ntdll.dll,1,2 biosinfo.inf = 1,,,,,,_1,20,0,0,,1,1 ntdetect.com = 1,,,,,,_1,1,3,,,1,1 biosinfo.inf = 1,,,,,,_1,20,0,0,,1,1 wkbddv.dll=55,,,,,,_5,82,0,0,kbddv.dll,1,2 wkbdes.dll=55,,,,,,_5,82,0,0,kbdes.dll,1,2 wkbdgae.dll=55,,,,,,_5,82,0,0,kbdgae.dll,1,2 wkbdgr1.dll=55,,,,,,_5,82,0,0,kbdgr1.dll,1,2 wkbdit142.dll=55,,,,,,_5,82,0,0,kbdit142.dll,1,2 wkbdus.dll=55,,,,,,_7,82,0,0,kbdus.dll,1,2 wkbdusl.dll=55,,,,,,_5,82,0,0,kbdusl.dll,1,2 wkbdusr.dll=55,,,,,,_5,82,0,0,kbdusr.dll,1,2 wkbdusx.dll=55,,,,,,_5,82,0,0,kbdusx.dll,1,2 wntdll.dll=55,,,,,,_7,82,0,0,ntdll.dll,1,2 This is the output.... Though it doesn't say which filesgo into which directory...

In case anyone is interested I'm going to say the answer to this is now... I'm thinking there are other files that reference the winntbbu.dll file that prevent you from using another one... I used a second winntbbu.dll and called it winntbub.dll and changed the entry in one of the txtsetup.sif files and got nothing...

Well that hampers my testing skills... Someone just came in and bought the 64-bit computer I've been using to test my s*** on... Now I've got a build a new one, and it wont be an Athlon 64, it'll be a Sempron 64... ****... At least it'll still be 64-bit....

Having the directory structure as... AIO-DVD\MW64 (Wherein all i386 files ae copied) AIO-DVD\PRO64 (Wherein all AMD64 files are copied) and using a setupldr.bin from a Windows Server 2003 STD on my end I got into the setup and as far as formatting, but at that point it said it either couldn't see the drive, or some files were corupted...

Figured as much..... Is there any way to tell which files are ABSOLUTLY necesary for it to work? Because otherwise there needs to be a full I386 and AMD64 directory... Is the BT we'd get this case the AMD64 directory, and we could just use the i386 directory as a place holder? *Bare in mind in the creation of my AIO I use 3 BT's, one for complete unattended, with drivers and software, another for attended with software and drivers, and a fully vanilla attended version.. I'd try to do the same with X64* That being said, say we created XP64 and threw in all of the i386 files into there, we could tell all the boot sectors to look at the same folder, but different AMD64 folders, which are the BT's in this case... Or am I just totally confusing an otherwise simple to grasp subject...

Using the technique you described on the previouis page using your instructions did nothing but a blinking cursor... It's my belief that we technically need 2 BT directories, one to represent i386 and another to represent AMD64...

I'm trying to get x64 edition working using the method listed above...

Alright, I've got Windows Server 2003 on my end, which version do I need, and how can I tell if it's pre-SP1... I've got WS2K3 Standard, Enterprise, Datacenter, both VLM and OEM.... Edit: And Web Release, again both VLM and OEM... Also, how many instances of AMD64 should I be expecting? The setupldr.bin file I have (Which may or may not be pre-sp1) has 27 reference to it...

I know there's an update pack, but I wouldn't mind a site with a list of all the current updates and a link please...

Last time I got that "Press ctrl+alt+del" message was when I had something fowled up in my 32bit install.... I tell you what though.... But everything you guys have discovered into a single post for me to review and second or third thing I do when I get into work tomorrow will be to attempt to get 64-bit to work multi-boot... I meant to awhile back anyways, just got caught up in fine tuning my DVD.... So, please consolidate as much as you can into a single post for me.. Even files I may need... I've got a A64 system I use regularly as a guinea pig, hell I even use RAID drvers..

So I'm making an multi-boot DVD with a few instances of the same version of windows, I was wondering if it's at all possible for me to have multiple billboard screns.. like having a txtsetup.sif file reference winntbbu.dll and then another refernce winntbbu2.dll... Theoretically this would work, but I haven't tried it, and right now I don't have time to, so I figuerd I'd ask see if anyone else has tried....

Does the above mean I need to put the files in the root of the drive, or can I get away with: if $lastKey == key[?]; then isolinux \NTPASS\vmlinuz rw vga=1 init=/linuxrc initrd=/initrd.gz root=/dev/ram0 source=/dev/cdrom/0 ???

It was something I toyed with, I removed it from my AIO because it's not that well used and you're limited to one install options... I had created a test chamber, but since i've not yet fine tuned my AIO-DVD it's been put on the back burner, I just know I did it.... I use DVD-RW's so I've even lost my original.... Hard to do this when you've got only 40GB of work space... I keep alot of clutter around for originals, generics, things like that.... AIO-DVD's are a side project for me....

Nothing got overwritten, so you can leave any like files the same... I used nLite to slim it down and slipstream hotfixes, then whatever was left I copied to the root of the AIO-DVD that you're makin'... I had it trigger an X64.DAT which was the bootsector of the CD... Ran like a charm... Hell, even the two PE's I've got worked...

I tried the others on the thing, worked just fine... Had XP Home, Pro, MCE, Tablet PC... Worked like a charm...

And for CDShell?

http://home.eunet.no/~pnordahl/ntpasswd/ This is a little utility I use to emove the passwords from NT based machines, was wondering how I incorporate it into the DVD using CD Shell and/or Easy CD Boot (Preferrably CDshell for now, but I may change it in future to Easy Boot, right now this NT thing is the only thing left I need before I call my DVD "Version 1", so... It's basically a version of Linux, annd I don't know how to trigger it...

The x64 edition doesn't multi-boot very well because of that AMD64 directory... The CLOSEST thing I was able to do was work around it... As someone else mentioned I basically added Multiboot ability to me x64 CD, I copied the root of the 64-bit CD to the root of the DVD, left all the names intact and boot the XP64.dat bootsector I got from the CD, made the appropriate entries into the CDshell.ini menu system and it worked... It's not the most desirable method, but it works...