288 replies to this topic

[betrand]

I found one here. Have no idea if it works; it's for Pe, but I'll try (editing) anyway.

http://www.400gb.com...877c43d275.html

[betrand]

Yeah, it works. Need to edit to system instead of pe.

Will post it for future ref.

 

I need a kqemu.reg. Can someone post? thanks.

Also, looking for ntvdm.reg.

 

Nuno, you mention in antother thread qemu on picoxp not really fast. Why not?

 

thank you.

[betrand]

Nuno, you mention in antother thread qemu on picoxp not really fast. Why not?

 

thank you.

Sorry, misread.

 

http://reboot.pro/to...one/#entry36912

Yes, you can use it for that task although qemu will be extremely slow on the task of installing XP.

Better use VirtualBox for this goal to enjoy much quicker XP install.

[betrand]

Yeah, it works. Need to edit to system instead of pe.

Will post it for future ref.

Tada.

 

I think Wonko's modular approach is a good idea.

You can really have a small base system and the rest (the fun stuff)

in other place.

 

 

 

Can't find an xp Kqemu.reg, just a win98  for a MurgaLinux thingy.

Probly 'll need to study regwrite..

Attached Files

•  imdisk.reg   6.29KB   652 downloads

[Wonko the Sane]

Can't find an xp Kqemu.reg, just a win98  for a MurgaLinux thingy.

Probly 'll need to study regwrite..

Here, kid , take my hand and I will try to have you cross the road safely....

 

Wonko

Attached Files

•  Kqemu_regshot2.zip   5.22KB   576 downloads

[Louis XV]

How can I make an auto execute script (like autoexec.bat for DOS) with this version?

[betrand]

How can I make an auto execute script (like autoexec.bat for DOS) with this version?

 

Good use for Xpcli. I would look in Regedit for the reference to Shell= cmd.exe (or similar).

Replace "cmd.exe" with a batch. I did something similar in the past.

Play with that idea, I remind you that the batch mightn't stop until the program (autoexecuted)

has stopped (only if you make a 'correct' batch file).

 

 

Btw, I found a small 'glitch' with Xpcli. I created a (small) file called test.img on a hard drive. Renamed to test.

On reboot grub listed test.img. Can't remember if the booted system said test or test.img.

I am thinking this might be because the XPCLI has no "shutdown" so you hard shutdown.

 

Now, Rebooters, a question.

How do I change the Rambooted Xpcli sysdrive from C: to D: or R: or X: ? Thank youu!

[betrand]

Glitch confirmed.
Open notepad.
Save-as 1.txt.
Close notepad.
Rename as 1 (or whatever).
Reboot, with power button.
Boot to grub4dos.
ls /1 (tab)

It shows 1.txt on my setup. Same if you write something in the
file afterward. It doesn't save the last thing.

I am using the MiniXP build (Misty), booted to ram (c:).
Hd is normal IDE HD. Grub4dos is of Feb 2013 I think.

Good to know if you are doing "important" stuff. Writing a book for e.g. :whistle:

I know the shutdown thing (patch /.reg) was mentioned in a prev. post. Also if using another build
(Xpcmd) it probably is allright. (edit: as they have the gui)

 

Edit: also goes without saying the booted system's file is then also the original file, with no rename or changes (when it should be different).

 

Edit: This is probably an NTFS write delay thing. Use (20kb) shutdown.exe would solve the thing.

[erwan.l]

Hello Gents,

 

I have decided to play a bit with this XPCLI project.

 

Thus I am puzzled with what is the best way to handle the "Application Error - The application failed to initialize properly (0xc0000142)" ?

I can use Dependency Walker and also Process Monitor still for most apps I am stuck

 

I got as far (XPSP2 based) as enabling mouse/cdfs/fat, format.com, regedit but cannot seem to go any further ...

 

And for regedit I feel I succeeded only by luck by copying : 

x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.0.0_x-ww_1382d70a and 

x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9

in windows\winsxs folder.

 

Can anyone direct me to a proper and effective method to find all dependencies needed by a program?

 

Second and last question : has anyone tried to enable network in XPCLI? TCPIP would be quiet handy to transfer datas.

 

