Help - Search - Members - Calendar
Full Version: XPSP1 with full commandline and NTFS below 10 MB
Boot Land > Groups > Boot Methods and various OS support > Windows 2K/XP/2003 and Vista
Pages: 1, 2
Dietmar
Hi all,

here is the promised XP SP1, which files can simple be copied on a NTFS compressed partition that is set activ. Uncompress only ntldr after that. Voila laugh.gif .
It contains only original XP SP1 files and a renamed minlogon to winlogon from Windows Embedded.
The whole registry is made by hand. >It is the full commandline cmd.exe, not based on WinPE, just full XP. I never saw something like before. Nice to hear from you

Dietmar

PS: At the moment, only IDE harddisks are supported with Fat, Fat32 and NTFS.
The boottime is 1 second biggrin.gif .
But this is a nice project, to build XP from single pieces, so I will integrate network, SATA and so on.

Hi all,
now it works also on SATA harddisks. It works on any compi... jump.gif .

Nice to hear from you,
Dietmar
TheHive
QUOTE
here is the promised XP SP1, which files can simple be copied on a NTFS compressed partition that is set activ. Uncompress only ntldr after that. Voila


Thanks! Sounds good.

I had a question(s)
Primary Partion. right?


When you say that it can be copied to an NTFS compressed Parttion. Is that Mandatory or is it a recommendation. Also how would you create a compressed Partition.

Howt do you go by doing the Uncompress Ntldr.



jaclaz
I find this to be a GREAT FIND!
thumbup.gif
yahoo.gif

Unfortunately sad.gif posting here the complete set of files may be against Forum Rules, thus I removed Dietmar's original attachment and I am posting here the core of it (the redistributable part):

attached filelist.7z is a dir of the original Dietmar's Setup.
attached config.7z is the contents of the \Windows\System32\config directory (a.k.a. the Registry)

BOOT.INI can be as follows:
CODE
[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP1 Dietmar's CLI"


You'll have to get your own Windows XP SP1 files + the minlogon.exe (from Windows XP Embedded).

I have tried to rebuild manually and tested it in Qemu (+Qemu Manager) successfully, but a further check by another user to make sure I didn't "cheat" somehow is welcome.

If anyone has some spare time, it would be nice if he could provide (preferably in the form of a batch file or of a Winbuilder .script) an automated way to build the directory structure and copy to it files from source \I386.

cheers.gif

jaclaz
dennis123123
I put together a batch file from Jaclaz's filelist, it doesnt show right in the codebox on this forum, its over at the 911cd forums Dietmar's topic about this.


http://www.911cd.net/forums//index.php?s=&...st&p=140543
jaclaz
QUOTE (TheHive @ Jan 3 2008, 09:09 AM) *
Thanks! Sounds good.

I had a question(s)
Primary Partion. right?


When you say that it can be copied to an NTFS compressed Parttion. Is that Mandatory or is it a recommendation. Also how would you create a compressed Partition.

Howt do you go by doing the Uncompress Ntldr.


1) Yes, Primary Partition
2) No, it should work on FAT as well (untested) but you will probably need more space, unsure.gif (actually cannot say, on such small volumes NTFS filesystem structures are rather BIG)
3) Select NTLDR -> Right Click -> Properties -> Advanced -> Untick "Compression"

Find attached a RAW 16 Mb image already formatted as NTFS Compressed and containing the Registry and Directory structure, suitable for QEMU.

To mount the image with IMDISK use an offset of 63 blocks.

NOTE:
using QEMU the screen tries to resize itself a few times during booting, to avoid this you can load the SYSTEM hive (in the example into HKEY_LOCAL_MACHINE with name "testgo") and change the entries 1024 and 768 in
HKEY_LOCAL_MACHINE\testgo\ControlSet001\Hardware Profiles\0001\System\CurrentControlSet\Control\VIDEO\{23A77BF7-ED96-40EC-AF06-9B1F4867732A}\0000
into 640 and 480


jaclaz
jaclaz
QUOTE (dennis123123 @ Jan 3 2008, 07:58 PM) *
I put together a batch file from Jaclaz's filelist, it doesnt show right in the codebox on this forum, its over at the 911cd forums Dietmar's topic about this.


http://www.911cd.net/forums//index.php?s=&...st&p=140543


Good work dennis123123,
I am attaching latest version as D123_XP.cmd smile.gif

(the problems in the early version - which I was checking - were only pidgen.dll and ksecdd.sys right? )

jaclaz
dennis123123
QUOTE (jaclaz @ Jan 3 2008, 07:30 PM) *
Good work dennis123123,
I am attaching latest version as D123_XP.cmd smile.gif

(the problems in the early version - which I was checking - were only pidgen.dll and ksecdd.sys right? )

jaclaz



Yes I think so rolleyes.gif

