94 replies to this topic

[pscEx]

Maybe I have to replace some CopyFile by CopyOrExpand.

I did so in version 56, which is just uploaded.

The GUI support does not (yet) work with W2003 sources. Perhaps someone can find what is missing.
To test GUI support, type "format /?" in the PE.

Peter

[Vortex]

Hi Peter,

Many thanks for your nice work. Is it possible to add the MMC script?

[pscEx]

Hi Peter,

Many thanks for your nice work. Is it possible to add the MMC script?

Here the result with the existing MMC script of multiPE.

Maybe with some research for additional files it will work.

If somebody tries:

• "Replace dll files" MUST be ubselected
• "GUI support" MUST be selected.

Peter

[Virtual-R]

Hello again!

Format.COM is now working.
Another strange problem appears though, I get the error WINNT32U.DLL is corrupt or could not be read in.
I know this file is not corrupt, it happends if you run winnt32.exe command. I suppose something else is missing,
I haven't figured out what it could be.

I run with all addons checked (Like GUI support and so on) and "Replace DLL-files" unselected

Attached Thumbnails

• 

[Vortex]

Hi Peter,

I followed your advice but I got a similar error message in the attached image.

Attached Thumbnails

• 

[pscEx]

Another strange problem appears though, I get the error WINNT32U.DLL is corrupt or could not be read in.
I know this file is not corrupt, it happends if you run winnt32.exe command. I suppose something else is missing,

Only an idea: Unselect "Replace DLL files".

If that does not work, I currently have no idea.

Peter

[Virtual-R]

I will do some research myself to find what this is about. An idea is that this may have something to do with DLL-files in general. Maybe a key component is missing.
I don't know how high the priority to fix this is. Don't want to waste your time, Peter. I will check this myself and see what I can find. But I bet that other
programs also will work if the ability to read dll-files exists. I run with replace dll files unselected, have tried both selected and unselected but the same
problem is there.

[pscEx]

What is winnt32u.dll?

I do not have it in my XP host, and it is not on the XP source CD.

Peter

[Virtual-R]

You haven't? ?? That is weird, looked at two different WinXP source-cds now, both have that file. One is English, the other one is Swedish.
They are in the i386-catalog, and the are dated 2008-04-14 as the rest of the files on the cd. The source is SP3. Hmm.. This is the file that failes when you run winnt32 from the command prompt.
Here is what Google says:

"The winnt32u.dll module was not called by its present name originally. Winnt32.exe is the original filename of winnt32u.dll module. In new installations of Windows, there is a separate winnt32.exe file and a winnt32u.dll module that works along with it during an installation or an upgrade of the Windows Operating System."

[pscEx]

I found winnt32.exe on my German source CD.
Appearently this needs winnt32u.dll which is not in my source CD.

But when you google for it, it seems to be in a driver kit.

Looks like that in a customized script you added winnt32.exe to %Target%. Here you also have to add winnt32u.dll.

If you did so, and there is no success, please PM me the English winnt32u.dll. I have some English source CDs and will check with them.

Peter

[Virtual-R]

As you can see, the file exists, so it's stange that it doesn't work. i also noticed that commands like edit.com doesn't work, but for me personally that is not important . I uploaded the DLL here: http://speedy.sh/7Nv56/WINNT32U.DLL . Thank you for caring!

Attached Thumbnails

• 

[pscEx]

Try to copy winnt32.exe into the X:XPI386 directory and start from there!

But appearently X:XP is already known, as the error message shows ...

Peter

[Virtual-R]

My attached Picture was not so good, I did a dir *.dll, the winnt32.exe is also in the correct folder, so this is not the problem. I'm still researching this, I don't know why it doesn't work. I have done this script in win7pe and livexp, and there they work, so it's something thas is missing. I also noticed that commands like edit.com doesn't work. As I have said earlier, Peter this is my personal interest only. If other people are uninterested in getting this to work, don't waste time on me . Doing research as much as I can . Thank you again!

[Vortex]

Another test : notepad.exe is quitting silently without displaying it's graphical interface.

[Virtual-R]