Attaching my registry base (from Wonko post #48) and a modified script from post #6

 

Regards,

Erwan

Attached Files

•  config_basic2.zip   91.08KB   505 downloads
•  D123_XP.cmd   6.16KB   694 downloads

[betrand]

@Erwan, http://reboot.pro/to...e-9#entry154017 ?

[erwan.l]

@Erwan, http://reboot.pro/to...e-9#entry154017 ?

 

Thanks Betrand, will look at it.

 

In the meantime I succeedeed in running CloneDisk in XPCLI : most functions seems to work (i can create a disk, a partition, format, etc).

XP size = 30 mb.

 

I had to review my code thus to make it work (use dynamic link wherever possible vs static link).

Attached Thumbnails

• 

[Wonko the Sane]

 

 

Attaching my registry base (from Wonko post #48) and a modified script from post #6

WHY?

 

I mean:

Post #48 includes a rudimental "builder" that works "as is".

Post #50 adds instructions for the mouse.

Once you have built the very minimal project with the above, you can add anything else later manually)

 

Why mixing them with the original command in #6 (which is to be considered outdated)?

 

And BTW the whole batch based process is now outdated (and only good for reference) and made much more easy by the nice little Winbuilder project by Misty:

http://reboot.pro/topic/16765-minixp/

http://minixp.reboot.pro/

which also provided some "logically ordered" documentation and links to the relevant posts on this topic.

BTW links provided by Misty, like here:

http://minixp.reboot...les/develop.htm

have been once again "botched" by the nth stupid board update.

 

A link like:

hxxp://reboot.pro/3717/page__view__findpost__p__151904

need to be changed into:

hxxp://reboot.pro/topic/3717-xpsp1-with-full-commandline-and-ntfs-below-10-mb/?p=151904

or:

hxxp://reboot.pro/topic/3717-/?p=151904

or:

hxxp://reboot.pro/topic/3717-xpsp1-with-full-commandline-and-ntfs-below-10-mb/#entry151904

 

Wonko

[erwan.l]

WHY?

 

I mean:

Post #48 includes a rudimental "builder" that works "as is".

Post #50 adds instructions for the mouse.

Once you have built the very minimal project with the above, you can add anything else later manually)

 

Why mixing them with the original command in #6 (which is to be considered outdated)?

 

And BTW the whole batch based process is now outdated (and only good for reference) and made much more easy by the nice little Winbuilder project by Misty:

http://reboot.pro/topic/16765-minixp/

http://minixp.reboot.pro/

 

Wonko

 

I am not too much into winbuilder scripts (too lazy to get into it).

 

And I like the idea of using the most simple base where I can add my stuff onto it.

Hence me using your original registry (which includes mouse/fat/cdrom) AND the batch file where I can add my own lines.

 

This way I too call feel the pain, sweat blood and by the end of day feel like I had fun and eventually learned something.

 

I am now struggling adding ramdisk support and my next drive would be TCPIP running.

 

Only experimenting there and sharing, on a lazy / rainy sunday !

[Wonko the Sane]

Sure , but the batch file in post #48 "MK_XPcli.cmd" and the directory structure should anyway allow experimenting much better than the one in post #6 "D123_XP.cmd".

 

That is what I was trying to tell you (besides recommending - at least as a useful reference - the nice thingy by Misty)

 

Wonko

[erwan.l]

Sure , but the batch file in post #48 "MK_XPcli.cmd" and the directory structure should anyway allow experimenting much better than the one in post #6 "D123_XP.cmd".

 

That is what I was trying to tell you (besides recommending - at least as a useful reference - the nice thingy by Misty)

 

Wonko

 

Thanks for pointing this out : i have indeed missed that batch (looking at it right now).

 

To be fair, that thread is quiet lengthy and it took me quiet some reading back and forth to get me started.

 

Invaluable informations thus : in a few hours I was able to get my xpcli running under 32mb with a few softwares in there :

-devmanview

-driverview

-regedit

-clonedisk

etc

 

Now I want to pxe boot it (ram disk) and am looking for ramdisk or firadisk .

If ramdisk works, it should be easy to move on to usb/portable media.

 

Next step would be networking.

 

Regards,

Erwan

[Wonko the Sane]

 

Now I want to pxe boot it (ram disk) and am looking for ramdisk or firadisk .

If ramdisk works, it should be easy to move on to usb/portable media.

And again, check the MiniXP by Misty, which includes a working setup for WinVblock, both as Ramdisk and as Filedisk (besides a list of files and as said, a well ordered set of preliminary documentation)

The good thing with batch files (but also with winbuilder scripts) is that it is relatively easy to "extract" from them the informations needed for use in another kind of script.

 

Wonko

[erwan.l]

Tried MiniXP.

 

Just brilliant

And it does boot over PXE (ramdisk).

 

Love it !!

 

Thanks Wonko for pointing this out, Thanks Dietmar, Thanks  Misty.

[misty]

@Wonko
Thanks for the publicity!

Tried MiniXP....Just brilliant ...Thanks Wonko for pointing this out, Thanks Dietmar, Thanks  Misty.

@erwan.l
It's a pleasure. Thanks for the positive feedback. MiniXP was a great distraction during a difficult time - I hope you have as much fun playing around with this project as I did.



Regards,

Misty

[Wonko the Sane]

@Wonko
Thanks for the publicity!

It's not "publicity" , it is much more than that, it is outright "endorsement" .

 

It is however well deserved , and, indirectly, has a second scope.

 