The working code is the current version at 911cd, and if it is the same, then also the one Jaclaz has kindly attatched cool.gif
jaclaz
Yep, just tested the attached batch file with BOTH XP SP1 and XP 2600 (SP0) and it works allright! smile.gif

Any taker for XP SP2 ?
And for Server 2003 ?
(though most probably there are REASONS why Dietmar used SP1) wink.gif

jaclaz


psc
QUOTE (jaclaz @ Jan 3 2008, 08:49 PM) *
Yep, just tested the attached batch file with BOTH XP SP1 and XP 2600 (SP0) and it works allright! smile.gif

Any taker for XP SP2 ?
And for Server 2003 ?
(though most probably there are REASONS why Dietmar used SP1) wink.gif

jaclaz


I'm already thinking about 'cmd' as third option of nativeEx_BSOR.
Because Dietmar's file list does not use any shell32.dll, I think, it's possible.

Peter coffee.gif
Dietmar
Hi jaclaz,

to integrate diskpart.exe in my mini XP isnt an easy task.

You have to add the following files:

diskpart.exe
dmadmin.exe

cabinet.dll
clusapi.dll
dmintf.dll
dmserver.dll
dmutil.dll
ole32.dll
oleaut32.dll
osuninst.dll
setupapi.dll
shlwapi.dll

The Registry needs 3 parts, I tested them, they work.


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID]

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\dmadmin.exe]
"AppID"="{4FB6BB00-3347-11d0-B40A-00AA005FF586}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{4FB6BB00-3347-11d0-B40A-00AA005FF586}]
@="Logical Disk Manager Administrative Service"
"LocalService"="dmadmin"






Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\dmadmin]
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\
74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,\
00,6d,00,61,00,64,00,6d,00,69,00,6e,00,2e,00,65,00,78,00,65,00,20,00,2f,00,\
63,00,6f,00,6d,00,00,00
"Start"=dword:00000003
"DependOnService"=hex(7):52,00,70,00,63,00,53,00,73,00,00,00,50,00,6c,00,75,00,\
67,00,50,00,6c,00,61,00,79,00,00,00,44,00,6d,00,53,00,65,00,72,00,76,00,65,\
00,72,00,00,00,00,00
"Type"=dword:00000020
"Description"="Configures hard disk drives and volumes. The service only runs for configuration processes and then stops."
"DisplayName"="Logical Disk Manager Administrative Service"
"ObjectName"="LocalSystem"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\dmadmin\Enum]
"Count"=dword:00000001
"NextInstance"=dword:00000001
"0"="Root\\LEGACY_DMADMIN\\0000"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\dmadmin\Parameters]
"EnableDynamicConversionFor1394"=dword:00000000

"ServiceParameters"="/com"





Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\dmserver]
"DependOnService"=hex(7):52,00,70,00,63,00,53,00,73,00,00,00,50,00,6c,00,75,00,\
67,00,50,00,6c,00,61,00,79,00,00,00,00,00
"ImagePath"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\
74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,73,\
00,76,00,63,00,68,00,6f,00,73,00,74,00,2e,00,65,00,78,00,65,00,20,00,2d,00,\
6b,00,20,00,6e,00,65,00,74,00,73,00,76,00,63,00,73,00,00,00
"DisplayName"="Logical Disk Manager"
"ErrorControl"=dword:00000001
"Type"=dword:00000020
"Start"=dword:00000002
"ObjectName"="LocalSystem"
"Description"="Detects and monitors new hard disk drives and sends disk volume information to Logical Disk Manager Administrative Service for configuration. If this service is stopped, dynamic disk status and configuration information may become out of date. If this service is disabled, any services that explicitly depend on it will fail to start."

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\dmserver\Enum]
"Count"=dword:00000001
"NextInstance"=dword:00000001
"0"="Root\\LEGACY_DMSERVER\\0000"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\dmserver\Parameters]
"ServiceDll"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,\
00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,\
64,00,6d,00,73,00,65,00,72,00,76,00,65,00,72,00,2e,00,64,00,6c,00,6c,00,00,\
00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\dmserver\Security]
"Security"=hex:01,00,14,80,90,00,00,00,9c,00,00,00,14,00,00,00,30,00,00,00,02,\
00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\
00,00,02,00,60,00,04,00,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,\
05,0b,00,00,00,00,00,18,00,9d,01,02,00,01,02,00,00,00,00,00,05,20,00,00,00,\
23,02,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,20,\
02,00,00,00,00,14,00,fd,01,02,00,01,01,00,00,00,00,00,05,12,00,00,00,01,01,\
00,00,00,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00


But you have to build a Mini XP to make diskpart work also with

dllhost.exe
lsass.exe
regsvr32.exe
rundll32.exe
services.exe
svchost.exe

and their whole dependencies. This makes my Mini XP larger to 48 MB (uncompressed).
Today I build such a Mini XP by hand, and diskpart.exe works with the 3 registry entries above.

