QUOTE (jaclaz @ Oct 1 2007, 01:00 PM)

I just posted as attachment the copy I have.

OK,

definitely we are cross-posting.
Some (most) of the downloads from www.archive.org simply miss 1 (one) byte at the end, in other words the downloaded file is one byte shorter than the original.
Since 99,999% of archive files have a few 00 bytes at the end (so called "padding"), you need to add to the file a byte with value 00.
You do not need necessarily a Hex-editor to do so.
Copy and paste the following with Notepad in a new .txt file and rename the file to pad0.cmd:
CODE
@ECHO OFF
if %1.==. GOTO :EOF
if not exist echoo.com (
echo Bj@jzh`0X-`/PPPPPPa(DE(DM(DO(Dh(Ls(Lu(LX(LeZRR]EEEUYRX2Dx=>echoo.com
echo 0DxFP,0Xx.t0P,=XtGsB4o@$?PIyU WwX0GwUY Wv;ovBX2Gv0ExGIuht6>>echoo.com
echo ?@xAyJHmH@=a?}VjuN?_LEkS?`w`s_{OCIvJDGEHtc{OCIKGMgELCI?GGg>>echoo.com
echo EL?s?WL`LRBcx=k_K?AxVD?fCo?Cd?BLDs0>>echoo.com
)
echoo.com $00>tempbin.$$$
copy /b %1 + tempbin.$$$ %1
del echoo.com
del tempbin.$$$
PAUSE
put it in the same directory where you downloaded the file, open a Command Prompt there and simply type:
pad0 filename.ext [ENTER]
or simply drag and drop the archive on the .cmd
jaclaz
Thanks mate :-)
Yes, we are definetley cross posting but it's all good now...
Ok, I completely understand what you mean now in respect to padding and thankyou for this checksum/padding/byte fixing program/batch file script which I have just tested and confirm to work perfectly...
Out of curiousity, how does this batch file work ?
I understand nearly everything in the batch file (I think) except for these lines between the parantheses:
(
echo Bj@jzh`0X-`/PPPPPPa(DE(DM(DO(Dh(Ls(Lu(LX(LeZRR]EEEUYRX2Dx=>echoo.com
echo 0DxFP,0Xx.t0P,=XtGsB4o@$?PIyU WwX0GwUY Wv;ovBX2Gv0ExGIuht6>>echoo.com
echo ?@xAyJHmH@=a?}VjuN?_LEkS?`w`s_{OCIvJDGEHtc{OCIKGMgELCI?GGg>>echoo.com
echo EL?s?WL`LRBcx=k_K?AxVD?fCo?Cd?BLDs0>>echoo.com
)
What does this mean and how does this work ?
Just very curious...
What other languages/scripts/code do you work with - do you also do low-level stuff (ie Assembler) or just high-level (C, C++) and/or Web (C# etc etc) ?
Anyway, in regards to TinyKRNL I have now installed the WDK (6000/VISTA DRIVER DEV KIT) and have setup the Razzle/Dazzle command-line-based build environment...
I have also downloaded the Tortoise-Shell-Subversion client thanks to Nuno Brito below - both you guys have been very helpful in getting me and TinyKRNL up and running so thanks a lot !!!

Moving back to my other queries:
has anyone here at BootLand built (compiled) the code in this TinyKRNL archive - using the razzle/dazzle environment and WDK ?
or has anyone used (or even seen) the Native Command Line Interface giving one access to the NT layer of the Windows OS - ie before SMSS.EXE as executed and whilst still in the system process ???
-->(as depicted here:
http://tinykrnl.org/dev_test.htm - scroll right down to TESTING A COMPONENT)
I have attached a picture to this post (Native Command Line Interface = command prompt at NT layer before "Windows").
Continuing on with the NCLI for a moment -
My understanding is that this prompt is pretty much running at the exact same time and in the exact same fashion that CHKDSK.EXE would run - even the screen coluring is the same as you will see from that image.
CHKDSK.EXE and AUTOFMT.EXE plus a few other programs in the %system32% directory are NATIVE and do not require the Windows sub-system to be loaded - they are only dependent on NT itself and therefore only require NTOSKRNL.EXE as they run as system threads/processes.
This also means that SMSS.EXE has not been executed and, more importantly, it also means that such programs (CHKDSK, AUTOFMT, AUTOCONV etc etc) are built with device driver kits like the WDK - just my changing the sources file to output an EXE and not a SYS driver. This point is stated here (EXEs made via WDK/DDK) as opposed to most other EXEs being built in Visual Studio or another appropriate "high-level" IDE where programs are reliant on the Windows Sub-System (WIN32K.SYS, CSRSS, KERNEL32.DLL) - ie CreateProcess....
Finally, this also means that such a program (NCLI/CHKDSK/AUTOFMT) would have all the benefits and privileges of a device driver - not just being executed in kernel memory space etc - but on the x86 processor such programs are executed in Ring Zero (0) !!!
Is this understanding pretty much correct and consistent with everyone else's understandings ?
Well the reason I ask is because I would to know how one could get such a interface (NCLI as in the picture attached/posted) to boot up as part of a WinPE disk or standard windows installation...
I do not think this NCLI is specific to TinyKRNL whatsoever.
Basically, I see the NCLI as being a COMMAND.COM (and not CMD.EXE/NTVDM/MVDM emulated) dos prompt that is able to talk directly to the kernel and make use of the NATIVE NT API...
This would basically be setting up a true and proper "NT" operating system. When I say "true and proper" I suppose the best way to perceive what I mean would be to consider "WINDOWS" as a program that runs on top of "NT".
Makes sense yes ?
Anyway, to summarize and keep things simple and focused, and considering this is boot-land.net, does anyone know how to get a WinPE or Windows installation to bring up such a prompt from a standard cold bootstrap on a REAL machine (no emulation etc) ?
There would be many many uses to this sort of an environment - for example a cluster could be created using several NT/x86 (or x64) boxes: instead of using something like Compute Cluster Server (Win x64) the footprint could be kept to an absolute minimum by just running a MPIEXEC client/server system on top of this native NT NCLI point.
That is what I intend to do as a matter of fact - for my PhD thesis - create a proper cluster operating system.
Finally, and speaking of x64, would it be possible in anyone's opinion, to use Microsoft Windows' Compute Cluster Server with SP1 instead of the standard 32-bit edition that TinyKRNL asks for to build itself around - would CCS/x64 work instead of the standard 32-bit x86 version ???
Could a WinPE disk be made with CCS/x64 - to run in native x64 mode ???
I am not sure if anyone is familiar with Compute Cluster Server (Win x64) or not (download here - www.microsoft.com/windowsserver2003/ccs/default.aspx ) but this would be interesting to know - both if TinyKRNL could use it as it's base and wether or not a WinPE disk could be made with these files just like a WinPE ISO can be made from any other XP or Server ISO.
Ok, Ok, too much for one post I know - sorry !!!!!!!!!
Thanks again everyone.
PS:
In conclusion the main interest here is getting to the NCLI so if anyone can help that would be great - any thoughts on any of the rest would also be good - I have tried googling native API and NCLI but NOTHING.