Ошибка получения объекта com 2147221020 0x800401e4 синтаксическая ошибка

Hi all,
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

Dietmar,

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

Hi Konstantin,
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

Hi Dietmar,

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.

Thanks Slobodan,
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

Dietmar,

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

Hi Dietmar,

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

Hi Slobodan,
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

Hi Dietmar,

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

Hi Slobodan,

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

Konstantin,

Point 3 in that doc is pretty clear to me:

«
3) Import the partition in the SDI file (sdimgr xpe.sdi /readpart.
The size of the partition must be less than 500 MB.
«

Regards,
Slobodan

Hi Slobodan an Konstantin,
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

Hi Dietmar,

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

Slobodan,

Oops.. I missed that point. Thanks for watching!

Then that makes it even more clear.

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?

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.

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?

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

Hi all,
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 EmbeddedRemote Boot
ServiceDownlods.

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

Slobodan,

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

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

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 EmbeddedRemote Boot
ServiceDownlods.

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