102 replies to this topic

[damian666]

hmm, what do you think? would it be due to the space between program and files?
could that be it?
and i am glad the service is finally runnig man, now its almost done
but how to check if we are on PE?

hmm, i will try something...

Damian666

[damian666]

ok, new version uploaded man.
try it out, and let me know dude

Damian666

[allanf]

hmm, what do you think? would it be due to the space between program and files?
could that be it?
and i am glad the service is finally runnig man, now its almost done
but how to check if we are on PE?

hmm, i will try something...

Damian666

command-line imagex really believes that the image is mounted on x:\mount, but it just anin't there. In fact, imagex will even capture the 'mounted' image to another .wim - ends up as a 1KB .wim, and will mount that one to x:\ as well - but it ani't there either!

I've cranked winpe 2.1 up as much as I can - added all the optional packages, 512MB ScratchSpace in RAM, and a pagefile on the c:\ drive. Might be something else...

I could try 'dependency walker' to see if there is some other system files I can add to winpe... not sure where to go from here. I think it's something to do with the two filters - WimFltr and the FBWF on x:\ - don't work together?

Regards

[damian666]

well, the only thing i can think of now, is really hard coding that c: disk in man.
i didnt do that now, i checked for drive letters and then let it select the non x one.
but maybe that doesnt work?

so i will hard code it for now...

be back in a few moments

Damian666

[allanf]

well, the only thing i can think of now, is really hard coding that c: disk in man.
i didnt do that now, i checked for drive letters and then let it select the non x one.
but maybe that doesnt work?

No. It was still "mounting" on x:\mount.

I can't believe this... cmd imagex will '/unmount /commit' the image "mounted" by 'wim mounter pe'.

I tried cmd-line imagex to '/apply' the image to 'x:\mount' - it errors out after a few minutes with 'insufficient resources' message but leaves behind a fair bit of what's in my test wim, winpe.wim - the directories, and quite a few files... I'll try cranking up the Virtual Machine and WinPE even more.

[damian666]

hard coded one uploaded man.
if this doesnt work, then please shoot me

let me know dude

Damian666

[allanf]

wim mounter pe
ok, xp install of driver now standard, also left the button for now...

and the mountmap switched to x:\mount.

let me know if you tested it ok?

Damian666

... just rebuilding my ISO. I have some real-world things to do in a few minutes, be back soon - an hour at most. You take it easy. I'll let you know.

Regards

[allanf]

... just rebuilding my ISO. I have some real-world things to do in a few minutes, be back soon - an hour at most. You take it easy. I'll let you know.

Regards

...quick look... image mounted successfully....

...got to go!

[damian666]

Lets all hail the great scripting god high in the sky
ok man, thanx, i will be back in a few hours, i have to go get some sleep.
have work later man

thats real live for ya huh?

Damian666

[allanf]

The more I look at this Program, the more I like it and what it does.

For readers - most of the discussion in this thread relates to getting 'Wim Mounter' to work in the Windows PE OS - a bare-bones OS designed to run in RAM. The program should run fine in a full OS.

Here's the next hurdle for WinPE... and I think it's a big one!


[attachment=5072:WimMExp.png]


I have tried the 'Options' to set/remove the file association.

... does the File Association have anything to do with x:\windows\explorer.exe? The screenshot shows the Windows Directory of the mounted winpe.wim - mounted with 'Wim Mounter PE' ... ... It's the same as the running WinPE OS on 'x:\'. And there isn't any explorer.exe in WinPE - not anywhere!

If this is the cause of the error message, I can think of two alternatives - 'Wim Mounter PE' tags up with some free File Manager, or it gets customized for individual WinPE projects that install there own File Manager. The former might be one universal solution. I can't think of anything else.

For the latter, I was thinking of my pe2 project, where it might be possible to set a System Variable to say %FileManager%. ('Wim Mounter' would probably work 'as is' on VistaPE because explore.exe can be taken from install.wim)

What's the solution? Have I got the problem right?

Regards

BTW, I'm looking at emergeDesktop - the shell replacement I use. There's a new version out. Some of its features still depend on explore.exe too.

[TheHive]

You should get in contact with the author of emergeDesktop and tell him about the project youre using his shell on. He might be incline to come here and help or update emergeDesktop to mee the needs.

[allanf]

You should get in contact with the author of emergeDesktop and tell him about the project youre using his shell on. He might be incline to come here and help or update emergeDesktop to mee the needs.

Yes. I have been thinking aout what to say to the developers of all the software I use in the project - apart from "Thanks" and "Hope you don't mind". I might have found a little bug with the new version of emergeDesktop, so I should say something to them. Thanks for the prompt!

Regards


BTW ... ... I thought you'd found a solution to my problem... ...

[damian666]

Well, i think that file assciations are only for use in the explorer man.
dont think it works without it...
It is just a reg-entry that gets added for the .wim extension though...
so thats not the prblem, but i think you need a explorer thingy to see that change.