Nice to hear from you
Dietmar

jaclaz
@Dietmar
Thanks, I would probably never have gotten there. smile.gif

I'll recheck the size of the needed files, but if it gets to 48 Mb I think it is too much to have the functionality of diskpart, we may need another app. unsure.gif

@All
To add FORMAT.COM to the build you need:
format.com
ulib.dll
ifsutil.dll
cfgmgr32.dll
setupapi.dll
(still to be thoroughly checked)

Though dramatically a smaller addition than the above, some 1,3 Mb uncompressed, I still think we may start googling for some alternative.

cheers.gif

jaclaz
jaclaz
The tbosdt.exe from the newish Terabyte TBOS:
http://www.boot-land.net/forums/index.php?...c=3722&st=0

Appears to be working in the reduced environent smile.gif, too bad is only a TRIAL. sad.gif

The GOOD news are that MBRwizard (version 2.00 beta):
http://mbrwizard.com/download.shtml
appears to be working as well. smile.gif

Even BETTER news are that DN /2, the Open Source evolution of Ritlabs Dos Navigator appears to work well in this! smile.gif

Here:
http://www.dnosp.com/
http://www.dnosp.com/lite/
http://www.dnosp.com/files/dn2/dnw32b16.rar

jaclaz
Dietmar
Hi all,

after one day of hard work, I succeed to implement diskpart.exe in a Mini XP SP1 with a size of 19MB.
Therefore, the registry is new build laugh.gif , oh my...
And still there is no use of shell32.dll .

Nice to hear from you
Dietmar

PS: Tomorrow I give you the new config Folder and the file list, but now I am too tired.
TheHive
Can some create the list thing into a Script project.
jaclaz
QUOTE (Dietmar @ Jan 6 2008, 02:06 AM) *
Hi all,

after one day of hard work, I succeed to implement diskpart.exe in a Mini XP SP1 with a size of 19MB.
Therefore, the registry is new build laugh.gif , oh my...
And still there is no use of shell32.dll .


GOOD news smile.gif

@Dietmar
By the way, I have seen that a few very simple windowed apps do work in this environment, but it lacks (at least in Qemu) mouse support, though some of the Registry entries for mouse are actually present in the Registry.

I had a (quick) look if I could find what was missing, but ended up empty handed.

In due time, can you have a look at this?

@The Hive
I can confirm that it works allright on a FAT filesystem, I added these entries:
(see ilko's post below)

for CDFS and FAT, just to be on the safe side, but cannot say if they are actually needed.
EDIT: confirmed to be working

jaclaz
jaclaz
QUOTE (jaclaz @ Jan 6 2008, 11:19 AM) *
@Dietmar
By the way, I have seen that a few very simple windowed apps do work in this environment, but it lacks (at least in Qemu) mouse support, though some of the Registry entries for mouse are actually present in the Registry.

I had a (quick) look if I could find what was missing, but ended up empty handed.

In due time, can you have a look at this?


Nevermind, it was a stupid typo, now mouse is working yahoo.gif:
1) Add mouclass.sys to \Windows\System32\Drivers
2) Merge this:
CODE
[HKEY_LOCAL_MACHINE\gotest\ControlSet001\Control\Class\{4D36E96F-E325-11CE-BFC1-08002BE10318}]
"UpperFilters"=hex(7):6d,6f,75,63,6c,61,73,73,00,00
@="Mouse"

[HKEY_LOCAL_MACHINE\gotest\ControlSet001\Services\Mouclass]
"ErrorControl"=dword:00000001
"Group"="Pointer Class"
"Start"=dword:00000003
"Tag"=dword:00000001
"Type"=dword:00000001
"DisplayName"="Driver classe mouse"
"ImagePath"="System32\\DRIVERS\\mouclass.sys"

[HKEY_LOCAL_MACHINE\gotest\ControlSet001\Services\Mouclass\Enum]
"0"="Root\\*PNP0F03\\1_0_21_0_31_0"
"Count"=dword:00000001
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\gotest\ControlSet001\Services\Mouclass\Parameters]
"ConnectMultiplePorts"=dword:00000000
"MaximumPortsServiced"=dword:00000003
"MouseDataQueueSize"=dword:00000064
"PointerDeviceBaseName"="PointerClass"
"ConnectMultiplePortsChanged"=dword:00000001
"ConnectMultiplePortsUpgraded"=dword:00000001


smile.gif

jaclaz
Dietmar
Hi all,

here comes the Mini XP SP1 with 19 MB NTFS compressed with working diskpart.exe.

So, here comes the registry and the full filelist of that Mini XP, thanks aeroxp biggrin.gif

Dietmar
aeroxp
Short List Format:
CODE
dir [drive:][path] /w /s>C:\filelist.txt

Replace Drive and path with your path.

Example of Syntax:
CODE
dir C:\xpcli /w /s>C:\filelist.txt


_________________

