Hi all


I made one with nLite and slipstreaming SP2 for Win2003 with addon and hotfixes and driver
I copied the files in the I386 folder, autorun.inf, setup.exe, WIN5I, WIN5IA, WIN51IA.SP2,
Boot.bin, Bootfont.bin in the folder with Grub4Dos.

I created iso with mkisofs and Grub4Dos.
When with VM launch the installation, get a message that the file Amdide.sys is missing.
I added a remark to all lines in the file txtsetup.sif for Amdide.sys
I rebuilt iso, but it is another error disappeared and installation fault. Arc.sys file missing and
install can not continue.
I added a remark in the file txtsetup.sif for arc.sys, recreates iso file, it appears a
another error, the file hpisss.sys is missing.
Remark all entries that refer this file in txtsetup.sif, rebuilding iso and, install now is okay.
Works.


With the ISO created with nLite there are no such problems.

You know why?

Thank

Regards

Setupldr.bin search file AMDIDE.SYS, case is importand.

What can I do to solve the problem?

Thanks

Regards

If you get a answer, confirm the idea first.
Does ISO image contain file name Amdide.sys or AMDIDE.SYS?

And write more details.

Which file name do you read from hard disk?

Which 'mkisofs -version' do you use?
Which command line do you use?

Which grub4dos menu.lst do you use?

Why do you ask at multibooting systems section?
Do you like to add more boot parts?

Yes

??


mkisofs 2.01 (i686-pc-cygwin)

mkisofs -v -iso-level 4 -l -D -d -J -joliet-long -R -volid "GRLDR" -A GRLDR/MKISOFS -b grldr -no-emul-boot -boot-load-size 4 -allow-multidot -hide boot.catalog -o myiso.iso D:\myiso

title 01.->[WINDOWS]
find --set-root/I386/SETUPLDR.BIN
chainloader /I386/SETUPLDR.BIN


grub4dos 0.4.4


what forum should I ask?
iso creating with grub4dos, the project is multidvd boot Windows/Linux

Regards

Which amdide.* file name does exist at CD? Name the name.

??
Ask a question, write a whole sentence.
Open command prompt, change directory to I386 directory at hard disk, runOpen names.txt.
Which amdide.* file name do you read?

Uppercase windows I386 files at hard disk. Use FileCase.exe.
http://www.stevemiller.net/apps/


Historic version, does work.

Yes, it's nice to get a overview. File system is based on multiboot dvd project.

Overall I won't use Joliet.
And not rock ridge with permissions. This dosn't make sense at a windows build environment.

the folder I386 is present and name is I386

the file amdide.sy_ is present in the folder I386

as tips for mkisofs command line?


Thanks

Regards

Setupldr.bin dosn't find this file.
Yes, uppercase selected files.


Which file name length do you require at ISO9660?

-iso-level 4: up to 207 chars
Use previous given command line, but add -force-uppercase with another mkisofs release.
E.g. http://www.paraglidernc.com/links/links.htm

-iso-level 3: up to 31 chars
Use at any mkisofs version

What problems can make use ISO Level 4?

mkisofs using this: http://www.student.tugraz.at/thomas.plank/...3-win32-bin.zip


Regards

ISO level 4 maps to ISO9660:1999. There are allowed lower case names.
A old DOS driver won't find files.
Mentioned version dosn't support -force-uppercase.

Again, at a multi boot DVD solution (different OS may require different conditions):
first uppercase required files at hard disk
next create a ISO image