Jump to content

Recommended Posts


Posted

That's very strange. :unsure:

One of the given links specifiy that this Registry entry is a SP2 feature.

Maybe you are running Gold or SP1?

Or SP3 and the feature has been removed? :w00t:

jaclaz

Posted (edited)

Nope its the normal XP with SP2... well allmost normal cus it is Windows XP N

witch really mean that there isnt any Media Player included... Maybe this is the

reason but I doubt it, what should Media Player have to do with the all this.

Hmm another strange thing is I changed the value to 0 and when I restarted

Bart it didnt stop right after the windows load screen... so the problem only

accurs when I set the writeprotection to 1.

Oh btw cdob... the syntax for winnt32 is:

X:\xpsetup\i386\winnt32.exe /makelocalsource /syspart:c: /unattend:X:\xpsetup\i386\Winnt.sif>

Edited by fusan
Posted
When I restarted the PC, it stopped right after the WindowsLogo Screen (just before it starts to load the GUI) and it didnt go further from there.
Sorry, bad memory: FBWF plugin is expected too.

http://www.911cd.net/forums//index.php?s=&...st&p=133433

Overalll find the error source. Try set tempdrive:

X:\xpsetup\i386\winnt32.exe /makelocalsource /syspart:c: /tempdrive:c: /unattend:X:\xpsetup\i386\Winnt.sif

Posted
Sorry, bad memory: FBWF plugin is expected too.

http://www.911cd.net/forums//index.php?s=&...st&p=133433

Well, no, it should be additional.

@fusan

Why don't you try the Reg key on a "normal" XP?, it has always worked. If you use XP SP2, that is. Could it be some KB update?:unsure:

It is definitely documented to work with BartPE, try using this .cmd:

http://www.911cd.net/forums//index.php?showtopic=19422

or, another idea, maybe the thereby referenced app?:

http://www.joeware.net/freetools/

http://www.joeware.net/freetools/tools/writeprot/index.htm

jaclaz

Posted (edited)

@jaclaz

I have tried to change the reg key on my own PC with Windows XP SP2 and it works like a charm,

but you have to do it before you plug in the USB... othewise is want work. So that is why it doesent

work in Bart since the stick is allready pluged in.

Anyway I have tried the link: http://www.911cd.net/forums//index.php?showtopic=19422 that you

gave me but Im having the same result as before with setuphiv.inf-> Windows Splash screen ->

black nothing and the laptop is halted/frozen.

Maybe there is another way to prevent this delay than writeprotect the USB?

Another observation I made was: If I let windows be copied to the HD and instead of rebooting I rerun

the proces of copying windows again, there is no problems...

Somtimes there is no delay at all the first time.

@cdob

I would love to find the overall error source, but I dont have a clue were to start

Edited by fusan
Posted
SB... othewise is want work. So that is why it doesent work in Bart since the stick is allready pluged in.

Well, no.

The idea is that WHILE booting BartPE reads migrate.inf and then loads the key.

It has been reported to work by several people, so there must be something "peculiar" with your build.

Next try is to add the key to setupreg.hiv.

jaclaz

Posted (edited)

@jaclaz

I have tried to create the migrate.inf in minint\system32 with this code:

[Version]
Signature = "$Windows NT$"

[Addreg]
;WriteProtect USB
HKLM,"SYSTEM\ControlSet001\Control\StorageDevicePolicies","WriteProtect",0x00010001,1

I created the hiveOEM.inf and added it to minint\system32 with these lines

[Version]
Signature = "$Windows NT$"

[Addreg]
;WriteProtect USB
HKLM,"SYSTEM\ControlSet001\Control\StorageDevicePolicies","WriteProtect",0x00010001,1

and added this entry to txtsetup.sif:

[HiveInfs.Fresh]
AddReg = hiveOEM.inf, AddReg
...

[HiveInfs.Upgrade]
AddReg = hiveOEM.inf, AddReg
...

None of the methods changed the registry in Bart. Is seems like they both are totaly ignored.

The only way I assume is changing the registry in Bart is editing Setupreg.hiv but at soon as I

change the writeprotect value to 1 it halts/freeze the PC right after the Windows Splash screen.

(If I change it to 0, I can see the entry changed in the registry.)

I have also tried this method: http://www.911cd.net/forums//index.php?showtopic=19422 witch

was very promising and actually changed the registry, but I got the same result as with Serupreg.hiv...

Windows splash screen and a Halt/freeze after that.

So the conclusion is... I can change the registry to writeprotect the USB at startup, but it doesent load bart...

is there any logfile to check what happend right before it Halted?

