oscdimg

  • Thread starter Thread starter Dietmar
  • Start date Start date
D

Dietmar

Hi Slobodan,
what do You think about

oscdimg.exe -h -n -bc:\boot.bin c:\winxp\ c:\winxp.iso

hihi, seems to work

Dietmar
 
what do You think about
oscdimg.exe -h -n -bc:\boot.bin c:\winxp\ c:\winxp.iso

hihi, seems to work
Click to expand...

I'm not sure what do you expect me to say?
Of course that it works it is meant to work.

Regards,
Slobodan
 
Hi all,
for large bootable images with NOEMULATION in ELTORITO specification You
must use the switch -m too.

oscdimg.exe -h -m -n -bc:\boot.bin c:\winxp\ c:\winxp.iso

Dietmar

PS: Burning DVD with XPPRO image, will see.
 
Hi Slobodan,
I receive the message NTLDR (booting from DVD with NOEMULATION build with
oscdimg) not found.
Does this mean, that the ARCpath isnt found?
I set in boot.ini on BOOTDVD with NOEMULATION

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional" /fastdetect
This seems to be wrong or, because
for example:
Booting WinPE from CD than Winobj shows me no arcpath, but it starts on
commandline with H:\ and in registry there is SystemBootDevice Reg_SZ
multi(0)disk(0)cdrom(159) which belongs to \device\CdRom0 where the
WinPE BOOTCD is in.

My Question is now: The ntldr may be also the wrong one, because he
isnt(?) able to read on CDFS. You told me, that You have one which can do
this.
Would be in that case also the message "NTLDR not found" arrive? Another
problem is the arcpath.
Do You know why there stands cdrom(159) ???
Any idea what I must do to overcome this problems? Does the ntldr which
can read from CDFS
needs a boot.ini?
I think, that XPE and(?)can than boot from Cd (DVD) with NOEMULATION and
EWF enabled.

Dietmar

PS: Can I use the ntldr from WinPe,which needs no boot.ini when I set
,folder
i386 instead of Windows, but than I have also to change ntoskernel.exe and
so on or?
 
Dietmar,

I though that by now you know what is loaded and how, including who load the
loader.
bios load bootsector (2048 bytes) from CD
bootsector load ntldr. (it should be differently named on CD boot).
ntldr load boot.ini
ntldr load ntdetect.com
ntldr load registry hives.
ntldr load al drivers and files specified in registry that need to be loaded
by ntldr.
ntldr start kernel.
kernel initializes drivers
drivers load enum and load other drivers.

Regards,
Slobodan
 
Hi Slobodan,
thanks for this answer.
But why is NTLDR not loaded? WHERE looks the Bios for NTLDR when loaded
those 2048 bytes?
You said, that you have 2048 byte which work together with an special
NTLDR which can read from CD filesystem. Without that I dont know where is
my error, and what to do next.
I have VMware, with witch I can test on an virtuell CD device, whitch
bootsector with whitch ntldr works for CD BOOT with no emulation. But I
havnt enough time for that. Is there a reason, that you dont say to me
where I can get those 2048 bytes and the ntdlr belonging to that
bootsector whitch can read on CDFS?
I am thinking that all will work, if I can get them.

Dietmar
 
Hi all,
I found my error.
NTLDR is searched as \i386\setupldr.bin where it isnt is. So a little
mistake, but now I am nearly ready. Seems, I must help myself.

Dietmar
 
Dietmar,

