51 replies to this topic

[Galapo]

The new script is available in the nativeEx_BSOR download on the nativeex.boot-land.net server.

Hi Peter,

Great new addition! I tried to download but it's not on the server as far as I can tell. Was the upload unsuccessful?

Regards,
Galapo.

[AeroXP]

New Version of urtl\native.exe for nativeex_BSOR.

This is the version with updated copyright and help.

 src.zip   1.7KB   545 downloads
 native.zip   6.77KB   655 downloads

[pscEx]

Hi Peter,

Great new addition! I tried to download but it's not on the server as far as I can tell. Was the upload unsuccessful?

Regards,
Galapo.

Now it is really on the server
And it contains the new version aeroxp posted.

Peter

[Galapo]

Thanks! I'm going to test the new option tomorrow.

Regards,
Galapo.

[pscEx]

I added the bootMenu.Script to the project.

Peter

[asiekierka]

I plan to make a project based on WinRoot and nativeEx_BSOR stuff, BUT:
1) Using the Windows 2000 SP4 core (smaller)
2) Working properly on a single floppy.

I plan to work on it, BUT it still seems... impossible.
I'll try though. I'll need your permission, psc, to use info of scripts from your project. Otherwise i wouldn't be able to publish my project...

[thunn]

But Psc is still waiting to hear from O&O!
Just kidding Peter, great little project!

[AeroXP]

1) Using the Windows 2000 SP4 core (smaller)

It gives you a stop error. Your best bet is Whistler 2462. (RamBoot is not supported, gives a SYSTEM_LICENSE_VIOLATION error.)

2) Working properly on a single floppy.

Impossible, the Kernel is 1.1 MB Compressed. The hal is 50kb compressed, and NTDll is 597-700kb.

[MedEvil]

Impossible, the Kernel is 1.1 MB Compressed. The hal is 50kb compressed, and NTDll is 597-700kb.

Well if the whole OS should fit on a floppy, we're not talking about a lot of functionality here. So i'm pretty sure that the files in question can be slimmed down.

[AeroXP]

Your main problem: Drivers.

[AeroXP]

psc, did you get it working?

[pscEx]

psc, did you get it working?

If you mean my post in NDK:

I wrote 'as previously'. The ACCESS issue is still not solved.

Peter

[asiekierka]

aeroxp: STOP error, eh? It's because of PE-like mode that isn't supported by Win2k and earlier.
Also we could slim NTDLL/NTOSKRNL.

EDIT: We can also rewrite the NCLI, but it shouldn't be needed.
EDIT#2: We can also maybe... use ReactOS stuff?

[MedEvil]

Your main problem: Drivers.

For a fun project like this, which will never have any real use and only the goal, to start from a single floppy and present you a command prompt?

I would say the biggest problem is smarts ...and knowledge ...and smarts!

I still have a demo disk of a unix that starts from a floppy, has a desktop, mouse and keyboard support, a filemanager, a javascript capable browser and a TCP stack including a dialer.
Not to mention a game and some demos!

Never underestimate what a true geek can do!

[MedEvil]

aeroxp: STOP error, eh? It's because of PE-like mode that isn't supported by Win2k and earlier.

If that is the reason for the error, you will just have to fix ntoskrnl. the difference between PE mode and not PE mode is, that the registry is loaded read only and never tried to write it back.
Doesn't seem to be two impossible things to fix, when you already slimming down the file.

[AeroXP]

Stop: Entry point not found.
---

EDIT#2: We can also maybe... use ReactOS stuff?

I have tried that long ago... It boots up to a blue screen or a black screen.

[Galapo]

Hi Peter,

In the '!CopyFiles.script' I'd like to suggest the addition of the follow line

ShellExecute,Hide,"attrib","-R #$q%target_win%\TXTSETUP.sif#$q"

after the line

CopyOrExpand,%source_win%\TXTSETUP.sif,%target_win%

I made this change myself, but others may need it too if copying from CD.

Thanks,
Galapo.

[pscEx]

There is a redesign available: Download center > nativeEx server > nativeEx_BSOR.

It runs under WB 077 RC 1 and higher.