any idea's ?
And thanx for liking my program man.

i am afraid, i have to make it a seperate version though...
it will be to hard , to try to adept the main wim mounter to all the things needed to let it run on PE, and still have the functions it does now.

But thats not a real problem huh?

Damian666

and again man, thanx for the help, we are a good team

[allanf]

OK. The 'Options' file association is for .wim files. I like that idea too! That's not the real issue.

The error message is from WinPE/Vista asking for file association for 'c:\mount' - should be folder association - and it's looking for explorer.exe - and asking to set the association in a control panel which WinPE doesn't have. That has given me an idea - I didn't know it was possible to associate folders with a file manager. I will need to do some research, because it would need to be done from my end.

Correct me if I'm wrong! And if you have the registry entries, let me know.

Regards

BTW, @TheHive, I have registered with emergeDesktop and awaiting activation of my account. I'm sorry about the off-topic thing. You know you are welcome wherever you dare to tread!

[damian666]

then i did not understand you right man, i thought it was due to the wim mounter association.

but if you can set that to a folder ???
i dont know man, so i dont have a regentry for you sorry

Damian666

[allanf]

No. It's when I click 'Open' that the error pos up... I should have said that before. The title of the error is 'c:\mount' and no association. It wants to know what program to dislpay the files... I assume.

[damian666]

well, to be honest, i think its about the wim mounter man
i use shellexecute to open the folder so.
so that would look for explorer to open it i think

hmm, i will look intoo it man

Damian666

[Frank77]

Could you make a version that can open WinFLP.wim of the Windows Fundamentals for Legacy PCs (WinFLP). ? That would be great

[damian666]

well, what is the difference about that wim then?
i dont even saw one, so i dont know what to do with it...

But if its possible, then yes, i can man

Damian666

[Frank77]

well, what is the difference about that wim then?
i dont even saw one, so i dont know what to do with it...

But if its possible, then yes, i can man

Damian666

I don't know what is different about that wim. That OS is a mixture between xp and vista.

[allanf]

well, to be honest, i think its about the wim mounter man
i use shellexecute to open the folder so.
so that would look for explorer to open it i think

hmm, i will look intoo it man

Damian666

Any ideas yet?

I've asked the people at emergeDesktop to look into making the FileManager configurable. However, I wouldn't want you to design 'Wim Mounter PE' exclusively for one shell. I know litestep has a Variable called $FileManager$, but I'm not sure if a System Variable or only for launching the FileManager from litestep shortcuts. bbLean might have the same.

Really, it should be independent of any shell.... a Universal solution. How can it find the FileManager?

... ... catch you later!

[was_jaclaz]

I don't know what is different about that wim. That OS is a mixture between xp and vista.

Well, NO.
It's a reduced XP that is installed through the .wim engine of Longhorn, that uses a different WIM format.

See this:
http://www.boot-land...?...ic=3549&hl=

jaclaz

[damian666]

@ allanf, to be honest man, no i dont have a clue...
without a explorer like shell, it wont open that folder, and i dont know of any other way to call that function so...

@frank77, well as you read, i dont think it can be done man...

bummer huh, but its waaaay of the normal wim image so...

Damian666

[allanf]

@ allanf, to be honest man, no i dont have a clue...
without a explorer like shell, it wont open that folder, and i dont know of any other way to call that function so...

damian666,

You can do it man. I can do it with two two cmds:

'set FILEMANAGER="D:\Program Files\FreeCommander\FreeCommander.exe"'
'%FILEMANAGER% c:\mount'

Look at the screenshot:

[attachment=5086:WimMFilM.png]

What is all the space in 'Options' dialogue for? It's there to select the alternative filemanager. ... ... All the good ones will take 'c:\mount' as the first parameter.

That's it.

Look at from a user's point of view. Click on 'Open', and that WinPE/Vista error pops up about 'c:\mount' having no file (sic) association, and asking to go to some control panel that doesn't exist. What does the user do? Clicks on 'Options', and voila, there's an option to input the path to an alternative filemanager. It would be good if you could intercept the error message with a message that says to click on 'Options' and input the path to the file manager.

If it's really out of the question, let me know and I'll give it a rest. It's been a great experience for me.

Regards

[damian666]

out of the question??? give it a rest??? hell no man!!!
we are just getting started man

if that is how it can work, then thats how we will make it work man, no problem...

and about the error message, i can always force the user to first set the option.
Because we agree that it wont work otherways right?

so we have too, i am also looking intoo a way to set the mountpoint.
It wont always be c:\, or maybe user wants a choice.

So that i can also put in the options page, it will search for present drives, and list them in a combobox.
So user can select there, and then down a bit to set the custom filemanager

like the idae? i do

let me know what you think, and expect a new version tomorrow ok?

thanx partner

Damian666