Long List Format:
CODE
dir [drive:][path] /s>C:\filelist.txt

Replace Drive and path with your path.

Example of Syntax:
CODE
dir C:\xpcli /s>C:\filelist.txt
ilko
Dietmar, great work thumbup.gif


@all-
This is working for me to have access to CDROM and FAT, tested with XP SP2 in VirtualBox, launched from FAT and NTFS, having 2 partitions (FAT and NTFS) and a CDROM:

CODE
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_CDFS]
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_CDFS\0000]
"Service"="cdfs"
"Legacy"=dword:00000001
"ConfigFlags"=dword:00000020
"Class"="LegacyDriver"
"ClassGUID"="{8ECC055D-047F-11D1-A537-0000F8753ED1}"
"DeviceDesc"="cdfs"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_FASTFAT]
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\Root\LEGACY_FASTFAT\0000]
"Service"="fastfat"
"Legacy"=dword:00000001
"ConfigFlags"=dword:00000020
"Class"="LegacyDriver"
"ClassGUID"="{8ECC055D-047F-11D1-A537-0000F8753ED1}"
"DeviceDesc"="fastfat"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\Fastfat]
"ErrorControl"=dword:00000001
"Group"="Boot file system"
"Start"=dword:00000000
"Type"=dword:00000002

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\cdrom]
"Type"=dword:00000001
"Start"=dword:00000000
"ImagePath"="system32\\drivers\\cdrom.sys"
"Group"="SCSI CDROM Class"
"Tag"=dword:00000002

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\cdfs]
"Type"=dword:00000002
"Start"=dword:00000000
"ErrorControl"=dword:00000001
"Group"="File system"
"ImagePath"="system32\\drivers\\cdfs.sys"

Don't forget to copy cdrom.sys and cdfs.sys to \system32\drivers.

Format.com and chkdsk still not working, copied autochk.exe, ulib.dll, ifsutil.dll, cfgmgr32.dll and setupapi.dll, but getting "chkdsk/format is not available for fat/ntfs drives". Any ideas what else it needs? If I launch these 2 from the CDROM with PE on it, both work.

edit: typo corrected- ImagePath in CDFS service.
jaclaz
@Dietmar and aeroxp
GOOD work, as always wink.gif, will test later.

@ilko_t
glad to see you are in the game. smile.gif

Once added the mouse support, I got EDXOR to work:
http://members.ozemail.com.au/~nulifetv/fr...eware/edxor.htm
Make a dir \edxor and put in it Edxor.exe AND the riched32.dll contained in edxorfix.exe

Add these .dlls (again list to be fully checked) LIST CHECKED:
COMCTL32.DLL
COMDLG32.DLL
OLE32.DLL
OLEAUT32.DLL
RICHED20.DLL
SHELL32.DLL
SHLWAPI.DLL

EDIT: Since the use of SHELL32.DLL, we might later find an editor without this requirement.


Type edxor in the command prompt.

Now that the system is somewhat windowed, add to the build CONSOLE.DLL.

Reboot, and you should be able to, once having started edxor, to right click on the minimized CMD.EXE window and set it up as "windowed" as opposed to "Full Screen".

Starting to fiddle with BBLEAN... rolleyes.gif

Adding a screenshot, before our friend The Hive asks for it. wink.gif

cheers.gif

jaclaz

TheHive
QUOTE (jaclaz @ Jan 7 2008, 01:54 AM) *
Adding a screenshot, before our friend The Hive asks for it. wink.gif

cheers.gif

jaclaz


tongue.gif biggrin.gif thumbup.gif
psc
QUOTE (jaclaz @ Jan 7 2008, 08:54 AM) *
EDIT: Since the use of SHELL32.DLL, we might later find an editor without this requirement.

What about using shell32.dll by FreeDOS? It's very much smaller.
(Compare PicoXP or the nativeEX_barebone cmdline version)

Peter
jaclaz
QUOTE (psc @ Jan 7 2008, 08:06 PM) *
What about using shell32.dll by FreeDOS? It's very much smaller.
(Compare PicoXP or the nativeEX_barebone cmdline version)

Peter


Yep, where is the downloadable file? unsure.gif

jaclaz
psc
QUOTE (jaclaz @ Jan 7 2008, 11:34 PM) *
Yep, where is the downloadable file? unsure.gif

Looks like that you agree: Hard to find! It is in this link, but:
It is hidden in a downloadable ISO, and you find it in this ISO as \FDOS\BIN\SHELL32.DLL (3 kB size).

[BTW]
I thought that you are the Finder whistling.gif
... we decrease the bonus points of the candidate by 1 ... innocent.gif
[/BTW]

An easier way: Freedos32's SHELL32.DLL is attached to nativeEx_Core\Basic\Build\6 - Freedos32-Resources.Script cheers.gif

[BTW]
An expert Finder should have found this, too yahoo.gif
[/BTW]