The project now is less complicated for unexperienced users.

When you have downloaded, define your XP (any SP) or W2003 (any SP) source CD and start.

The project will run into qEmu with TinyKRNL.

New: The target files are cached for OS, SP, Language, etc.
As a result: The first run takes around one to two minutes to build the ISO.
The second run only takes about 5 seconds, even with a different target application.

Whenever something changes with the source CD, an additional cache item is generated.

Please note, that BlueCon does not work when built with W2003 source.

BTW: I'm restarting to work with: 'Not have a fixed target application, but a menu'. Chances are good, following my latest Googleing.

Peter

[AeroXP]

I plan to make a project based on WinRoot and nativeEx_BSOR stuff, BUT:
1) Using the Windows 2000 SP4 core (smaller)
2) Working properly on a single floppy.

I plan to work on it, BUT it still seems... impossible.
I'll try though. I'll need your permission, psc, to use info of scripts from your project. Otherwise i wouldn't be able to publish my project...

I compiled a version of NCLI for NT4/2000. It features something called CPUID!

If you mean my post in NDK:

I wrote 'as previously'. The ACCESS issue is still not solved.

Peter

You don't have to use NtCreateProcess or ZwCreateProcess, you can use RtlCreateUserProcess.

Here's a prototype:

NTSYSAPI 

NTSTATUS

NTAPI

RtlCreateUserProcess(







  IN PUNICODE_STRING	  [i][color="blue"]ImagePath[/color][/i],

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

  IN OUT PRTL_USER_PROCESS_PARAMETERS [i][color="blue"]ProcessParameters[/color][/i],

  IN PSECURITY_DESCRIPTOR [i][color="blue"]ProcessSecurityDescriptor[/color][/i] OPTIONAL,

  IN PSECURITY_DESCRIPTOR [i][color="blue"]ThreadSecurityDescriptor[/color][/i] OPTIONAL,

  IN HANDLE			   [i][color="blue"]ParentProcess[/color][/i],

  IN BOOLEAN			  [i][color="blue"]InheritHandles[/color][/i],

  IN HANDLE			   [i][color="blue"]DebugPort[/color][/i] OPTIONAL,

  IN HANDLE			   [i][color="blue"]ExceptionPort[/color][/i] OPTIONAL,

  OUT PRTL_USER_PROCESS_INFORMATION [i][color="blue"]ProcessInformation[/color][/i] );

Here's a litttle example:

PRTL_USER_PROCESS_INFORMATION ProcessInformation;

	UNICODE_STRING SessionMgr;

	PRTL_USER_PROCESS_PARAMETERS ProcessParameters;



	RtlCreateUserProcess(

				   &SessionMgr,

				   OBJ_CASE_INSENSITIVE,

					RtlDeNormalizeProcessParams( ProcessParameters ),

					 NULL,

					NULL,

					 NULL,

				   FALSE,

				   NULL,

				   NULL,

				   ProcessInformation);

[AeroXP]

w00t! Found out how to make new process!

NTSTATUS

RtlCreateNewProcess(

	VOID 

	)

{

	

	NTSTATUS					 s;						   // Status

	UNICODE_STRING			   imgname;					 // ImageName

	UNICODE_STRING			   imgpath;					 // Nt ImagePath

	UNICODE_STRING			   dllpath;					 // Nt DllPath (DOS Name)

	PRTL_USER_PROCESS_PARAMETERS processparameters;	   // ProcessParameters

	RTL_USER_PROCESS_INFORMATION processinformation={0};  // ProcessInformation 

		//

		// Change name to Nt format

		//

		s = RtlDosPathNameToNtPathName_U(L"C:\\smss.exe", &imgpath, NULL, NULL);

		//

		// Initialize Unicode strings.

		//

		RtlInitUnicodeString(&imgname, L"smss.exe");

		RtlInitUnicodeString(&dllpath, L"c:\\");

		//

		// Create ProcessParameters value

		//

		s = RtlCreateProcessParameters(&processparameters, &imgname, &dllpath, 0, 0, 0, 0, 0, 0, 0);

		//

		// GRAND FINALE: CREATE PROCESS!!!

		//

		s = RtlCreateUserProcess(&imgpath,

				OBJ_CASE_INSENSITIVE,

				processparameters,

				NULL,

				NULL,

				NULL,

				FALSE,

				NULL,

				NULL,

				&processinformation

			);

		//

		// Hook to new process!

		//

		s = NtResumeThread(processinformation.ThreadHandle, NULL);

	return STATUS_SUCCESS;

}

