S
Sturm
Is there a way to create a DVD .ISO from a run time image? hd2iso has
options for 74 and 80 min. CDs only.
options for 74 and 80 min. CDs only.
K
KM
Sturm,
Did you read this thread:
http://groups-beta.google.com/group...934c4899f4e/61c03cd67f2ff1a6#61c03cd67f2ff1a6
Did you read this thread:
http://groups-beta.google.com/group...934c4899f4e/61c03cd67f2ff1a6#61c03cd67f2ff1a6
S
Slobodan Brcin \(eMVP\)
Konstantin,
Have you noticed google behaving strangely and not showing root of threads
by default?
I have been geting these quite offten recently.
Check this link and link that you gave and you will see what I'm talking
about.
http://groups-beta.google.com/group...e9cd63d679b/4bb9658425996274#4bb9658425996274
Regards,
Slobodan
Have you noticed google behaving strangely and not showing root of threads
by default?
I have been geting these quite offten recently.
Check this link and link that you gave and you will see what I'm talking
about.
http://groups-beta.google.com/group...e9cd63d679b/4bb9658425996274#4bb9658425996274
Regards,
Slobodan
S
Slobodan Brcin \(eMVP\)
Konstantin,
Have you noticed google behaving strangely and not showing root of threads
by default?
I have been geting these quite offten recently.
Check this link and link that you gave and you will see what I'm talking
about.
http://groups-beta.google.com/group...e9cd63d679b/4bb9658425996274#4bb9658425996274
Regards,
Slobodan
Have you noticed google behaving strangely and not showing root of threads
by default?
I have been geting these quite offten recently.
Check this link and link that you gave and you will see what I'm talking
about.
http://groups-beta.google.com/group...e9cd63d679b/4bb9658425996274#4bb9658425996274
Regards,
Slobodan
K
KM
Slobodan,
Yes, I see the difference. But this is almost my fault.
Google archive has always been broking some threads in parts (don't know the reason but perhaps thread size is the issue) so that
you have a link to each part. The parts are hieratical and inclusive. Meaning that if you are looking at the part #N, you will see
the links to all parts #N+1, #N+2, etc., but not vice versa
I happened to capture the second part of that thread and therefore you couldn't see the first part.
I can only say I am glad you are watching
Yes, I see the difference. But this is almost my fault.
Google archive has always been broking some threads in parts (don't know the reason but perhaps thread size is the issue) so that
you have a link to each part. The parts are hieratical and inclusive. Meaning that if you are looking at the part #N, you will see
the links to all parts #N+1, #N+2, etc., but not vice versa
I happened to capture the second part of that thread and therefore you couldn't see the first part.
I can only say I am glad you are watching
L
Leonid
I have the run time image that answers on all my requirements. Now I want to
make bootable DVD from it.
- The C:\ partition is NTFS formatted.
- Registry RAM EWF is implemented.
- %TEMP% and page file are located on unprotected D:\ partition
Questions:
- Is it possible to use NTFS to create bootable DVD or I must convert it to
FAT16?
- How to implement eltorito component into run-time image without
rebuilding?
- How to imlement virtual (memory) drive component and assign D:\ to it
without rebuilding?
- Do I need to set pagefile to size=0?
- What else I have missed to complete the task?
Thanks
\Leonid
make bootable DVD from it.
- The C:\ partition is NTFS formatted.
- Registry RAM EWF is implemented.
- %TEMP% and page file are located on unprotected D:\ partition
Questions:
- Is it possible to use NTFS to create bootable DVD or I must convert it to
FAT16?
- How to implement eltorito component into run-time image without
rebuilding?
- How to imlement virtual (memory) drive component and assign D:\ to it
without rebuilding?
- Do I need to set pagefile to size=0?
- What else I have missed to complete the task?
Thanks
\Leonid
the reason but perhaps thread size is the issue) so thatKM said:
Meaning that if you are looking at the part #N, you will see
S
Slobodan Brcin \(eMVP\)
Leonid,
Technically there is no reason to prevent NTFS from working on El-torito.
Only question is if you have right tools to make it work. If you have
problems I would start by using FAT in the beginning.
Very hard. You will need to use regedit on offline hives and to add all
entries that are used by El-torito components and all components that you
might be missing and that El-torito depends on.
Then you will need to start XPe from HDD with dummy El-torito CD in. as in
doc. If you can access El-torito data content then you are ready to go and
deal with EWF and other stuff.
Download ramdisk sample driver from MS and install in on running XPe.
Regards,
Slobodan
Technically there is no reason to prevent NTFS from working on El-torito.
Only question is if you have right tools to make it work. If you have
problems I would start by using FAT in the beginning.
Very hard. You will need to use regedit on offline hives and to add all
entries that are used by El-torito components and all components that you
might be missing and that El-torito depends on.
Then you will need to start XPe from HDD with dummy El-torito CD in. as in
doc. If you can access El-torito data content then you are ready to go and
deal with EWF and other stuff.
Download ramdisk sample driver from MS and install in on running XPe.
Yes.
Regards,
Slobodan
L
Leonid
Thanks, Slobodan
What does it mean "have right tools to make it work"? Some more info if
possible, please.
I have an experience with El-Torito XPe in the past. I did the similar
project for test purpose last year, but with regular FAT16 and 650MB. It did
work.
Is it possible to trace it in TD by building the dummy project and by
switching off "autoresolve dependances"?
\Leonid
What does it mean "have right tools to make it work"? Some more info if
possible, please.
I have an experience with El-Torito XPe in the past. I did the similar
project for test purpose last year, but with regular FAT16 and 650MB. It did
work.
Is it possible to trace it in TD by building the dummy project and by
switching off "autoresolve dependances"?
\Leonid
S
Slobodan Brcin \(eMVP\)
Leonid,
I did not used NTFS on CD. But I know that El-torito specification do not
care about FAT, NTFS or any other FS so there are no techincal problems for
this to work.
I do not know if hd2iso or Nero are capable of using NTFS for creating
bootable content, you will have to try and figure out this yourself.
I did not used NTFS on CD. But I know that El-torito specification do not
care about FAT, NTFS or any other FS so there are no techincal problems for
this to work.
I do not know if hd2iso or Nero are capable of using NTFS for creating
bootable content, you will have to try and figure out this yourself.
L
Lucvdv
I'm using MKISOFS. It allows creation of large ISO files, and these work
fine when burned to DVD with Nero.
See http://www.nu2.nu/bootcd/
I actually discovered it at http://www.nu2.nu/pebuilder/, and found out
that if it doesn't fit on a CD anymore, just burn it to a DVD and it works
just as good.
S
Slobodan Brcin \(eMVP\)
Lucvdv,
Are you sure that you actually made "Windows XP Embedded" to boot from CD by
using this tool and link that you gave us?
Could you please give us few basic steps that you did to make it work?
Regards,
Slobodan
Are you sure that you actually made "Windows XP Embedded" to boot from CD by
using this tool and link that you gave us?
Could you please give us few basic steps that you did to make it work?
Regards,
Slobodan
L
Lucvdv
No, I never tried with XP Embedded, just standard bootable CD's.
S
Slobodan Brcin \(eMVP\)
I'm using MKISOFS. It allows creation of large ISO files, and these
This approach can't work with XPe. But you can use only Nero without any
other tools to make XPe bootable DVD.
Regards,
Slobodan
This approach can't work with XPe. But you can use only Nero without any
other tools to make XPe bootable DVD.
Regards,
Slobodan
M
Matt Kellner \(MS\)
Actually, HD2ISO doesn't care what file system is in use on the partition it
converts to ISO, and technically I don't think any other ISO tools should
care about this either. We've successfully tested NTFS in El Torito
configurations, but we recommend you use FAT32 instead for a couple of
reasons:
(1) NTFS has a lot of low-level security stuff going on that involves
frequent writes to the volume, to update security descriptors, last-accessed
dates, etc., and this can eat up your EWF overlay fairly quickly. FAT
doesn't do all of this - it usually only writes to the file system whenever
any actual file updates are performed, such as writing to the registry,
saving a file within a program, writing a log, etc. Even when perfectly
idle, an NTFS system occasionally writes to the hard drive, so this is not a
good solution for El Torito unless you don't mind occasionally rebooting the
system to clear the overlay.
(2) FAT32 is more widely supported by various tools and provides for simpler
overall operation and potentially a smaller image footprint. NTFS is
generally only recommended in Embedded systems if you need to take advantage
of its advanced security features, such as being able to set specific user
permissions to folders and files, sharing folders on a network, etc.
FAT32 will most likely work better for you than FAT16, as it supports larger
partition sizes and automatically supports using NTLDR. (FAT16 requires you
to run BOOTPREP before you can boot an XPe system.)
--
Matt Kellner ([email protected])
STE, Windows Embedded Group
This posting is provided "AS IS" with no warranties, and confers no rights.
===============================
converts to ISO, and technically I don't think any other ISO tools should
care about this either. We've successfully tested NTFS in El Torito
configurations, but we recommend you use FAT32 instead for a couple of
reasons:
(1) NTFS has a lot of low-level security stuff going on that involves
frequent writes to the volume, to update security descriptors, last-accessed
dates, etc., and this can eat up your EWF overlay fairly quickly. FAT
doesn't do all of this - it usually only writes to the file system whenever
any actual file updates are performed, such as writing to the registry,
saving a file within a program, writing a log, etc. Even when perfectly
idle, an NTFS system occasionally writes to the hard drive, so this is not a
good solution for El Torito unless you don't mind occasionally rebooting the
system to clear the overlay.
(2) FAT32 is more widely supported by various tools and provides for simpler
overall operation and potentially a smaller image footprint. NTFS is
generally only recommended in Embedded systems if you need to take advantage
of its advanced security features, such as being able to set specific user
permissions to folders and files, sharing folders on a network, etc.
FAT32 will most likely work better for you than FAT16, as it supports larger
partition sizes and automatically supports using NTLDR. (FAT16 requires you
to run BOOTPREP before you can boot an XPe system.)
--
Matt Kellner ([email protected])
STE, Windows Embedded Group
This posting is provided "AS IS" with no warranties, and confers no rights.
===============================
M
Matt Kellner \(MS\)
To clarify: A "standard bootable CD" usually uses the "Floppy type" El
Torito standard, which more systems support. This standard basically fools
the computer into thinking your CD is a floppy-style boot device, and it'll
work fine if you want to make a bootable CD that does the same thing as a
Win98 Boot Floppy. It's also the ET style that WinPE uses.
However, booting a full OS image requires the "Hard-disk type" El Torito
standard, which makes the system think the CD is a non-removeable hard
drive. This standard isn't as widely supported among system BIOSes, and it
requires different preparation steps than the Floppy type. If the tool you
mentioned can only support "standard bootable CDs", it's most likely
designed for the Floppy type ET standard, and will not work with XPe.
--
Matt Kellner ([email protected])
STE, Windows Embedded Group
This posting is provided "AS IS" with no warranties, and confers no rights.
===============================
Torito standard, which more systems support. This standard basically fools
the computer into thinking your CD is a floppy-style boot device, and it'll
work fine if you want to make a bootable CD that does the same thing as a
Win98 Boot Floppy. It's also the ET style that WinPE uses.
However, booting a full OS image requires the "Hard-disk type" El Torito
standard, which makes the system think the CD is a non-removeable hard
drive. This standard isn't as widely supported among system BIOSes, and it
requires different preparation steps than the Floppy type. If the tool you
mentioned can only support "standard bootable CDs", it's most likely
designed for the Floppy type ET standard, and will not work with XPe.
--
Matt Kellner ([email protected])
STE, Windows Embedded Group
This posting is provided "AS IS" with no warranties, and confers no rights.
===============================
S
Slobodan Brcin \(eMVP\)
Matt,
If it do not tamper with partition table and just do raw sector copy then I
must agree. Although I have no idea what is the use of all those options
then in hd2iso?
FAT12<4085 Clusters<=FAT16<65525 Clusters<=FAT32
Depending on selected cluster size and partition space you can estimate
cluster count. This is directly related to filesystem type used by format
operation.
You can't make 8 MB FAT32 but you could easily make 256+ MB FAT16 image.
Regards,
Slobodan
If it do not tamper with partition table and just do raw sector copy then I
must agree. Although I have no idea what is the use of all those options
then in hd2iso?
FAT12<4085 Clusters<=FAT16<65525 Clusters<=FAT32
Depending on selected cluster size and partition space you can estimate
cluster count. This is directly related to filesystem type used by format
operation.
You can't make 8 MB FAT32 but you could easily make 256+ MB FAT16 image.
Regards,
Slobodan