[BTW]
I today needed less than half an hour to find SHELL32.DLL at the site.
... we increase the bonus points of the candidate by 1 ... innocent.gif
[/BTW]

Peter
jaclaz
QUOTE (psc @ Jan 8 2008, 06:26 PM) *
Looks like that you agree: Hard to find! It is in this link, but:
It is hidden in a downloadable ISO, and you find it in this ISO as \FDOS\BIN\SHELL32.DLL (3 kB size).


Well, you gave a link to the FreeDOS-32 site, the question was more a rhetorical one, it took me all of five seconds (Italian ones, of course wink.gif) to find these pages:
http://updates.boot-land.net/067/PicoXP/Bu...esources.Script
http://update.boot-land.net/WinBuilder_San...esources.Script
And of course this one:
http://updates.boot-land.net/067/
QUOTE
Use dll files from the FreeDos32 project wich will replace the original big sized versions - althougth these files are compatible they will remove all graphical support to your build, only command line based apps will work.

...so my guess is that it won't be useful to Run Edxor, which is a GUI app whistling.gif

So you lose 1 Italian point for mis-linking and another Italian point for mis-representing the .dll, which rounds up to:
-2 x 1 x 2 x half-a-dozen = -24 German points w00t.gif

roll1.gif

....but you won elsewhere:
http://www.boot-land.net/forums/index.php?...=3733&st=24

cheers.gif

jaclaz
psc
QUOTE (jaclaz @ Jan 8 2008, 09:48 PM) *
Well, you gave a link to the FreeDOS-32 site, the question was more a rhetorical one, it took me all of five seconds (Italian ones, of course wink.gif ) to find these pages:
http://updates.boot-land.net/067/PicoXP/Bu...esources.Script
http://update.boot-land.net/WinBuilder_San...esources.Script
And of course this one:
http://updates.boot-land.net/067/

...so my guess is that it won't be useful to Run Edxor, which is a GUI app whistling.gif

So you lose 1 Italian point for mis-linking and another Italian point for mis-representing the .dll, which rounds up to:
-2 x 1 x 2 x half-a-dozen = -24 German points w00t.gif

roll1.gif

....but you won elsewhere:
http://www.boot-land.net/forums/index.php?...=3733&st=24

cheers.gif

jaclaz

