Briar

hello all, sorry, im having a problem with the oem distribution folders. i created the unattend.txt and renamed it to winnt.sif and put it into the i386 folder. i created the $oem$ folder and put it at the root of the cd with i386 not in i386. i created a cmdlines.txt and put it into $oem$ folder. cmdlines.txt reads: [COMMANDS] ".\RunOnceEx.CMD" i also put the runonceex.cmd file inside the $oem$ folder and then i edited the winnt.sif file to have the following commands: OemPreinstall = Yes OemFilesPath="..\$OEM$" Application path is $oem$\Apps\ but when i create an iso and run it in vmware, it doesn't install the apps? i dont know what im doing wrong, and any help would be appreciated. thanks for reading and and help you can offer. P.S. happy thanksgiving all! Briar

Hello all, i have been working on building cd using hfslip. A while ago i tested the modified sfcfiles.dl_ which while worked fine, i havnt been using it. The latest cd i built integrated ie6 and the necessary hotfixes mentioned on the hfslip website. I made a bootable cd using nlite and now when i run the cd in vmware it keeps poping up windows saying "the software you are about to install does not contain a microsoft digital signiture". what did i do??? i tried replacing the dll file and burning a new cd but that didn't work. note: i have obviously decided in my head that the sfcfiles.dl_ is responsible for this. i am probably wrong. any sugestions? Grateful as always, Briar

ok

hey buddy, thanks for the knowitall way of replying, i am not a newbie, or whatever you would like to call the people you feel arnt worth replying to. what i was looking for is the source to LOADER.BIN not setupldr.bin. and if you're referring to the setup folder question, you can change it in hex. so, thanks for your reply, but if you cant actuall help , or provide any coments that point me in the direction of what i was looking for .....dont reply. Briar

so if im understanding correctly, if you had the source code to loader.bin you could change the max number of characters accepted and everything should be fine from there right? if so any idea where i can get the source for loader.bin? i went to cdshell's website and downloaded the full source, only i dont know where the source for only loader.bin is. thanks for the reply, Briar

hello all, im working on making a multiboot dvd and im following flyakite's guide, what im not understanding is the **boot.bin files that point to the setup folder and setupldr.bin. what i dont understand is why the setup folder has to be four characters. can it be more? i would just be nice to be able to actually have the ability to understand what is in what folder. thanks briar

Has anyone tried adding the files io.sys, himem.sys, autoexec.bat and the such (files to make a floppy bootable) to the root of your cd and just make autoexec.bat with a custom boot menu your boot loader? Briar

Do anyone know the steps the bootloader takes from boot up (and what makes that able to be a bootable file) to the setupldr.bin for whatever operating system you choose? Has anyone written anything on this? i saw a small explanation on flyakite's site, anyone have anything more indepth? Thanks Briar

What i meant was without other peoples software. Anyone try that? Briar

what if you wanted to make a custom .bin file and link that with a simple batch file that gave you your menu choices? has anyone tried this? thanks.

Ok, im making a multiboot dvd, i have extracted the i386 from all of my origional cds, made an autorun menu, extracted the boot sectors from each of the operating systems and put them on the root folder. The problem i am having is the file that enables the cd to boot up. Which file is this, where do i get it, and how do i edit it. i am following flyakite's guide, i checked unattended.msfn and tech-hints and i cant seem to understand. any help? Thanks in advance. Briar