66 replies to this topic

[Brito]

I've sent a reply to your email about this question - please post your results here - thanks!

[AeroXP]

Update: Windows XP RamBoot in a 2.88M Floppy Disk!
Link to Download
Uses LZX Cab Compression and Driver Stubbing!

-----------------------------------------------------
Script Devs, Can you help me here?

( ºsedir% = % basedir %)

cabarc -m LZX:21 n  %iso%\RamBoot.is_ %iso%\ramboot.iso -> [insert script version here]md ºsedir%\ramboot -> [insert script version here]...move %iso%\RamBoot.is_ ºsedir%\ramboot > [insert script version here]

[Brito]

Impressive results!

Let's automate them, maybe something like this would help you:

ShellExecute,Hide,"cabarc.exe","-m LZX:21 n #$q%isodir%\RamBoot.is_$%q $%q%isofile%#$q"

DirMake,"%isodir%\RamBoot"

FileCopy,"%isodir%\RamBoot.is_","%isodir%\RamBoot\RamBoot.is_"

FileDelete,"%isodir%\RamBoot.is_"

Haven't tested but should help you get an idea of how it works.

There's a valuable help to learn your way around these codings:

• 1 - open up wb and click on the edit button on the script you wish to modify.
  
• 2 - Go to the Source tab and you should see a source code editor.
  
• 3 - The last icon is a "Magic wand" - clicking it should give you a detailed list of available commands.

You can also use as reference the syntax manual --> http://boot-land.net...ipt_syntax.html

If you print the above page then it will help you whenever needed to learn exactly what each command does.

[thunn]

aeroxp,
although I've only opened the image and had a quick peek, it seems like your working on something very worth while. It could, perhaps, help full platforms boot faster too.
.. nice work! .. nice progress bar.

[Brito]

Been playing around the Recover Console lately and it is very similar to the files used by WinRoot.

Is it possible to launch the recovery console instead of the TinyKrnl binary?

At the moment the only way to have a standalone Recovery Console is wrapping around setupldr.bin and this is not a direct solution.

[AeroXP]

If you do try, setup will want even more binaries.

[Brito]

Hmm..

I've installed XP under a virtual machine (Virtual Box) to later apply the Winnt32.exe /CMDCONS switch from the install CD.

As result - the rescue console is called directly from boot.ini on disk.

Under a read-only media it seems trickier to get the same option.

Will keep testing and let you know if I make any progress.

btw: Looked on my USB HDD archive and haven't found the FreeDos image created earlier - will have to look on the older DVD archive to see if it was stored there but this takes a bit longer since it is very disorganized.

[AeroXP]

btw: Looked on my USB HDD archive and haven't found the FreeDos image created earlier - will have to look on the older DVD archive to see if it was stored there but this takes a bit longer since it is very disorganized.

Thanks, Nuno Brito!

[thunn]

As result - the rescue console is called directly from boot.ini on disk.

Under a read-only media it seems trickier to get the same option.

Will keep testing and let you know if I make any progress.

Please see:
http://bartpe.boot-l...ls/GRLDR_NT.cab

Some configuration suggestions may be found via links in a readme I included.
The file is there for use with the BcdwPE.script and contains a grub4dos boot loader with an embedded menu file that auto loads boot.ini from any media supported by grub4dos. I use it to run a reduced 'full' XP on the go in system Ram or from hdd/usb.

Also there's related info. on this page: 'XPnRam'
The above boot loader can be used for a universal raw image for placing on cd/hdd/usb, etc. with minimal formating changes. If it helps, please test and report.

[Brito]

hmm... interesting indeed - would the use of boot.ini be the solution for this case?

Will try!

[was_jaclaz]

Cannot say if it may help, but do check this:
http://www.boot-land...?...c=2362&st=4
http://www.boot-land...?...c=2362&st=7

(how to directly load Recovery Console from bootsector)

jaclaz

[Alex Ionescu]

Just to mention something, you don't need to edit the kernel to change the boot logo anymore...