As usual, your replies seem to be unbeatable (I say 'seem', I'm hard working on checking 'are').
I have at least a small satisfaction in your last lines.

Peter cheers.gif
jaclaz
Back to topic, I managed to get blackbox to work as shell. smile.gif

Also, miniexplorer (partially) works.

There is a lot of Registry editing/adding/fixing to do to have "base" functions like executing programs (managed to make it working) and copy/paste (NO joy yet) to work but I am pretty sure that with lots of patience it is doable.

I did not find yet a way to run Regedit/Regedt32, but command line REG.EXE appears to be working.
Good ol' RegistrarLite loads (but does not load properly the Registry) sad.gif

Next step is definitely finding a way to manage comfortably the Registry from within the booted VM, closing it, mounting the drive image, loading the hive(s) on main OS, editing them unloading and re-booting the VM is definitely a too long process.

Here are a couple screenshots of System (almost) working and of the (rarely seen before) "It is now safe to turn off your computer" screen, obtained by using the "Goodbye->LogOff" feature of blackbox.

Right now the UI is a mess as it mixes some remnants of Dietmar's (German) Registry, most standard (English) from new source and a few (Italian) text from entries I blatantly copied from my running Win2k.

I definitely need to install a base English XP and work in the same environment as that inside the VM. rolleyes.gif

cheers.gif

jaclaz




psc
QUOTE (jaclaz @ Jan 9 2008, 12:24 PM) *
Right now the UI is a mess as it mixes some remnants of Dietmar's (German) Registry, most standard (English) from new source and a few (Italian) text from entries I blatantly copied from my running Win2k.

You should use nativeEx's hiveFactory clone and build your own registry with HoJoPE.exe, using your source CD and control files describing the registry content.

Peter
Dietmar
Jaclaz,

make a try with the registry from the configfolder of the Mini XP SP1, that I put here to make Diskpart work.
Nice to hear from you

Dietmar

PS: I do not think, that the different language is the problem.
jaclaz
QUOTE (Dietmar @ Jan 9 2008, 02:40 PM) *
Jaclaz,

make a try with the registry from the configfolder of the Mini XP SP1, that I put here to make Diskpart work.
Nice to hear from you

Dietmar

PS: I do not think, that the different language is the problem.


Much better! smile.gif

Copy/Paste + Drag n' Drop now work!

Programs do not execute on double click, but that's OK I already solved it, it is a file association thingy in HKCR that I can manage by merging relevant entries.

There are three files:
IPROP.DLL
STORPROP.DLL
STREAMCI.DLL
that appear to be unneeded/DVD specific. unsure.gif

And no, different language is not a problem, of course smile.gif, I am just curious (I'll find it before or late wink.gif) where the heck are the strings "Abbrechen" and "Eigenschaften von" that come out from "Disk Properties" roll1.gif

cheers.gif

jaclaz


jaclaz
Smallish update, nothing (yet) fully replicable, but I managed to have Regedit work.

Also, both Ultradefrag:
http://ultradefrag.sourceforge.net/
and SWISSKNIFE:
http://www.compuapps.com/Download/swissknife/swissknife.htm
(the version inside http://files.compuapps.com/us/swissknife/C...nife-BartPE.exe i.e. the "BartPE" version)

work! yahoo.gif

jaclaz
jaclaz
Summing up these last days experiences, I think we must re-formulate goals and expectations for this project.

We must "fork" it in two main development paths:
1) WinCLIBR
(i.e. Base Recovery, based on first posted files from Dietmar.)
This with:
Mouse support
NTFS, FAT and CFDS support
Dos Navigator (about 1.5 Mbytes)
blackbox (about 300 Kb)
Swissknife (about 3 Mb)
A number of smallish utilities, say Nirsoft ones + various ones like MBRfix/MBrwiz and the like, say another 2 Mb
Can stay below 30 Mb, maybe 20, which is what I personally find as a reasonable size for this kind of build, having all the functionalities of the Recovery Console, but with a file navigator (VERY fast, NC-like) smile.gif and a graphical partitioning utility.

The missing step is a Registry manipulating utility, the excellent
Native Registry Editor by Dan Madden:
http://www.codeproject.com/KB/applications/NtRegEdit.aspx
http://www.codeproject.com/KB/system/NtRegistry.aspx
works as a charm, I used the "VC++6.0" version as it was the most "compact one" with:
NTRegedit.exe 312 kb
aclui.dll 105 kb
Msvcp60.dll 393 kb

problem is, it still misses the Load/Unload hive capability, which is of course needed in Recovery Environment.

(I will try to contact Mr. Madden to see if he is interested in adding this feature) smile.gif

Making default Registry Editor working is, besides rather difficult, incredibly space-hungry, unless I am mistaken, getting it to work adds to the build something like 17 Mbytes of related files and dependencies.

On the other hand, still below 100 Mbytes:

2) WinCLINL
(i.e. No Limits based on second sets of files by Dietmar)
Same as above, with normal Regedit, full clipboard/OLE support, almost ANY app running or installable.

The great advantage of such a system as compared to the various PE based ones is that it is a writable system, thus you do not need to re-build, you just add applications (almost) the normal way. If an app does not work, you fire up Dependency Walker and/or Regmon/Filemon and add the missing file or Registry entry.
I have seen in these days that, as expected, once you have resolved the "base" dependencies for a number of programs, each subsequent one you try needs less and less work to be made working.

And of course here comes the request to Dietmar (I know he is waiting for it and I don't want to disappoint him):
Can we have this thingy bootable from USB? wink.gif

And one for Euhenio, Bilou_gateux or for anyone with experience with RamDisk:
Can we have this thingy bootable from Ramdisk using the Server 2003 SP1+ files? wink.gif

cheers.gif

jaclaz
Dietmar
Hi jaclaz,

you are right, I also thought about the possibilty of USB and ram boot.

This can be done easily.

I post this in a few days, when there is no school in germany for 4 days.

Nice to hear from you all

Dietmar
MedEvil
@jaclaz
I'm a bit confused at the moment, care to help me out? wink.gif
Up to this point i thought the goal of this project was to create the smallest XP possible.
But when i read your last post, i see this project play, size wise, in the same category as, for instance, nativeEx_barebone.

So what is the potential advantage of a OS based on this project over a PE one?

cheers.gif
dog
@MedEvil
QUOTE
The great advantage of such a system as compared to the various PE based ones is that it is a writable system, thus you do not need to re-build, you just add applications (almost) the normal way.

Although if it boots to ram, the re-building is back, I suspect.
jaclaz
@dog

Yes, of course, with some, I think, still residual advantages nonetheless, I mean, for example, being able to actually test an app BEFORE re-building and only rebuild once and IF results are satisfying.
But RAM booting is probably a requisite for the people that have hardware that generates 0x000007b BSOD when booted from USB.

@Medevil
I may add to the part dog quoted, as you can see from my post, that I vouch for a fork of the project, one still aimed to the smallest having practical utility* one, and the other to a more feature-filled build.

jaclaz

* I mean, and no offence intended for anyone smile.gif that there are a few projects around, that are more a "proof of concept" than anything, this (the BR one) can be something you can "stick" (pardon me the pun) on your 16 Mb or 32 Mb USB stick wink.gif, yes the one you bought for some 40 US$ some four years ago or the one that you got as a promotional gift a few weeks and that you put in a drawer of your desktop, not knowing what to do with it, and have a handy Recovery environment much better than Recovery Console.

MedEvil
Sorry, dog, jaclz, but i seem to be a little slow today.
Isn't PE already able to run from ram?

cheers.gif
jaclaz
QUOTE (MedEvil @ Jan 15 2008, 04:19 PM) *
Sorry, dog, jaclz, but i seem to be a little slow today.
Isn't PE already able to run from ram?

cheers.gif

Well, today is a new day, the sun is shining (actually NO, I am lying wink.gif, right now it is raining cats and dogs, but the image of a blue sky with a bright sun helps smile.gif).

I hope you feel "faster" today, but it's my turn to be "slow".

I cannot see the relevance of your comment. unsure.gif.

I mean, what gives? wacko.gif

Also DOS, Win9x/ME, Linux and probably a few tens of other lesser known Operating Systems are "already able to run from ram".

Would this be a reason why this thingy we are discussing here should not? blink.gif

I got the impression (hopefully being totally wrong) that you perceive this XPCLI to be somehow a "competitor" of some kind to PE.

This is not, at least for me, the general idea.

I see it as an alternative, with some advantages (and, quite obviously, some shortcomings) to ANY other bootable environment.

I mean IF it is possible, why not try using it?

cheers.gif

jaclaz


MedEvil
QUOTE (jaclaz @ Jan 16 2008, 12:20 PM) *
I see it as an alternative, with some advantages (and, quite obviously, some shortcomings) to ANY other bootable environment.

Ahh, finally we're getting somewhere.
An alternative makes only sense if it is different in some way. Why should anyone else spend time on reinventing the wheel exactly like it already exists?

So what are the advantages, that would make this project an alternative to the already working PE projects?

If it is only different and has nothing but disadvantages, tell me and i won't bother you again. wink.gif

cheers.gif
jaclaz
@Medevil
Listen, I have already clearly stated what I think of it, just read it.

Then you may agree or disagree with my ideas, and on what I find an advantage or disadvantage, but what is the point of asking for the THIRD time the same thing (that is already here) ?

Re-read, slowly, posts #32, #35, #36 :
http://www.boot-land.net/forums/index.php?...=3717&st=31

I have nothing to add to them.

If you want to start a "philosophical" discussion of the type "NTFS vs. FAT32", "Win98 vs. XP" or, in this case, "PE vs. XPCLI", you are very welcome to do so, start a new thread, please.

jaclaz

dog
QUOTE (jaclaz @ Jan 13 2008, 05:45 PM) *
Smallish update, nothing (yet) fully replicable, but I managed to have Regedit work.


Can you post your file list, and config dir?
Seems a shame to re-invent the wheel biggrin.gif
jaclaz
QUOTE (dog @ Jan 17 2008, 12:12 PM) *
Can you post your file list, and config dir?
Seems a shame to re-invent the wheel biggrin.gif


Well, not yet, the method I used is a bit "unconventional" and I still have to resolve some of the problems, but I will post something soon, promise-

Basically I did MISTAKE #1 wink.gif Added too many things together without properly documenting the steps and I have now a Registry with redundant entries, some unneeded files and more generally something that I cannot remember how I made. sad.gif

I am re-working step by step to see if I can produce something replicable.

Problem is with the Registry, I did something tha made things work and I cannot find what it was....

About the wheel, you appear to be part of the less historically aware people wink.gif:
http://www.boot-land.net/forums/index.php?...c=2037&st=8
roll1.gif

cheers.gif

jaclaz
jaclaz
GOOD NEWS smile.gif:

Dan Madden, the author of NTRegEdit, is interested in the project and will see if he can add the missing features to his app:
http://www.boot-land.net/forums/NTRegEdit-...itor-t3782.html

jaclaz
dog
Trying NtRegEdit.exe I get "The system cannot execute the specified program."
Is this something you documented solving tongue.gif ?
jaclaz
QUOTE (dog @ Jan 18 2008, 02:25 PM) *
Trying NtRegEdit.exe I get "The system cannot execute the specified program."
Is this something you documented solving tongue.gif ?


Should just be these:
NTRegedit.exe 312 kb
aclui.dll 105 kb
Msvcp60.dll 393 kb
but maybe you miss MFC42.DLL (which is needed anyway for SWISSKNIFE)
or some of the other files I added for Edxor, OLE32.DLL COMDLG32.DLL, whatever

Run Dependency Walker:
http://www.dependencywalker.com/
on it, you should have just the "direct" dependencies OK.
The delayed ones (the ones that get a hourglass near the name) should not be needed)

jaclaz
thunn
Somewhere in here is the base for a proper non pe XP inram, under 100 MB., which is what I seek to offer wb users. Up to now getting the win root under 100MB. and keeping all need functions has been difficult so I also started from scratch, once again.. XpSp2 btw.
Peters comment about using his hojo app should be taken into consideration.
Psc,
can you please PM me or post us a little example of how to configure a test environment using hojo? smile.gif
MedEvil
QUOTE (thunn @ Jan 20 2008, 08:59 AM) *
Somewhere in here is the base for a proper non pe XP inram, under 100 MB., which is what I seek to offer wb users. Up to now getting the win root under 100MB. and keeping all need functions has been difficult so I also started from scratch, once again.. XpSp2 btw.
Peters comment about using his hojo app should be taken into consideration.
Psc,
can you please PM me or post us a little example of how to configure a test environment using hojo? smile.gif

Cool, we're again on the same quest! hyper.gif
No idea what functions you wanna keep in your XP, but the difference, size wise, between a true XP and a PE with the same features, is not worth speaking of.
I would guess that PE is at best 1 or 2 MB bigger.

cheers.gif
jaclaz
OK, peeps smile.gif

I somewhat managed to create a replicable situation. yahoo.gif

My .script developer friends, and expecially psc will pardon me if I did not use Winbuilder, but I simply have not the time to learn how it works, and besides, seeing how UGLY and INCONVENIENT is the "Building Environment" I put together will make some of them want to create a proper WB project for this thingy here. wink.gif

Please find attached two .zip files:
first one containing the directory listing of the build environment folder, both as a "normal" DIR /S and as a DIR /B /S
second one containing the "custom" files needed.

Instructions (BRIEFLY):
1) Unzip files to a work directory (Please only paths WITHOUT spaces!)
2) Run XPcliLST.cmd
3) Open with Notepad the produced aXPCLI.lst file and see if what is in there makes sense
4) Use the two DIR files to get an idea what and where "third party" files are needed and place them accordingly (links to the various apps are in my previous posts)
5) Please make sure you do not overwrite the .rc files in the bblean directory
6) Run MK_XPcli.cmd and see if it throws any error ( check ATTENTIVELY the xpcli.log that will be made in \ROOT\ directory)
7) Create a bootable disk image suitable for Qemu, I am using a 100MB one, format it as NTFS, mount it in IMDISK or VDK and copy to it the contents of \ROOT\ directory, unmount it
8) Run Qemu with the image and start experimenting...smile.gif


