PrePE - fast boot PE
Posted 19 March 2012 - 11:21 AM
Since the reg file is seemingly EXTENSIVELY commented, something that could be really useful would be to translate those comments from Russian to English.
Or at least *somehow* convert it to text that I can try feeding Google Translate or similar.
Posted 19 March 2012 - 11:27 AM
All options are open.
But as I understand this is grldr(grub) + full disk image (loaded into RAM?)
You can boot the XP Image file either as FILEDISK from USB or HDD,
Or load and boot from RAMDISK, OR you can decide to use IMG_XP_Restore.exe to restore to partition ......(HDD or USB)
Posted 19 March 2012 - 11:48 AM
and the same goes on FIXED usb drive
So i'm curious about 1st post..
Posted 19 March 2012 - 02:38 PM
Comments are very few ))
The user hosting this
content is out of bandwidth.
54 Mb out of a 50800 bytes file?
My suggestion is to leave alone any other VM and do the tests with Qemu (with Qemu Manager): http://www.davereyn.co.uk/download.htm
It will be slower than other VM's but - believe me on my word for it - it is more suitable for this kind of experiments.
Ok about Qemu.
fresh 'system' from my XP VM(Ware) after 1st reboot (of installation process)
Posted 19 March 2012 - 08:53 PM
I thought that sarcasm was transparent enough.
I known you'd like it ))
I will expand on it though.
There are a zillion versions of VmWare (of which I have NOT installed ANY) so, besides the fact that "VmWare" means nothing without an EXACT version description, I have no iinterest for a file that is made on something that I cannot easily replicate.
Additionally VmWare virtual machines, last time I used one, had "peculiar" hardware simulated, thus needing some proprietary drivers installed, and from experience such VM's are "less similar" to "real hardware" in a few parts that may make the difference when conducting this kind of experiment.
For the reason above I asked you (I guess politely ) if you could instead use Qemu + Qemu Manager, as I have it available and - in my experience - is an environment that is better suited.
To this you replied with "OK" (mind you, you were - and still are - perfectly free to reply "No I will never use Qemu!").
Now it would only be normal if you carried your experiment on Qemu and posted related data, since you replied "OK".
We are not only talking two different languages we also have different VM's .
Posted 20 March 2012 - 07:11 AM
Sure. I did not intend to use sarcasm or something.
Sorry if I did write anything ambiguous..
Yes , yes, i understand about Qemu and Vmware.
I just tried to reproduce 1st post - there is written it was SUCCESSFUL on usb media.
This is while we waiting details from VV2006
I don't think registry from qemu install xp will be very different from VM and the real machine,
i mean in case of we have registry "patch" posted above that needs to eliminate hardware differences.
This was just due i had vm , xp installation disk and 5 minutes to install (1st boot) and extract "system"
This r just small experiments trying to lucky follow 1st post instruction.
If i'll have no additional info (from VV2006) then i'll involve the real debugging (qemu and other things)
ps BTW does qemu support virtual com1/2 port redirected to pipe?
to connect it to windbg like i do in vmware?
Posted 20 March 2012 - 07:12 AM
it was wrong link to very different stuff))
Posted 20 March 2012 - 09:42 AM
To understand in which situation I am, see what I can get with google translate of the original post by Alexey:
Google translate of the above:
You might understand how I cannot get much from sentences like:
After picking a ntbtlog.txt after booting via ntldr and setupldr.bin found that ntldr first determines Soup, and then loads the wood, and setupldr.bin does everything through the ass - first loads all of the wood, and then unloads the excess.
That is why I would have been interested in the translation of the comments inside the .reg file:
Request: please write, who can, cmd script to convert txtsetup.sif (section [SCSI.Load] and [HardwareIdsDatabase]) in the reg-file. It is well commented, I think it will be clear. There's quite simple, but I do not know how to make cmd cycles.
I could write the batch allright, if only I could understand the concepts.
Posted 20 March 2012 - 10:05 AM
"After picking a ntbtlog.txt .." section describes differences between NTLDR and SETUPLDR.bin
that differences are in load drivers rules:
- ntldr checks devices and loads drivers for em
- setupldr loads ALL drivers and then unloads unneeded
2nd section about cmd file is seems alredy included in .reg file posted above
Originaly he asked for help to convert txtsetup.sif ([SCSI.Load] & [HardwareIdsDatabase] sections) into reg file.
[this is already done imho; shall recheck]
The problem is that he says he did rename SETUPREG.HIV to system and appended it with those final .reg file
(produced from txtsetup.sif) and SUCCESSFULLY booted different test XP machines
I can't do this from Bart's SETUPREG.HIV appended with posted above .reg
Seems .reg file above is not full or we miss somthing..
(LIKE PATCHED NTDETECT.COM - what for?)
So waiting some help (of old results digging) from VV2006,
or shall try to recreate those experiments of making 'system' later if nothing will come out from the dark..
Posted 20 March 2012 - 10:08 AM
Posted 20 March 2012 - 11:54 AM
I could not get the "translated" .reg file.
The link you posted originally was to a very large .pdf file that I was NOT able to download.
The other files you posted are seemingly "system.zip" files that I have no use whatsoever for.
WHICH files (the "original archive" you cited) are you missing instead?
In the original post by Alexey there are three files cited:
http://narod.ru/disk..._ntldr.rar.html <- For_boot_ntldr.rar
http://narod.ru/disk...torito.rar.html <- Eltorito.rar
http://narod.ru/disk...TSETUP.SIF.html <- TXTSETUP.SIF
And a link to here:
which seems to me a Russian version of the original instructions by emanuel:
I have a copy of the three cited files, which one do you miss?
Posted 20 March 2012 - 04:54 PM
TXTSETUP.SIF - it is from original MS installation disk..
Posted 21 March 2012 - 11:46 AM
I am now starting to understand the idea/procedure , and it's very clever I might say .
To replicate, it should be easier if we do the steps in the post by VV2006 "reversed".
- FORGET (temporarily) anything about this approach.
- Create a "normal" PE 1.x (the simplest, with the less complications/piugins/what not the better) using XP SP2 sources should be the "safer" choice.
- Test it so that it boots on the media you chose (Virtual Hard disk image or USB flash stick)
A simple howto "convert" an existing, working PE 1.x .iso is given here:
http://www.911cd.net...topic=23777&hl= (step #6)
For USB - only if needed - one can use the Dietmar's modified NTDETECT.COM.
- Test that it boots normally.
- You have now a "plain" PE 1. x that boots with a SETUPLDR.BIN copied to root and renamed to NTLDR and with a "flat" directory structure minint (as you are on HD like device)
- Now do the steps by VV2006:, only very slightly modified
- Copy with rename minintSYSTEM32SETUPREG.HIV to minintSYSTEM32CONFIGSYSTEM.
- Extract from archive Updated_boot_ntldr.rar files srv_txtset.cmd and srv_txtset.reg to minintSYSTEM32CONFIG and then run srv_txtset.cmd.
Little changed srv_txtset.cmd:
@ECHO OFF SETLOCAL ENABLEEXTENSIONS rem VV2006 -- a few changes by jaclaz IF NOT EXIST SYSTEM GOTO :ERROR1 REG LOAD HKLMt SYSTEM regedit /s srv_txtset.reg REG UNLOAD HKLMt PAUSE GOTO :EOF :ERROR1 ECHO File %~dp0SYSTEM does not exist! PAUSE GOTO :EOF
- Put this BOOT.INI in the root of the drive:
[boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)minint [operating systems] multi(0)disk(0)rdisk(0)partition(1)minint="Use NTLDR" /fastdetect /minint /HAL=HALMACPI.DLL /KERNEL=NTKRNLMP.EXE C:grldr="Use SETUPLDR.BIN"
- Rename NTLDR back to SETUPLDR.BIN (so that you can go back if anything is not working as expected
- Copy to root a "real" NTLDR
- Add to root grldr from latest grub4dos
- Put this menu.lst in root:
color black/cyan yellow/cyan timeout 30 title find and load SETUPLDR.BIN of Windows NT/2K/XP find --set-root /setupldr.bin chainloader /setupldr.bin
- Try booting from the thingy. (keeping your fingers crossed), you should be able to boot "as before" (if you choose "Use SETUPLDR.BIN") or with the new approach (if you choose "Use NTLDR").
Posted 21 March 2012 - 12:17 PM
Meanwhile I recreated the 1st post results.
But plz reupload the archive ANYWAY!
My fault was using VMware (like your said), it somehow emulates/works with USB connected HDD and stick
I did near all the same on live machine and booted successfully from USB stick!
The only difference i used with posted above is:
additionally to appending SETPREG.HIV with .reg above
i appended it before with full 'system' posted above (from 1st boot installed full XP)
['system' was exported to .ref file also as somehow it is locked for editing as a hive]
without this step like i written above just "/config/system corrupt" error on registry accessing.
ps. /minint switch in boot.ini is always needed in such case to avoid LICENSE_VIOLATION BSOD
So i'm going now to the ntldr-CD-boot part of the project..
WAITING FOR Updated_boot_ntldr.rar UPLOAD!
Do You know some sources with patched ntdetect.com (for bsods or somth) to read for?
Posted 21 March 2012 - 12:19 PM
from my tests it is better without /HAL=HALMACPI.DLL /KERNEL=NTKRNLMP.EXE
Posted 21 March 2012 - 12:29 PM
Correcting it now, however it is this one:
And yes, the stupid board software also makes attachment work "randomly" at least with my Opera setup.
The "Dietmar's" ntdetect.com is only needed on some hardware, however you can recreate it easily, see:
My fault was using VMware (like your said), it somehow emulates/works with USB connected HDD and stick
Experience: that most brutal of teachers. But you learn, my God do you learn.
Posted 21 March 2012 - 01:41 PM
Once you will have confirmed that the approach works for you, we might try again at the CD, like in original VV2006's request.
I seem to remember that there were a few findings related to NTLDR and CD paths in the meantime, I'll try and find them.
One of my usual semi-random ideas , based on the posts made here:
and on the BOOT.INI posted there by VV2006, which is here in UNbotched CODE:
[boot loader] timeout=3 default=multi(0)disk(0)cdrom(224)\I386 [operating systems] multi(0)disk(0)cdrom(224)\I386="CD on Primary Channel" /fastdetect /minint /HAL=HALMACPI.DLL /KERNEL=NTKRNLMP.EXE multi(0)disk(0)cdrom(239)\I386="CD on Secondary Channel" /fastdetect /minint /HAL=HALMACPI.DLL /KERNEL=NTKRNLMP.EXE C:\grldr="Grub Menu"
What happens if on the CD there is BOTH the \I386\ folder and a \minint\ one (at first attempt I would simply make the \I386\ an integral copy of the already tested \minint\ on USB)?
[boot loader] timeout=3 default=multi(0)disk(0)cdrom(224)\I386 [operating systems] multi(0)disk(0)cdrom(224)\I386="224_I386" /fastdetect /minint /HAL=HALMACPI.DLL /KERNEL=NTKRNLMP.EXE multi(0)disk(0)cdrom(239)\I386="239_i386" /fastdetect /minint /HAL=HALMACPI.DLL /KERNEL=NTKRNLMP.EXE multi(0)disk(0)cdrom(224)\minint="224_minint" /fastdetect /minint /HAL=HALMACPI.DLL /KERNEL=NTKRNLMP.EXE multi(0)disk(0)cdrom(239)\minint="239_minint" /fastdetect /minint /HAL=HALMACPI.DLL /KERNEL=NTKRNLMP.EXE C:\grldr="Use SETUPLDR.BIN"
Posted 21 March 2012 - 03:14 PM
then i figured it out
else help appreciated ))
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users