As of Windows 2003, you can tell NTLDR to display a BMP during the boot, which will show up even before the kernel starts loading.

[AeroXP]

/BOOTLOGO
Use this switch to have Windows XP or Windows Server 2003 display an installable splash screen instead of the standard splash screen. First, create a 16-color (any 16 colors) 640x480 bitmap and save it in the Windows directory with the name Boot.bmp. Then add "/bootlogo /noguiboot" to the boot.ini selection.

[MedEvil]

/Bootlogo does not work with PE.

[AeroXP]

To my surprise, "devtree" acts a little like a native version of Target Analyzer Probe.

Pci Root Bus

   PCI HOST Bridge

   IDE Controller

	 IDE channel

	   Virtual HD

	Video Controller (VGA Compatible)

	Ethernet Controller

ISA timer

ISA DMA

PCAT_ENHANCED

Parallel output only

XT Serial

XT Serial

Floppy Controller

Other system device

ISA RTC

RAM memory

Other system device

Other system device

Other system device

MICROSOFT PS2 MOUSE

[Alex Ionescu]

To my surprise, "devtree" acts a little like a native version of Target Analyzer Probe.

Pci Root Bus

   PCI HOST Bridge

   IDE Controller

	 IDE channel

	   Virtual HD

	Video Controller (VGA Compatible)

	Ethernet Controller

ISA timer

ISA DMA

PCAT_ENHANCED

Parallel output only

XT Serial

XT Serial

Floppy Controller

Other system device

ISA RTC

RAM memory

Other system device

Other system device

Other system device

MICROSOFT PS2 MOUSE

Yep, and it can be made even better by using some other NtPnP calls..

[AeroXP]

After a long time, NCLI finally works on Windows Whistler 2462!

RapidShare Link

[was_jaclaz]

Can't say if it's of any use , but it seems that UltraDefrag:
http://ultradefrag.sourceforge.net/

has, besides the CLI and GUI apps, a NATIVE version .

jaclaz

[AeroXP]

I added the files and when It launches, it makes the command portion lock up.

----

offtopic:

A new platform for WinBuilder!

[Alex Ionescu]

I don't really like the way their native app works...

- Broken, insecure string functions
- KeyboardClass0 assumptions
- Outdated, wrong native headers

It doesn't even link with nt.lib like it should, so they implement their own NtProcessStartup...

[pscEx]

@Alex Ionescu
@aeroxp

when seeing you discussing here, I'm getting headache. As already posted at a different place: I know that I do not know anything.

But this dicussion makes me unsatisfied and crazy.

Since a while I'm trying to go into the secrets of native API, but w/o success.

As I could read at Alex's blog, M$ does not publish anything usable.
When trying the OpenSource TinyKernel, I got the informatino that it is not longer supported >> no source samples
When trying Alex's Google storage, I found th project description, but no source code stored.

For Alex and aeroxp, which may not know me:
I'm an experienced programmer since more than 30 years. My knowledge (and built projects) ranges from DEC PDP11 assembler and x86 assembler to ... .NET

I also googled and stored the complete native API reference in my PC

But I do not want to reinvent the wheel, by e.g. open a file given by name.

Here your publications may be very helpful.

Is it possible to have an 'inofficial alpha' set of your OpenSource (closed TinyKernel or candidate to publish native-nt-toolkit) here?

Peter

[AeroXP]

Here is the source that compiles correctly for me.
 tinynightly.7z   2.09MB   746 downloads

--
NtDll Status: Boots up to black screen.

[pscEx]

Here is the source that compiles correctly for me.
 tinynightly.7z   2.09MB   746 downloads

--
NtDll Status: Boots up to black screen.

Thanks, aeroxp!

I think that you'll not hear me for several hours / days, until I've read and understood all the sources

Peter

[Alex Ionescu]

See inline.

@Alex Ionescu
@aeroxp

when seeing you discussing here, I'm getting headache. As already posted at a different place: I know that I do not know anything.

But this dicussion makes me unsatisfied and crazy.

Since a while I'm trying to go into the secrets of native API, but w/o success.

