Re: Run-time error '-2147221020 ( 800401e4)'

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Slobodan Brcin \(eMVP\) (sbrcin_at_ptt.yu)
Date: 12/28/04 

Date: Tue, 28 Dec 2004 22:19:25 +0100

Hi Dietmar,

Finally some useful info that we can discuss here. Although thus thread is pretty confusing till now. Please create new thread
regarding ONLY to third party boot of images larger than 500 MB and please do not put there your current issues with current MS way
that work.

Now to your points:
> But with syslinux I boot an image of 950MB real XPPRO (as SDI)to ram,
> which doesnt boot.

Actually you load disk image to memory and that do not boot. This was never in question if it is possible to be done. Question is
whether implementation in ntldr can handle such disk size. But this can be work-arounded. By careful file organization so all driver
files required for first part boot come to the beginning of that disk. And you can fake a size of disk to ntldr.

> The image in ram is exactly the one as it was on
> hardisk, not a single Bit hast changed.

I believe you, this also was never a problem.

> 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.

Possible, but this is your problem. Also you said that you was able to do SDI RAM boot by using MS ntldr, so this mean that what
ever loader you are using you don't know how to configure it.
You can always make your own loader it is pretty simple and you have even working sources here in this NG posted by me.

> If Remi booted an SDI image under
> syslinux,I believe it could be much bigger, that ramdriver allows this.
Sorry could you give me a link again to article/tip that he wrote and that you are reffering to it constantly.
You are constantly mixing boot and "image load" terminology :-(

ramdriver was never preventing image load since image load happened mush before the OS start booting. This mean that there is no
ramdriver until everything is in memory.
MS RamDisk driver has limitation that is uses system address space that is very limited for its internal use. They simply did not
thought that for embedded usage someone would actually need more than 500 MB image I guess.

> 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.

I complained on this when I lost a day fighting this. Loading image above 8MB should be ok, but the higher you go the better (to
avoid being overlapped during the initial driver load sequence).
ntoskrnl is the thing that must go low in memory and few other boot drivers everything else can go to empty memory.

Regards,
Slobodan

"Dietmar" <dietmar.stoelting@t-online.de> wrote in message news:41634c87e4a06260ffa470f852867c0b@localhost.talkaboutsoftware.com...
> 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
>

Relevant Pages

  • Re: Run-time error -2147221020 ( 800401e4)
    ... >> which doesnt boot. ... > Actually you load disk image to memory and that do not boot. ... By careful file organization so all driver ... >> doesnt matter which size the image has. ...
    (microsoft.public.windowsxp.embedded)
  • Re: memory reading and writing
    ... And, of course, during the boot process, it's mostly ... Plus, remember that Windows uses "on demand" loading...hence, an ... This conspires to mean that once initialisation is run (which is ... "avoiding" to load things until strictly necessary... ...
    (alt.lang.asm)
  • Problems PXE installing 5.X on RLX Blade
    ... Its like its not finding or able to load the next module in the chain ... echo Loading Kernel... ... IntelBoot Agent Version 4.0.17 ... Building the boot loader arguments ...
    (freebsd-current)
  • Origin 200 Boot Problem
    ... Cannot load dkscunix. ... If I boot manually from SASH, ... Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org ...
    (comp.sys.sgi.hardware)
  • SGI Origin 200 Boot Problem
    ... Cannot load dkscunix. ... If I boot manually from SASH, ... Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org ...
    (comp.sys.sgi.admin)