Notepad.exe needs support from other files in order to run: Shell32.dll, Kernel32.dl, User32.dll, Gdi32.dll, Comdlg32.dll, and Advapi.dll. These DLLs are the Dependencies of Notepad.exe. Each of these files are Dependents of the Kernel32.dll. I don't think the intention of PicoXP was to fill it with things, so I don't know what Peter thinks of getting all this different programs to work from the shell. Winnt32.exe MAYBE is of interest, since some people may want to use this script to install Windows. But I don't know

[Wonko the Sane]

Notepad.exe needs support from other files in order to run: Shell32.dll, Kernel32.dl, User32.dll, Gdi32.dll, Comdlg32.dll, and Advapi.dll. These DLLs are the Dependencies of Notepad.exe. Each of these files are Dependents of the Kernel32.dll. I don't think the intention of PicoXP was to fill it with things, so I don't know what Peter thinks of getting all this different programs to work from the shell. Winnt32.exe MAYBE is of interest, since some people may want to use this script to install Windows. But I don't know

Just in case (and JFYI):
http://reboot.pro/3717/page__st__100
Findings on PicoXP and XPCLI may be interchanged.


Wonko

[pscEx]

Vortex and Virtual-R!

Thanks for your interest. That helps a lot to improve the projects.

It's much more better than I would sit in my office and insert only my ideas to improve the project.
I'm retired since some years. Although a pensioner is basically very little free time I like to work on challenges.

When I add some GUI support, it should be "perfect" as long as it deals with low level native functions like ntdll, kernel32 etc.

It is not intended to add higher level systems like mmc (as seen it does not run).

When you want to see my final goal, download the multiPE project, define a XP source, choose cmd as shell and use the option "Add GUI support"

In PicoXP there are only some more files / reg entries to add. Which ones, we have to find.

Peter

[Vortex]

Finally, I got working notepad.exe. I borrowed some lines from the GUI.script found in the latest MultiPE project. Insert the lines to the [Process] section of the GUI.script :

CopyOrExpand,%source_win%ADVAPI32.DLL,%target_sys%

CopyOrExpand,%source_win%APPHELP.DLL,%target_sys%

CopyOrExpand,%source_win%COMCTL32.DLL,%target_sys%

CopyOrExpand,%source_win%COMDLG32.DLL,%target_sys%

CopyOrExpand,%source_win%CRYPTUI.DLL,%target_sys%

CopyOrExpand,%source_win%DESK.CPL,%target_sys%

CopyOrExpand,%source_win%DISKCOPY.DLL,%target_sys%

CopyOrExpand,%source_win%IMM32.DLL,%target_sys%

CopyOrExpand,%source_win%IPHLPAPI.DLL,%target_sys%

CopyOrExpand,%source_win%KDCOM.DLL,%target_sys%

CopyOrExpand,%source_win%LSASRV.DLL,%target_sys%

CopyOrExpand,%source_win%LSASS.EXE,%target_sys%

CopyOrExpand,%source_win%MSGINA.DLL,%target_sys%

CopyOrExpand,%source_win%MSV1_0.DLL,%target_sys%

CopyOrExpand,%source_win%MSVCP60.DLL,%target_sys%

CopyOrExpand,%source_win%NCOBJAPI.DLL,%target_sys%

CopyOrExpand,%source_win%ODBC32.DLL,%target_sys%

CopyOrExpand,%source_win%OLE32.DLL,%target_sys%

CopyOrExpand,%source_win%OLEAUT32.DLL,%target_sys%

CopyOrExpand,%source_win%OLEDLG.DLL,%target_sys%

CopyOrExpand,%source_win%OLEPRO32.DLL,%target_sys%

CopyOrExpand,%source_win%POWRPROF.DLL,%target_sys%

CopyOrExpand,%source_win%RUNDLL32.EXE,%target_sys%

CopyOrExpand,%source_win%SERVICES.EXE,%target_sys%

CopyOrExpand,%source_win%SHELL32.DLL,%target_sys%

CopyOrExpand,%source_win%SHLWAPI.DLL,%target_sys%

CopyOrExpand,%source_win%SXS.DLL,%target_sys%

CopyOrExpand,%source_win%SYSSETUP.DLL,%target_sys%