>>> Have you tried reading "Windows Internals 4th Edition", "Undocumented Windows 2000 Secrets: A Programmer's Cookbook", the WDK, and "Native API Reference"? If not, then you have no business complaining...

As I could read at Alex's blog, M$ does not publish anything usable.

>>> The WDK documents over 30-50 native system calls. SysInternals has a bit of information that's quite useful for understanding the system.

When trying the OpenSource TinyKernel, I got the informatino that it is not longer supported >> no source samples
When trying Alex's Google storage, I found th project description, but no source code stored.

>>> As I already said numerous times, I just *Started* that storage. I've been *working* for the last 3 weeks abroad, and still work on a daily basis from home... I will post it soon...

For Alex and aeroxp, which may not know me:
I'm an experienced programmer since more than 30 years. My knowledge (and built projects) ranges from DEC PDP11 assembler and x86 assembler to ... .NET

I also googled and stored the complete native API reference in my PC

>>> Did you STORE it or also READ it?

But I do not want to reinvent the wheel, by e.g. open a file given by name.

>>> Huh? NtCreateFile?

Here your publications may be very helpful.

>>> My publications won't help with information that's already documented by Microsoft in the WDK.

Is it possible to have an 'inofficial alpha' set of your OpenSource (closed TiniKernal or candidate to publish native-nt-toolkit) here?

>>> I'm not legally allowed to publish TinyKRNL anymore...and the native-nt-toolkit is made up of the NDK (which is already in ReactOS), the NDL (unreleased) and the NCLI (already released and being distributed). However it won't help you understand anything unless you read up what I suggested

Peter

I don't want to make it sound like I'm being unhelpful, but before saying you're "angry" and "disappointed" maybe you should read the documentation and tools that are already available out there.

[pscEx]

I don't want to make it sound like I'm being unhelpful, but before saying you're "angry" and "disappointed" maybe you should read the documentation and tools that are already available out there.

That's what I demand from anybody else. And that's what I do before asking for help.

In this particular case you really have much more technical knowledge than me.
But due to social behaviour, maybe you can learn something from me:
Please have a look at my signature:
There are never stupid questions, there can be only stupid answers.

You may check all of my posts.
On newbees' questions, I every time have been cooperative and helpful, never ironic or 'telling them how stupid they are'

Yes, I did read a couple of the doc mentioned.
Some:

>>> Have you tried reading "Windows Internals 4th Edition", "Undocumented Windows 2000 Secrets: A Programmer's Cookbook", the WDK, and "Native API Reference"? If not, then you have no business complaining...

Googleing I ony found the "Native API Reference".
But either I'm too stupid, or it is missing here: For me I found no answer, how to open a file system named file.

>>> Did you STORE it or also READ it?

See above answer

But I do not want to reinvent the wheel, by e.g. open a file given by name.

>>> Huh? NtCreateFile?

As already explained: Maybee I'm too stupid, but:
How declare a file name here:

NtCreateFile(

	  

		OUT PHANDLE			 [i][color="blue"]FileHandle[/color][/i],

		IN ACCESS_MASK		  [i][color="blue"]DesiredAccess[/color][/i],

		IN POBJECT_ATTRIBUTES   [i][color="blue"]ObjectAttributes[/color][/i],

		OUT PIO_STATUS_BLOCK	[i][color="blue"]IoStatusBlock[/color][/i],

		IN PLARGE_INTEGER	   [i][color="blue"]AllocationSize[/color][/i] OPTIONAL,

		IN ULONG				[i][color="blue"]FileAttributes[/color][/i],

		IN ULONG				[i][color="blue"]ShareAccess[/color][/i],

		IN ULONG				[i][color="blue"]CreateDisposition[/color][/i],

		IN ULONG				[i][color="blue"]CreateOptions[/color][/i],

		IN PVOID				[i][color="blue"]EaBuffer[/color][/i] OPTIONAL,

		IN ULONG				[i][color="blue"]EaLength[/color][/i] );

Sorry if I misused your time. I'll never do it again.

Peter