The real issue with this thingy here is the difficulty in finding other kids wanting to play this game and whenever a kid, particularly one with the capabilities/knowledge of erwan.l  happens to manifest this intention, I do the most I can to get him/her "addicted" to it.

 

Wonko

[erwan.l]

It's not "publicity" , it is much more than that, it is outright "endorsement" .

 

It is however well deserved , and, indirectly, has a second scope.

 

The real issue with this thingy here is the difficulty in finding other kids wanting to play this game and whenever a kid, particularly one with the capabilities/knowledge of erwan.l  happens to manifest this intention, I do the most I can to get him/her "addicted" to it.

 

Wonko

 

Been 20 years I was not called a kid : this will make this day a good day

 

About the minixp concept, I really like it to test my softwares : this is the best way to hunt/kill dependencies and to make my software less fat.

 

Second objective of course is to have a tiny booting xp for support purposes : retrieve offline files, modify offline registry, fix boot, etc.

 

Side note, I see that the dll proxy concept was not discussed in that thread (or was it?) : I experimented this with some success in the past.

Idea being to built a dll exporting empty functions.

Result is a lightweight (couple of KB) DLL tricking a software statically linked and helping to keep minixp light.

 

Regards,

Erwan

[Wonko the Sane]

Glad to have contributed to make your day a good day .

 

The matter of "fake" dll's has been (lightly) touched in the past, here:

http://reboot.pro/to...-10-mb/?p=27177

 

Though as I see it, the main issue (not yet solved) is to find a replacement for the minlogon.

 

Besides being a "fun" game to play, I find the XPCLI (either the most minimal command line only "base" or the GUI larger "fork") exactly what the Recovery Console should have been (since day one) and, while possible, not so much a "portable" solution, for which a PE has anyway some advantages.

BTW, one of the interesting outcomes (as well with very few or no kids wanting to play on it) of the thread has been the findings about "hybrid" PE's, i.e. PE's that have a more completely formed setupreg.hiv and that can be booted (faster) through NTLDR:

http://reboot.pro/to...10-mb/?p=154101

http://reboot.pro/to...e-fast-boot-pe/

 

And now, for NO apparent reason, some unrelated news (or maybe not really news ).

The Vista and later can use a "new" kind of link, a symbolic link for files that may open some new possibilities, but it exists an installable driver for XP which can use them:

http://schinagl.priv.at/nt/ln/ln.html

http://schinagl.priv...nksforwindowsxp

 

Also, oldish thread with IMHO more than a few points of interest:

http://reboot.pro/to...em-redirection/

 

 

Wonko

[0ffer]

Recovery Console should have been (since day one) and, while possible, not so much a "portable" solution

Recovery Console portable for USB flash & HDD
for his
install Recovery Console
In cmdcons\system32 make two directory

drivers and config with 2 zero sized files: sam & security
boot it from windows 7 bootmgr
in root directory:
ntdetect.com
cmldr(renamed setupldr.bin)
boot.ini

[boot loader]
default=c:\cmldr
timeout=-1
[operating systems]
c:\cmldr="Windows Recovery Console" /cmdcons

always logon cmdcons not windows!

Edited by 0ffer, 02 October 2014 - 05:22 PM.

[Wonko the Sane]

Recovery Console portable for USB flash & HDD

Sure , remember to post this also in "News".

There are several threads on reboot.pro ABOUT the Recovery Console and several different methods to create one, and you manage to post this info in a thread which is NOT ABOUT it?

http://reboot.pro/to...covery-console/
http://reboot.pro/to...covery-console/
http://reboot.pro/to...from-usb-stick/

Latest/most convenient method (IMHO) JFYI:
http://www.911cd.net...showtopic=24880

And, also JFYI, the Catch22 trick:
http://www.911cd.net...pic=20983&st=25


Wonko

[0ffer]

For dual booting XPCLI & RC

boot.ini for bootmgr without editing bcd file


[operating systems]
c:\cmldr="Windows Recovery Console" /cmdcons
c:\windiag="Windows Memory Diagnostic"
c:\ntldr=="Microsoft Windows XP menu"
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP1 Dietmar's CLI" /sos /NOEXECUTE=ALWAYSOFF

I have tried without success XPCLI created by cmd script & winbuilder on my HP 6820s in IDE mode (disabled SATA in BIOS)
USB Flash Drive 4Gb formatted FAT32 minlogon 24 384
BSOD only regardless file system NTFS or FAT32 on USB flash, XP sp1 or sp3

In winbuilder only core components

Edited by 0ffer, 02 October 2014 - 07:14 PM.

[Wonko the Sane]

BSOD only regardless file system NTFS or FAT32 on USB flash, XP sp1 or sp3

In winbuilder only core components

BSOD means NOTHING.
WHICH BSOD?
WHICH STOP ERROR?

WHICH Winbuilder project did you test?
The recommended one is MiniXP by Misty:
http://minixp.reboot.pro/


Wonko