Can you dump us here content of following command: ">oscdimg.exe /?"
I really have no idea what you are talking about :-(

What is -m switch I do not have it?
What is boot.bin file that you provide?
But why is NTLDR not loaded? WHERE looks the Bios for NTLDR when loaded
those 2048 bytes?
You said, that you have 2048 byte which work together with an special
NTLDR which can read from CD filesystem. Without that I dont know where is
my error, and what to do next.
Click to expand...

"Special ntldr." is already on your WinPE CD and is called "setupldr.bin"
I have VMware, with witch I can test on an virtuell CD device, whitch
bootsector with whitch ntldr works for CD BOOT with no emulation. But I
havnt enough time for that.
Click to expand...
Is there a reason, that you dont say to me
where I can get those 2048 bytes and the ntdlr belonging to that
bootsector whitch can read on CDFS?
Click to expand...

Reason is very simple you started this thread by saying us that you know how
to use oscdimg and that it work.
Second thing is that this program has nothing to do with focus of this
particular News Group.
WinPE is supported probably in some other setup related NG.
Beside that you have an some terible help that came with OPK. But it is
enough to do make bootable CD.

Regards,
Slobodan
 
Hi Slobodan,
the -m key overcomes the limitation, that oscdimg can only write
discimages < 700MB.
It is an undocumented funktion and is also not shown in my help.
I just wrote a *.iso file with nearly 2 GB. All oscdimg.exe, that I have
(about 10 ) are identic whitch I tested with hexeditor.
As boot.bin I extracted the bootsector from the WinPE CD. This works, but
there is a problem to me to rename all the files and folders. Does the
ntldr from WinPe work with ntoskernel? Or is it with this ntldr only able
to boot with /minint key in boot.ini? Looks this ntldr in boot.ini or
overrides it? When this ntldr not works with ntoskernel but only with
NTKRNLMP.EXE(or is it only another name like setupldr.bin)do You know
another whitch can also read CDFS?
There are a lot of questions but now I am shure:
I will suceed booting with NOEMULATION to something...hihi. But I have so
little time left.

Dietmar

PS: oscdimg makes something with BOOTCD I dont understand that all the
other Burning programs can not do. This statement is from Microsoft. So I
think it is the right program to do this.
 
NTKRNLMP.EXE (or is it only another name like setupldr.bin) it is original
name for one of few different kernels available.

You have ACPI and non ACPI kernels.
Multiprocessor and single processor kernels.
XPe just rename these files from original name to ntoskrnl during the
build.


You can find this file in XPe repositories.

Regards,
Slobodan
 
Hi Slobodan,
I installed VMwareBeta5R3, and now I can work nearly professional.

I have 2 questions:
Do You know an external Registry Viewer, with which You can make CHANGES
in that Registry from outside?

And the second: There is no external Registry with name "System" in WinPe.
If You run WinPe and type regedit there appears a registry nearly the same
as in XP(E). But where is it stored?

Thanks
Dietmar
 
Dietmar,

1. You can use regedit.exe Load Hive/Unload hive options for accessing
offline registry.
2. It is probably called setupreg.hiv

Regards,
Slobodan
 
Hi Slobodan,
on WinPe bootable virtuell CD.iso I changed carefully ALL setupldr.bin to
ntldr looking that after all remain at the right place on CD, ALL i386
with backslash(es) to minint with backslash(es), all with hexeditor and I
controlled the results that all take right place. I installed a boot.ini
in root with

[boot loader]
timeout=30
default=multi(0)disk(0)cdrom(159)
[operating systems]
multi(0)disk(0)disk(0)cdrom(159)="Microsoft Windows XP Professional"
/fastdetect /minint
(this root cdrom(159) is from realbootcd with winobj)

and copied ntldr and ntdetect.com to the root.
When I boot this *.iso virtuell CD in VMware I get the message "Cannot
boot from CD-code:5" .
The ntldr is correct detected.
Any idea what this could mean?

Thanks
Dietmar
 
Dietmar,

You have entered the waters uncharted by me.

I have no clue why do you get this error. Also can you tell us again what do
you try to accomplish and why?

One more question have you determined for sure that your boot.ini is loaded?

Put two entries in boot.ini and see if you get multi OS choice menu for two
seconds.

Regards,
Slobodan
 
Hi Slobodan,
I tested some boot.ini with two entries and I know that the boot.ini is
NOT loaded. The same error arrives without any boot.ini .
The message "cannot boot from CD code: 5" is NOT
on the WinPE CD! (But from where, Bios?) I think that was Microsoft
knowledge base said, Code 5 is an error arriving when there is an attempt
to load a driver which windows does not know to handle. It is so simple
what I try: Starting from an booting WinPE *.iso in VMware I changed
folder and filenames with hexeditor as long as it still boots. I changed
the kernel to the german version of my XPPRO and all WORKS. But if I
rename setupldr.bin to ntldr and copied it to the rootfolder this error
arrives at boot from CD.
I think, setupldr.bin does not (even not knows any about)need a boot.ini .
If You rename it and copy it to the folder there is a chance for a boot.ini
or? My dream is still a XP(E) which boots with NOEMULATION from CD (DVD). I
think this may reduce also the boottime. I believe that this can be
successfull, because WinPE boots from CD with the normal Kernel from
XPPRO!

I am also quiet shure, that EWF works on BOOTCD if the folders and files
are renamed as in XP(E)on harddisk before they went back to CD.

Dietmar
 
Dietmar,

1. You want to make XPe that will boot same as WinPE, right?
2. Also you want to install EWF that will work on that (WinPE like) image,
right?

IMHO it is pure waste of time attempting to do this based on what I know how
things work. (I reserve rights to be wrong of course, and you can prove that
I'm wrong very easily)

Bullet 1 can be done, but what would be the purpose of that?
Bullet 2 can be easily tested on WinPE image. Please indulge me and prove
that this can be done, if you can do that then everything can be done.


So for bullet 2.
Use regedit and preinstall Reg RAM configured EWF on WinPE image that boot
from CD.

Let me know what ewfmgr.exe used on CD vol letter tell you. (Please copy all
text from console)
I'm interested in two things:
- Whether you were able to enable EWF at all.
- Overlay memory usage.


Regards,
Slobodan
 
Hiho Slobodan,

I found the RIGHT Arcpath

[boot loader]
timeout=30
default=multi(0)disk(0)cdrom(159)\I386
[operating systems]
multi(0)disk(0)cdrom(159)\I386="Microsoft CDBOOT"
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft 2" /fastdetect


The second entry is only for to see, whether boot.ini is recogniced. It
is. Than, and that was my best idea, I renamed in folder I386 setupldr.bin
against setupldr.bak and put THERE EWFNTLDR and renamed THAT to
setupldr.bin.
Than boot.ini was left right and there stand message ntoskrnl.exe not
found, so I renamed the kernel as wished.
Now I am changing the other files in folder system32, but still the CD
boots, and I can put(hope) EWF there.

Dietmar
 
Hi Slobodan,
I copied the hole folder system32 from another XPPro partion in the ISO
image of WinPe. Now I saw the white line starting, now it wants
biosinfo.inf in the folder i386\inf and I think it WILL work...hihi.

Dietmar
 
Hi Dietmar,

You managed to do all this, WOW (I lost track of your transactions) ;-)
Could you please tell us: what do you think that is the function of ewfntldr
in your opinion and your own words?

Regards,
Slobodan
 
Back
Top