NOTES:
The Registry files within the attachment in \BaseRegistry\ are first release of Dietmar's files with the "patches" for mouse, CDFS and FAT support already merged, a copy of the original ones are in \BaseRegistry\XPCLIBR_Dietmar\

To start Blackbox, simply run the bb.cmd.

As an example in the generated aXPCLI.lst file the entries for Edxor are commented:
CODE
#To add Edxor
#WINDOWS\Edxor.exe  
#WINDOWS\riched32.dll  
#WINDOWS\system32\comctl32.dll  
#WINDOWS\system32\comdlg32.dll  
#WINDOWS\system32\ole32.dll  
#WINDOWS\system32\oleaut32.dll  
#WINDOWS\system32\riched20.dll  
#WINDOWS\system32\shell32.dll  
#WINDOWS\system32\shlwapi.dll


you must uncomment them:
CODE
#To add Edxor
WINDOWS\Edxor.exe  
WINDOWS\riched32.dll  
WINDOWS\system32\comctl32.dll  
WINDOWS\system32\comdlg32.dll  
WINDOWS\system32\ole32.dll  
WINDOWS\system32\oleaut32.dll  
WINDOWS\system32\riched20.dll  
WINDOWS\system32\shell32.dll  
WINDOWS\system32\shlwapi.dll