CopyOrExpand,%source_win%UMPNPMGR.DLL,%target_sys%

CopyOrExpand,%source_win%URLMON.DLL,%target_sys%

CopyOrExpand,%source_win%USER32.DLL,%target_sys%

CopyOrExpand,%source_win%USP10.DLL,%target_sys%

CopyOrExpand,%source_win%VGA256.DLL,%target_sys%

CopyOrExpand,%source_win%WININET.DLL,%target_sys%

CopyOrExpand,%source_win%WINSPOOL.DRV,%target_sys%

CopyOrExpand,%source_win%WLDAP32.DLL,%target_sys%

CopyOrExpand,%source_win%WSOCK32.DLL,%target_sys%

I am sure there are some unnessary entries above but the quick test worked fine.

[Virtual-R]

Not only did you solve Notepad.exe ! WINNT32.exe ALSO WORKS NOW! It doesn't complain about Winnt32u.dll anymore! Brilliant, BRILLIANT! Thank you all!

[Vortex]

Hi Virtual-R,

Yes, after adding the missing files to PicoXP winnt32.exe runs fine. As I mentioned in my previous posting, you have to review the list of files above to remove the unnecessary dependencies.

[TheHive]

Can you make a script to let a user select one .exe file as a shell.

[Virtual-R]

Vortex, yes, when I got more time, I will Review this, it will be interesting to know exactly what was needed and not. TheHive: have you tried to create a batchfile that calls for an exe-file?

[Wonko the Sane]

Peter,
I am doing some experiments "mixing together" PicoXP, XPCLI and Pre-PE:
http://reboot.pro/12339/
I found a number of issues with command line support, are you interested in troubleshooting together them?
I also noticed how you changed some of the approaches since the discussions on the "original" thread regarding Fonts:
http://reboot.pro/76/

For the record Dos Navigator 2.14 beta:
http://www.dnosp.com/
http://www.dnosp.com...dn2/dn2w214.rar
seemingly works allright in PicoXP,
BUT in one of my builds I needed to change the settings of the console taking down the buffer from current 300 to the the "normal 25" or however have buffer size the same as the "Windows Size" (cannot say if this is actually caused by some settings in the script or is the result of my fiddling with it ).
I personally hate the colours chosen for the console, to get access to these settings, these are (all) the files needed for console:

CMD.EXE
NTDLL.DLL
KERNEL32.DLL
MSVCRT.DLL
USER32.DLL
GDI32.DLL
ADVAPI32.DLL
RPCRT4.DLL
CONSOLE.DLL*
COMCTL32.DLL*
SHELL32.DLL*
SHLWAPI.DLL*

marked with asterisk the ones that are not in PicoXP (yes I know they add a lot of bloat ).
BUT, I just tried succesfully a nice trick , which I think has some future .
Since the SHELL32.DLL is normally within the "HKEY_LOCAL_MACHINESYSTEMControlSet001ControlSession ManagerKnownDLLs" (but it is not present in the PicoXP build), I removed the entry for shell32 from it.
I am testing in Qemu with a hard disk image that has "my" XPCLI on it (that has these DLL's) and "your" PicoXP booting off the .iso mounted as CD-ROM.

So, I navigate to C:XPCLIBRSystem32 and PicoXP uses the .dll's in there . (same can be done by adding it to the PATH variable).
This approach IMHO could lead - in due time - to a new "concept" of "LEECH PE" (a really minimal PE that makes use of files already present in the XP install on hard disk) that could have some uses.

Small BUG report:
EDIT.COM does not work on "standard" PicoXP because AUTOEXEC.NT and CONFIG.NT are cab compressed, these files need to be de-cabbed, and then it works fine


Wonko

[pscEx]

Wonko!

I'm very interested, but give me some time to start. Currently I'm working on "LiveXP under WB82". There are still some issues with the API.

BTW: I already solved the "edit.com" issue. I think the fix is in the latest upload, but who knows ... Maybe I made the fix after upload.

Peter

[Wonko the Sane]

I'm very interested, but give me some time to start. Currently I'm working on "LiveXP under WB82". There are still some issues with the API.

No prob whatsoever, as always we have all the time on the world....


Wonko