This is a hard one... Im running out of options... :(

Edited by fusan
Posted

Well, there MUST be a reason.

The problem is probably in your BartPE, possibly a conflicting plugin or something like that, cannot say.

How did you build it?

Do you use any "non-base" shell, like XPE or somethng like that?

jaclaz

Posted

Here is how I build it...

DOS

- I formated the 16GB stick with HP Disk Storage Format Tool (FAT32)

and used Win98 bootdisk.

- Copied BartPR to USB

- Copied GRUB4DOS to USB and edited the config.sys

BART PE

- Downloaded and Installed BartPE

- Added a plugin for support of Windows Script Host and HTA

- Added the SSH plugin to correct the Diskpart.exe bug

- Added Autorun_MyCMD.cmd to automate the process of installing windows from Bart.

And thats basicly it. No fancy plugins og Shells.

-----------------------------------------------------

Somthing weird just happend...

I created the windows installation on a 4 GB stick, just to tryif it works...

and there is absolutely NO delay when windows is being copied!!!

I tried on several different laptops now and still no delay

So what is the difference between 4 GB and 16 GB???

The installation is a little diffent becuse I used PEtoUSB to make the USB, instead

of formating and copying everything myself.

As I can se it the only difference is that I used GRUB4DOS but can that have any influence

in Bart???

Posted

Hmmm, did you use PEtoUSB:

http://gocoding.com/page.php?al=petousb :w00t:

Last time I checked it, it only formatted as FAT16 and thus with a limit of 2 Gb.

No, grub4dos should have not any relevance.

The only possible difference between a 4 Gb and a 16 Gb may be in the partition type used, a 4 Gb can have both a CHS and a LBA mapped partition, a 16 Gb may only have a LBA one.

Save the MBR from both the sticks, use HDHacker (pointing to Physical Drive), compress them in a .zip file and attach the file, I'll have a look at it.

Just for the sake of experimenting, can you try the migrate.inf and/or the setupreg.hiv on this new 4 Gb stick?

jaclaz

Posted

Hmmm, did you use PEtoUSB:

http://gocoding.com/page.php?al=petousb :w00t:

Last time I checked it, it only formatted as FAT16 and thus with a limit of 2 Gb.

No, grub4dos should have not any relevance.

The only possible difference between a 4 Gb and a 16 Gb may be in the partition type used, a 4 Gb can have both a CHS and a LBA mapped partition, a 16 Gb may only have a LBA one.

Save the MBR from both the sticks, use HDHacker (pointing to Physical Drive), compress them in a .zip file and attach the file, I'll have a look at it.

Just for the sake of experimenting, can you try the migrate.inf and/or the setupreg.hiv on this new 4 Gb stick?

jaclaz

Posted
Hmmm, did you use PEtoUSB:

http://gocoding.com/page.php?al=petousb :w00t:

Well thats the one and it worked on this Kingston 4GB stick

Save the MBR from both the sticks, use HDHacker (pointing to Physical Drive), compress them in a .zip file and attach the file, I'll have a look at it.

Done and attached as USB.zip

Just for the sake of experimenting, can you try the migrate.inf and/or the setupreg.hiv on this new 4 Gb stick?

Allready did that but with same result as 16GB

USB.zip

Posted

The 16Gb MBR appears correct, being 0C it is a LBA FAT32 partition.

The 4Gb is not the best way, it probably uses the NT extension to FAT to allow for 4Gb, at the expense of 64 kb clusters, partition type is 0E (FAT16 LBA), I would re-format it as FAT32.

Some info:

http://www.win.tue.nl/~aeb/partitions/partition_types-1.html

But of of course any of the above is unrelated to the problem you are experiencing, truth is I have no idea why your particular BartPE behaves as you describe. :(

Let's wait and see if cdob or someone else comes out with some ideas....

jaclaz

Posted

Well, overall I guess:

Setupldr.bin behave different at windows installation and at minint mode.

PE read migrate.inf at a device fixed media (internal hd, CD, USB hard disk), but not at removable media (most USB stick).

Setupreg.hiv is to be prefered. Works always.

@fusan

Did you tried tempdrive?

@jaclaz

I understand gray's statement different: WriteProtect requires FBWF.

Rough idea:

don't use winnt32.exe.

File acess is slow at USB stick. Reading one big file is faster.

Copy ISO image to USB stick. (The same ISO image maybe written to CD for installation.)

Boot PE. Extract ISO image to hd (run 7-zip or mount with imdisk).

Use a primary active partition. Use a ntfs partition.

Files goes to \$winnt.~ls$.

Hardlink \$winnt.~ls$\I386 files to \$winnt.~bt$.

Use boot.ini to boot renamed setupldr.bin. Or use grub4dos and boot \$winnt.~bt$\setupldr.bin.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...