to have it working.

Also, MiniExplorer is NOT implemented, although an entry in BlackBox menu.rc is present, adding it is left as an exercise to the reader. whistling.gif

Have fun! tongue.gif

jaclaz
dog
It works! thumbup.gif
I'm not getting a mouse cursor on vmserver, but I'll look into that later.
I also found that launching blackbox left a "hung" cmd window, which I couldn't kill without a mouse, so I changed the cmd to
CODE
start blackbox
exit


Cheers for the nice scripts, not at all ugly cheers.gif
jaclaz
QUOTE (dog @ Jan 21 2008, 05:25 PM) *
It works! thumbup.gif
I'm not getting a mouse cursor on vmserver, but I'll look into that later.
I also found that launching blackbox left a "hung" cmd window, which I couldn't kill without a mouse, so I changed the cmd to
CODE
start blackbox
exit


Cheers for the nice scripts, not at all ugly cheers.gif


Not having a "real" unmodified XP 2600 installed anywhere, I have no way to understand what mouse driver is used, so I used the mouclass.sys that is on my working W2K PC, which comes from Microsoft anyway, adding it the \ADDONS\ folder, it seems like there is not a mouclass.sy_ on the XP CD, of course the entries in Registry are for that driver, you might want to change the mouse.reg accordingly and add the right file to aXPcli.lst.

Maybe that is the problem. unsure.gif

jaclaz
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2008 Invision Power Services, Inc.