Run-time error '-2147221020 ( 800401e4)'
Dietmar
I install Cenatek Ramdisk 1.9 on a harddrive with XPeSP2, and when I RUN
it, I get this error:
Run-time error '-2147221020 (800401e4)'
Automation error
Invalid syntax
I think the term in the parentesis is due to an error in VB script or to
the missing Java VM. Unfortuanetly I cant use InCtrl5 because the
installation is automated using *.msi.
Please help
Dietmar
KM
> Hi all,
> I install Cenatek Ramdisk 1.9 on a harddrive with XPeSP2, and when I RUN
> it, I get this error:
What exactly did you run? Did you just try the driver itself? The driver should work as it should have very minimum dependencies.
> Run-time error '-2147221020 (800401e4)'
> Automation error
> Invalid syntax
http://www.computerperformance.co.uk/Logon/code/code_800401E4.htm
Although I think you are missing some dependencies of the app you are trying to run. Did you check it with DependencyWalker?
How about Regmon/FileMon (www.sysinternals.com)?
> I think the term in the parentesis is due to an error in VB script or to
> the missing Java VM. Unfortuanetly I cant use InCtrl5 because the
> installation is automated using *.msi.
Why can't you?
Btw, I'd recommend you to use a tool like RegSnap (search Google for it). It will give you more appropriate output (a .reg file).
KM
Dietmar
DependencyWalker shows me in XPE 4 files, that are missed:
inetcom.dll
mobsync.dll
msjava.dll
w32topL.dll
Do You know, which Component from the database this is?
I make a try to copy them myself.
Thanks
Dietmar
Slobodan Brcin (eMVP)
You have a filter option in TD that will give you an option for searching for components that contain specific file.
Regards,
Slobodan
PS:
At least one of these files in not a part of XPe/ XPP.
"Dietmar" <dietmar....@t-online.de> wrote in message news:f808efd71df8f3ab...@localhost.talkaboutsoftware.com...
Dietmar
there is no Java in XPe.
I take another Ramdisk,
RamdiskXPPro Vers. 6.0.0.1
an OLDER version by www.superspeed.com
This works great, 2GByte Ramdisk.
Now I build an SDI image (near to XPPRO, but only 501MB XPe on NTFS
compressed)in Ram with an extra Ramdisk installed as drive T.
Hope, all will work.
Dietmar
KM
As Slobodan mentioned, you may want to make use of the TD Filters feature.
Anyway, fromthe files you meantion only the mobsync.dll belongs to "Offline Browsing for Internet Explorer" component, and the
w32topl.dll is "Primitive: W32topl".
Others are not part of XPe/SP1 database/repository (and not part of XP Pro standard).
KM
Slobodan Brcin (eMVP)
I think that I forgot what you wanted to do in the first place.
I guess that you gave up on ramboot solution since you have created few different threads since the original post.
If you are still trying to make third party ramboot to work, then you probably know something about this problem that I do not know.
Please can you share with us how you are going to do this step by step?
Take assumption that we all know how to put 700 MB image in SDI file and what now.
How do you configure your XPe, ramdisk, procedures, procedures.....
> with an extra Ramdisk installed as drive T.
> Hope, all will work.
Hope is always a good thing :-) Although T: as boot volume letter sounds as that you exactly know what you are doing and that you
want it for some obscure reason that way. Or second choice is that you are not aware why this will not work.
Option 1 is legal since I have used Z: as boot drive letter, but I just want to be sure that you are on right way.
Anyhow good luck, I have seen stranger things to work and much simpler not to work so everything is possible with XPe :-)
Slobodan
"Dietmar" <dietmar....@t-online.de> wrote in message news:6cc29770337de201...@localhost.talkaboutsoftware.com...
Unknown
I learned so much about XPe in the last few days.
That is a wonderful OP, but it offers you all the
chances (of unallowded?,I hope not) things to do that you dont have in
XPPro. I boot an REAL XPPro dressed up as XPe in SDI clothes (hihi)to RAM
but it was not stable.
The first attempt with syslinux does not work.
I will write Remi Lefevre an EMail. In his tutorial he said, that it works
with SDI version 1.0.
I tried with version 1.0 and version 2.0 (XPeSP2)but it
doesnt work all all. I am sure, that is not my default.
I will write a Tutorial, when I am ready.
Perhaps about those things, that are possible, Microsoft
dont will make a Longhorn Embedded. That would be very sad.
Dietmar
Slobodan Brcin (eMVP)
> I learned so much about XPe in the last few days.
> That is a wonderful OP, but it offers you all the
> chances (of unallowded?,I hope not) things to do that you dont have in
> XPPro. I boot an REAL XPPro dressed up as XPe in SDI clothes (hihi)to RAM
> but it was not stable.
Not stable. As in it work few minutes then it crashes? Congratulations if you made it up to desktop at least once. (Not by using
some virtual machine)
> The first attempt with syslinux does not work.
> I will write Remi Lefevre an EMail. In his tutorial he said, that it works
> with SDI version 1.0.
> I tried with version 1.0 and version 2.0 (XPeSP2)but it
> doesnt work all all. I am sure, that is not my default.
Huh. Why do you use Linux? And what exactly do you use. How?
> I will write a Tutorial, when I am ready.
> Perhaps about those things, that are possible, Microsoft
> dont will make a Longhorn Embedded. That would be very sad.
Did not understand you about Longhorn part of question :-(
Microsoft dedicated almost all resources in making LHe.
Regards,
Slobodan
KM
> I learned so much about XPe in the last few days.
Good experience for you :-)
> That is a wonderful OP, but it offers you all the
> chances (of unallowded?,I hope not) things to do that you dont have in
> XPPro. I boot an REAL XPPro dressed up as XPe in SDI clothes (hihi)to RAM
> but it was not stable.
Not stable? So, did you make it to boot at least once?
Btw, SDI is a features of XP Pro ntldr first. XPe just inherits the feature by using XP Pro ntldr and MS ramdisk driver (that was
probably developed specifically for ram boot).
> The first attempt with syslinux does not work.
> I will write Remi Lefevre an EMail. In his tutorial he said, that it works
> with SDI version 1.0.
> I tried with version 1.0 and version 2.0 (XPeSP2)but it
> doesnt work all all. I am sure, that is not my default.
If you are still referring to this tutorial http://remile.free.fr/syslinux/sdi.txt, then it is not mentioned there what size of the
XPe imaeg they have tried.
It is pretty unusual to boot huge XPe (or XP Pro) images to RAM, so I assumed they only tried small XPe images (not above the known
limit).
> I will write a Tutorial, when I am ready.
> Perhaps about those things, that are possible, Microsoft
> dont will make a Longhorn Embedded. That would be very sad.
In LHe you will have more flexible solution with more control.
KM
Slobodan Brcin (eMVP)
Point 3 in that doc is pretty clear to me:
"
3) Import the partition in the SDI file (sdimgr xpe.sdi /readpart:D:).
The size of the partition must be less than 500 MB.
"
Regards,
Slobodan
"KM" <konstmor@nospam_yahoo.com> wrote in message news:uTxk7dQ7...@TK2MSFTNGP14.phx.gbl...
Dietmar
real XPPro boots with SDI.
Slobodan said, that all NTLDR's of XPPro, XPe,
XPeRemoteboot are the same.
That is not right, try.
But the limit of 500MB is because of SDI not broken, and that is what I
first wanted.
Now I am installing Suns JavaVM5.0, then I am ready.
Dietmar
David D
scripting in it.
I would get that same error (I think ).
I added the WMI components (I have the following:
WMI core
WMI coorelation
WMI filter
WMI management snapins
WMI scripting
WMI SNMP provider
WMI tools
WMI view provider
WMI win 32
WMI windows installer provider
"Dietmar" <dietmar....@t-online.de> wrote in message
news:b1a2eb9ffeb0ff95...@localhost.talkaboutsoftware.com...
Slobodan Brcin (eMVP)
Would you indulge my curiosity and tell us how long does it take for your XPP SDI image to load to ram?
> Slobodan said, that all NTLDR's of XPPro, XPe,
> XPeRemoteboot are the same.
> That is not right, try.
I never said that all of them are the same. There are many versions. XP Gold, SP1, SP2, and probably some fixes in between. But if
you take for instance same XP Pro SP2 version of ntldr and XPe SP2 ntldr you will see that they are same.
XPe has special ewf_ntldr but this does not fall in our story here, does it?
There is a first time that I hear of ntldr that is meant for XPeRemoteboot, but as they say there is a first time for everything :-)
> But the limit of 500MB is because of SDI not broken, and that is what I
> first wanted.
Sorry my English is not so good and I can't make any sense from above. What are you trying to say, it eludes me? :-(
> Now I am installing Suns JavaVM5.0, then I am ready.
Ready for what ?!!!! What is relation of SDI, ramboot XPP, XPe and Suns JavaVM5.0 ?!?!
Regards,
Slobodan
"Dietmar" <dietmar....@t-online.de> wrote in message news:ac0f2c704cc8f645...@localhost.talkaboutsoftware.com...
KM
Oops.. I missed that point. Thanks for watching! :-)
Then that makes it even more clear.
--
Regards,
Konstantin
KM
>
> > Now I am installing Suns JavaVM5.0, then I am ready.
>
> Ready for what ?!!!! What is relation of SDI, ramboot XPP, XPe and Suns JavaVM5.0 ?!?!
Slobodan, he is probably still trying to stick with the Cenatek ramdisk driver an fix its install. I don't know how it can help him,
though.
Dietmar, if you want to fix the Cenatek install issues you may want to stick with MS java to avoid any problem later on.
Also, look at the David's reply below. He listed WMI components you would need in your image.
--
Regards,
KM, BSquare Corp.
Slobodan Brcin (eMVP)
> >
> > > Now I am installing Suns JavaVM5.0, then I am ready.
> >
> > Ready for what ?!!!! What is relation of SDI, ramboot XPP, XPe and Suns JavaVM5.0 ?!?!
>
> Slobodan, he is probably still trying to stick with the Cenatek ramdisk driver an fix its install. I don't know how it can help
him,
> though.
Konstantin, come on, as you know preinstalling driver without using any install program is simple, especially when compared to what
he is doing.
Although I'm still curious about his accomplishment in booting XPP so far.
Regards,
Slobodan
Dietmar
I build an real XPPro with 350MB SDI image on compressed NTFS. (Looks
terrible with 4BitColor...hihi). I booted this to Ram from my USB
harddrive.
The boottime is about half a minute. The Windows XPProfessional screen
appears and disappears after the BOOT in about 7 seconds,..grrr.
There is an extra NTLDR "Remoteboot" in Windows Embedded\Remote Boot
Service\Downlods.
I told that with Java5, because my XPe image is ready.
456MB on compressed NTFS, nearly "XPPro" with Java, DVD Player, 2Gbyte
Ramdisk, Winrar, Paintshoppro, KazaaliteMegacodec, Mediaplayer9, DirectX9,
Sound from Audigy, Gigabitnetwork, 9700AllinWonder usw. That that is able
with XPe impresses me much. I boot that to Ram.
The only thing I worried about, that I have still the english keyboard
layout. Is there a chance to go to the German layout AFTER building the
image?
Dietmar
KM
> Konstantin, come on, as you know preinstalling driver without using any install program is simple, especially when compared to
what
> he is doing.
Yup.. And that is why I asked him earlier in this thread on how the driver works by itself? (without the complex installation)
Did not get any response and assumed he is still trying the msi package. :-)
> Although I'm still curious about his accomplishment in booting XPP so far.
Me too.
Regards,
Konstantin
Slobodan Brcin (eMVP)
> I build an real XPPro with 350MB SDI image on compressed NTFS. (Looks
> terrible with 4BitColor...hihi). I booted this to Ram from my USB
> harddrive.
> I build an real XPPro with 350MB SDI.
What do you mean by that? How can you build a real XP Pro? It is either XP embedded or XPP, what is in between?
> The boottime is about half a minute. The Windows XPProfessional screen
> appears and disappears after the BOOT in about 7 seconds,..grrr.
Use /noguiboot to remove this. But again how do you build XPP image of 350MB.
> There is an extra NTLDR "Remoteboot" in Windows Embedded\Remote Boot
> Service\Downlods.
>
> I told that with Java5, because my XPe image is ready.
Again is it XPe or XPP?
What do you mean by "The Windows XPProfessional screen"?
> 456MB on compressed NTFS, nearly "XPPro" with Java, DVD Player, 2Gbyte
> Ramdisk, Winrar, Paintshoppro, KazaaliteMegacodec, Mediaplayer9, DirectX9,
> Sound from Audigy, Gigabitnetwork, 9700AllinWonder usw. That that is able
> with XPe impresses me much. I boot that to Ram.
Ok so you have two ramdisks? Right?
BTW: Check licensing issues about the product that you are making, I do not know if you are allowed to make such product. (It does
not sound toom much "Embedded").
> The only thing I worried about, that I have still the english keyboard
> layout. Is there a chance to go to the German layout AFTER building the
> image?
Create new thread for this.
But basicaly you can do that from TD.
Regards,
Slobodan
Dietmar
I took XPlite on a fresh XPPro installation and
takes simply ALL marks away. The result is 350MB.
I build an SDI image of THAT XPPro with boot and load blob and booted that
to ram, believe me or not.
Yes, now I have two ramdisks one from windows XPe (500MB) and one from
superspeed (2Gbyte) and I will try to boot in each one, but thats a hard
work.
Dietmar
KM
> > I build an real XPPro with 350MB SDI.
> What do you mean by that? How can you build a real XP Pro? It is either XP embedded or XPP, what is in between?
For instance, nLite (http://www.msfn.org/comments.php?shownews=11162).
However, it is hard to name it as "build".
--
Regards,
Konstantin
KM
I have no doubt you could RAM boot the 350Mb XP Pro "image".
But now you confused us more.. I thought you were trying to boot > 500Mb image.
--
Regards,
KM, BSquare Corp.
Slobodan Brcin (eMVP)
> I took XPlite on a fresh XPPro installation and
> takes simply ALL marks away. The result is 350MB.
> I build an SDI image of THAT XPPro with boot and load blob and booted that
> to ram, believe me or not.
I was just curious. It is not a matter of belief.
XPlite has nothing to do with XPe and build terminology. I'm glad that we sorted that out.
350 MB is smaller than 500 MB so it is ok.
One more ingredient is missing here to make this work. What about ramdisk driver that you used with this test? Are you saying that
you just put third party driver without configuring it and it started to work?
> Yes, now I have two ramdisks one from windows XPe (500MB) and one from
> superspeed (2Gbyte) and I will try to boot in each one, but thats a hard
> work.
ramdisk from XPe will work, that was never in question.
But I was under impression during all this time that you was able to use third-party ram disk driver.
Regards,
Slobodan
Slobodan Brcin (eMVP)
Slobodan
"KM" <konstmor@nospam_yahoo.com> wrote in message news:ub3ighR7...@TK2MSFTNGP12.phx.gbl...
KM
I probably just have a better internet connection (T1) :-)
--
Regards,
Konstantin
Slobodan Brcin (eMVP)
And to that add few hundred milliseconds of ping time head-start that you have over us from Europe :-)
Regards,
Slobodan
"KM" <konstmor@nospam_yahoo.com> wrote in message news:eVoFKoR7...@TK2MSFTNGP14.phx.gbl...
Dietmar
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
Slobodan Brcin (eMVP)
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....@t-online.de> wrote in message news:41634c87e4a06260...@localhost.talkaboutsoftware.com...
Yann Blue
Hi,
> 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.
>
Slobodan is right: syslinux+SDI patch uses 32 bits addressing in
protected mode to load the SDI image in RAM, so it can load
images > 500 MB in RAM. But this
doesn't make Windows XPe able to handle it. I put a 500 MB limit on SDI
image sizes in the doc because of the default MS Ram Disk driver
limitation, however, because you could find another driver, it permits
bigger sizes.
Syslinux+SDI patch loads the image in RAM at 0x1000000h (I had issues when
loading below this limit). But as Slobodan said 'the higher you go the
better' is perhaps a better choice.
best regards,
Rémi