Re: Run-time error '-2147221020 ( 800401e4)'
From: Dietmar (dietmar.stoelting_at_t-online.de)
Date: 12/28/04
- Next message: Slobodan Brcin \(eMVP\): "Re: Run-time error '-2147221020 ( 800401e4)'"
- Previous message: Slobodan Brcin \(eMVP\): "Re: Run-time error '-2147221020 ( 800401e4)'"
- In reply to: Slobodan Brcin \(eMVP\): "Re: Run-time error '-2147221020 ( 800401e4)'"
- Next in thread: Slobodan Brcin \(eMVP\): "Re: Run-time error '-2147221020 ( 800401e4)'"
- Reply: Slobodan Brcin \(eMVP\): "Re: Run-time error '-2147221020 ( 800401e4)'"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 28 Dec 2004 15:40:24 -0500
Hi Slobodan,
that is what I try. But I said always, that I do not succeed,for example
with syslinux.
But with syslinux I boot an image of 950MB real XPPRO (as SDI)to ram,
which doesnt boot. The image in ram is exactly the one as it was on
hardisk, not a single Bit hast changed.
I can prove that.
But is shows always the same behavior, loud beeping of the computer,
doesnt matter which size the image has.
Therefore I believe, that it might be possible, if Remi Lefevre tell us
the true. Only the bootloader doesnt found
the partition at the right place. If Remi booted an SDI image under
syslinux,I believe it could be much bigger, that ramdriver allows this.
One thing makes me astonish: The image in Ram is loaded AS HIGH AS
POSSIBLE. The NTLDR bootloader loads it as low as possible I think. But
that can be a very tricky thing, I know this from xmsdsk.exe in good old
DOS days.
Dietmar
- Next message: Slobodan Brcin \(eMVP\): "Re: Run-time error '-2147221020 ( 800401e4)'"
- Previous message: Slobodan Brcin \(eMVP\): "Re: Run-time error '-2147221020 ( 800401e4)'"
- In reply to: Slobodan Brcin \(eMVP\): "Re: Run-time error '-2147221020 ( 800401e4)'"
- Next in thread: Slobodan Brcin \(eMVP\): "Re: Run-time error '-2147221020 ( 800401e4)'"
- Reply: Slobodan Brcin \(eMVP\): "Re: Run-time error '-2147221020 ( 800401e4)'"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