[AeroXP]

Added command line:

NTSTATUS

NtChkdsk(

	VOID

	)

{

	UNICODE_STRING EnvString, NullString, UnicodeSystemDriveString;

	NTSTATUS					 status;						   // Status

	UNICODE_STRING			   imgname;					 // ImageName

	UNICODE_STRING			   imgpath;					 // Nt ImagePath

	UNICODE_STRING			   dllpath;					 // Nt DllPath (DOS Name)

	UNICODE_STRING			   cmdline;					 // Nt CommandLine

	PRTL_USER_PROCESS_PARAMETERS processparameters;	   // ProcessParameters

	RTL_USER_PROCESS_INFORMATION processinformation={0};  // ProcessInformation

	WCHAR Env[2] = { 0,0 };							   // Process Envirnoment

	PKUSER_SHARED_DATA SharedData = (PKUSER_SHARED_DATA)USER_SHARED_DATA;  // Kernel Shared Data

	RtlInitUnicodeString(&imgpath,L"\\SystemRoot\\System32\\autochk.exe"); // Image path is %SystemRoot%\System32\Autochk.exe 

	RtlInitUnicodeString(&imgname, L"autochk.exe");						// Image name is autochk.exe

	RtlInitUnicodeString(&dllpath, SharedData->NtSystemRoot);			  // DLL Path is %SystemRoot%

	RtlInitUnicodeString(&cmdline, L"autocheck *");						// Command Line parameters

		

		status = RtlCreateProcessParameters(&processparameters, &imgname, &dllpath, &dllpath, &cmdline, Env, 0, 0, 0, 0);

		DbgPrint("Launching Process: %s, DllPath=%s, CmdLine=%s",

			 &imgname,

			 &dllpath,

			 &cmdline);

		   status = RtlCreateUserProcess(&imgpath,

								 OBJ_CASE_INSENSITIVE,

									processparameters,

									NULL,

									NULL,

									NULL,

									FALSE,

										   NULL,

									NULL,

									&processinformation

			);

		status = NtResumeThread(processinformation.ThreadHandle, NULL);

	return STATUS_SUCCESS;

}

[pscEx]

Thanks for your new snippet!

But currently I'm still fighting with your previous one.

In the first view it seems to be very well:

If I choose TinyKRNL from pscMenu, TinyKRNL is started and the help lines are shown. Great!

But when I try to do a command like e.g. 'dir', no 'dir' is shown. Instead of this the pscMenu is shown again.

But TiniKRNL is not really exited. Choosing pscMenu entries randomly(?) shows the pscMenu prompt > or the TinyKRNL prompt D:\I386>

Looks like there is some trouble with the console, standardinput, standardoutput and standarderror handles.

Currently I do not have so much time. But I'm going to collect all facts and post (and send you a copy of the BSOR source)

BTW: Do you knw the difference between

s = NtResumeThread(processinformation.ThreadHandle, NULL);

and

s = NtResumeProcess(processinformation.ProcessHandle, NULL);

Both work like described above.
Peter

[AeroXP]

Either will work, one resumes the thread, one resumes the process, resuming the process is recommended but Ntoskrnl uses ResumeThread.

Also, you should kill the previous process to make it work. (urtl1 -> urtl2, kill urtl1)

[pscEx]

Also, you should kill the previous process to make it work. (urtl1 -> urtl2, kill urtl1)

And how to come back into the menu after <process> finished?

A lot of questions Billy th Door seems intentionally not to anwer us! (or hides anywhere)

Peter

[AeroXP]

Perhaps, suspend the process?

Also, after you launch Recovery Console/Windows Setup, you can not go back to the standard Kernel Text-mode, limitation of SetupDD.sys

And it's not Bill: it's Ted Miller.