Jump to content











Photo
- - - - -

BSOD 0x0000007B


  • Please log in to reply
32 replies to this topic

#1 Decent

Decent

    Newbie

  • Members
  • 13 posts
  •  
    Germany

Posted 29 April 2009 - 12:57 PM

Hello,
i'm new to Winbuilder.
I created a "USB-Boot-Stick" upon the 'Newcomer'S Tutorial - Live XP'. Everthing went fine, no Errors in Log. It starts in qEmu (only performance is a little poor).
But when i put the USB-Stick in a DELL Optiplex GX260 it boots then the Windows Logo comes up and shortly after that i get a BlueScreen with Stop Message:
STOP: 0x0000007B (0xF8C16528,0xC0000034,0x00000000,0x00000000)

'7B' could have something to do with Harddrive, but there is no Harddrive in the PC, and i can't found anything about the second Code.

Has anyone experienced the same?

Kind regards,
Andreas

#2 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7101 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 29 April 2009 - 01:28 PM

Has anyone experienced the same?


NO.
http://homepages.tes...no-answers.html


It's the first time I see that error. :)

Some green men must have changed topic titles, as searching on the board for "0x0000007b" in the LiveXP forum gives 10 results, while searching on the entire board gives 45 of them. :)

If you google for GX260 0x0000007b you get tons of results.

Are you using the "BootSDI" .script (and the Server2003 SP1 or R2 (NOT "gold", NOT "SP2") files? (RAMDISK booting)

I guess that no, you are using "plain" USB booting.

If this is the case, try using the modified NTDETECT.COM:
http://www.911cd.net...showtopic=19235
http://www.msfn.org/...howtopic=112630

:)

jaclaz

#3 Decent

Decent

    Newbie

  • Members
  • 13 posts
  •  
    Germany

Posted 29 April 2009 - 02:13 PM

Hello,
yes 0x0000007b gives o lots of results, but i can't find anything about the second code 0xF8C16528.
I did the search but from my point of view the results are not that what i have. Sorry to be such impatient

I already use the "patched" ntdetect.com.

I use the Boot SDI Option, and use XP-CD(copied to Disk) as source, and create the USB-Stick with PeToUSB.exe

Kind regards,
Andreas

#4 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7101 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 29 April 2009 - 03:57 PM

I use the Boot SDI Option, and use XP-CD(copied to Disk) as source, and create the USB-Stick with PeToUSB.exe


Well, you cannot possibly have a 0x0000007b if using "BootSDI" (read RAMDISK booting) unless you are using the "wrong files". :)

The 0x0000007b error (regardless on what the second code is) means "unaccessible boot device", and is due to the "protected mode" or "GUI" device driver for the boot volume "kicking in" when the switch between "real mode" or "text mode" phase is over.

Please post the following:
  • contents of WINNT.SIF
  • size and version of SETUPLDR.BIN
  • size and version of RAMDISK.SYS

jaclaz

#5 Decent

Decent

    Newbie

  • Members
  • 13 posts
  •  
    Germany

Posted 29 April 2009 - 04:10 PM

Hi,
i just tested with another PC (DELL Optiplex GX620) and it works fine. ?!?

Kind regards,
Andreas

P.S. i have to leave now,i post the winnt.sif, SETUPLDR.BIN size and version of RAMDISK.SYS tomorrow.

#6 Decent

Decent

    Newbie

  • Members
  • 13 posts
  •  
    Germany

Posted 30 April 2009 - 03:39 PM

Hello,
the files on the USB-Stick are:
SETUPLDR.BIN 298096 Bytes
RAMDISK.SYS 22528 Bytes

there is no WINNT.SIF only a txtsetup.sif

Kind regards,
Andreas

Attached Files



#7 Lancelot

Lancelot

    Frequent Member

  • .script developer
  • 5013 posts
  • Location:Turkiye/Izmir
  • Interests:*Mechanical stuff and Physics,
    *LiveXP, BartPE, SherpyaXPE,
    *Basketball and Looong Walking,
    *Buying outwear for my girlf (Reason: Girls are stupid about buying bad stuff to make themselves uglier :))
    *Girls (Lyric: Girl,...., You will be a womann, Soon)
    *Answering questions for "Meaning of life",
    *Helping people,

    Kung with LiveXP, Fu with Peter :)
  •  
    Turkey

Posted 30 April 2009 - 04:21 PM

Hi Decent

have you used patch options of bootsdi script ?
also check:
SETUPLDR.BIN 2k3sp1enu md5 checksum:
4352373BC08FFA6D8FFDB20A3BA5BC9A

#8 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7101 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 30 April 2009 - 06:08 PM

I seem to perceive people speaking different languages. :D

Italian, German and Turkish, please read as:
  • size and version
  • size
  • md5 (and no size nor version) of one out of the two files


Isn't it curious how the same little problem that caused the failure of the Babel Tower project is still the same.....? ;)

:D

Notwithstanding the lack of information, my guess is that there is no way BootSDi (read RAMDISK booting) can work without a WINNT.SIF, with contents similar to this:
[SetupData]

BootDevice = "ramdisk(0)"

BootPath = "\i386\System32\"

OsLoadOptions = "/noguiboot /fastdetect /minint /rdpath=BootSDI.img"

Or is this added to TXTSETUP.SIF? ;)

jaclaz

#9 vmbray

vmbray

    Newbie

  • Members
  • 29 posts
  •  
    United States

Posted 02 May 2009 - 12:12 AM

I can tell you what causes this error, I might actually be able to help someone for a change... well not really since I just know what causes it, not what fixes it. Well sort of, I know one thing that fixes it. Also, I'm sure this is already known by/ posted about by someone more worthy than I, but for a brief moment I had a fantasy that I could contribute something intelligent :D

This is caused by you boot pe with no main hard drive (or new blank hd) attached with a windows installation on it. You want to miraculously see your machine boot, hook up a hard drive with an xp install on it. Doesn't have to be booting (ie could have corrupted reg, chkdsk problems etc.) but if you hook one up I pretty much guarantee you will boot. It's as if the pe gets confused and thinks it needs something from the main drive, or more likely when the os sees the main hd it looks for xp things there and if it sees them it's okay. Some mobo have this issue and some don't. ** could this be due to pe seeing the hd as c: once booted? that would actually make sense. mobo initializes usb as hd, then starts booting, then sees main hd as c: and looks there for things when it should be looking at usb, doesn't find what it's looking for, and 0x0000007b is the result. could that explain why iso emulation doens't have this since it *knows* it's booting from a 'cd' ??? **

To solve, use grub4dos and load an iso file instead of booting from the usb stick 'raw'. I have never seen this issue (well not in a week of working on this issue) when booting an iso into ram. The only issue I have with this is that some of the pc I support have 128mb ram (and don't need more for their 'normal' life) so this is not a solution for them.

I see a lot of suggestions that this is disk controller related and that may well be the case here (since some mobo work okay), but I have tried (to no avail) loading the correct driver. Also I don't totally buy this since the pe will see the hd once booted so it must have an adequate driver, AND it will only boot with the hd connected. So you can easily test, hook up a hd and boot. Do it, you will see.

This would be nice to figure out for me anyway.

#10 Psadi

Psadi
  • Members
  • 7 posts
  •  
    Sweden

Posted 08 May 2009 - 09:01 AM

I was having the same problem with BSOD 0x0000007B when booting using the latest scripts on a USB stick. Booting the same build from cd resulted in a working environment. Using an older project i saved I had no problem booting using the USB stick. This to me said that it was some script that was in the new project that wasn't in the old project, or that a script had change to cause this.

After a couple of hours compiling, adding script after script from the download server to the old build I found that when adding the script "EarlyStarter" I got the BSOD 0x0000007B. After i disabled the earlyStarter script I was once again able to boot from the USB stick.

What in the EarlyStarter script that makes the build fail I dont know but I hope it helps someone else :D

#11 Lancelot

Lancelot

    Frequent Member

  • .script developer
  • 5013 posts
  • Location:Turkiye/Izmir
  • Interests:*Mechanical stuff and Physics,
    *LiveXP, BartPE, SherpyaXPE,
    *Basketball and Looong Walking,
    *Buying outwear for my girlf (Reason: Girls are stupid about buying bad stuff to make themselves uglier :))
    *Girls (Lyric: Girl,...., You will be a womann, Soon)
    *Answering questions for "Meaning of life",
    *Helping people,

    Kung with LiveXP, Fu with Peter :)
  •  
    Turkey

Posted 08 May 2009 - 09:14 AM

What in the EarlyStarter script that makes the build fail I dont know but I hope it helps someone else :D

it will

Early starter is an essential future, can be fixed. Author of Early starter is in LiveXP project administrator (not me) and increase with the amount of info will lead to a quicker solution.

I guess (from your total writing) you are using v14 of early starter ??

and can you post your log****, and write how you exactly boot with usb.???

#12 Psadi

Psadi
  • Members
  • 7 posts
  •  
    Sweden

Posted 08 May 2009 - 09:45 AM

Yes its version .14
I use Boot SDI to create the files for USB. I belive I use the ramdisk and setupldr.exe from Windows 2K3 Sp1

checksum generated with Microsoft tool fciv
0f1ce9cbcd35a30d285c1eb672092778 ramdisk.sys
4352373bc08ffa6d8ffdb20a3ba5bc9a SETUPLDR.BIN

I then use PEtoUSB to move the files to the USB stick.

I uploaded the logfile for the compile of EarlyStarter

Need any more info?

Attached Files

  • Attached File  log.html   64.08KB   584 downloads


#13 Lancelot

Lancelot

    Frequent Member

  • .script developer
  • 5013 posts
  • Location:Turkiye/Izmir
  • Interests:*Mechanical stuff and Physics,
    *LiveXP, BartPE, SherpyaXPE,
    *Basketball and Looong Walking,
    *Buying outwear for my girlf (Reason: Girls are stupid about buying bad stuff to make themselves uglier :))
    *Girls (Lyric: Girl,...., You will be a womann, Soon)
    *Answering questions for "Meaning of life",
    *Helping people,

    Kung with LiveXP, Fu with Peter :)
  •  
    Turkey

Posted 08 May 2009 - 10:00 AM

Thank you for support

for future: when log file asked, everybody on boot-land ask for the project log file :D.

i will contact the author and try to make a bootable stick with petousb (which i never use :D ) to reproduce the result
also
using setupldr.bin from 2k3sp1 source directly on usb stick may cause problems with other settings for LiveXP boot. Use the one in LiveXP_RAM.iso and copy it to usb. setupldr.bin is patched for various purposes with the scripts/options you enable in livexp which will effect booting (i am not sure if this has any relation with early starter !)

keep in touch, cu ;)

#14 fxscrpt

fxscrpt

    Frequent Member

  • .script developer
  • 328 posts
  •  
    Germany

Posted 08 May 2009 - 10:09 AM

Yes its version .14
I use Boot SDI to create the files for USB. I belive I use the ramdisk and setupldr.exe from Windows 2K3 Sp1

checksum generated with Microsoft tool fciv
0f1ce9cbcd35a30d285c1eb672092778 ramdisk.sys
4352373bc08ffa6d8ffdb20a3ba5bc9a SETUPLDR.BIN

I then use PEtoUSB to move the files to the USB stick.

I uploaded the logfile for the compile of EarlyStarter

Need any more info?

Hi Psadi,

EarlyStarter creates ramdisk / modelram just after rpcss service started.
Would you please upload or PM complete log file and setupreg.hiv, so i can reproduce.
What's your version of winbuilder?


Thank you.

Peter

#15 Psadi

Psadi
  • Members
  • 7 posts
  •  
    Sweden

Posted 08 May 2009 - 11:00 AM

Im using Winbuilder 076.
Im using windows XP SP2 as source.

I dont have any apps in this build to reduce the time it takes to compile.

I uncheck everyting in EarlyStart but it also failed in BSOD

I built the cd version also, moved the setuplodr.bin from the iso to the usb but same result with BSOD

Dont know if its relevant but it looks like its accesing the USB at the time it BSOD.

This time its the full log of the compilation and the setupreg.hiv file both file is the zip file.

Attached Files

  • Attached File  log.zip   159.21KB   388 downloads


#16 fxscrpt

fxscrpt

    Frequent Member

  • .script developer
  • 328 posts
  •  
    Germany

Posted 08 May 2009 - 11:49 PM

Im using Winbuilder 076.
Im using windows XP SP2 as source.

I dont have any apps in this build to reduce the time it takes to compile.

I uncheck everyting in EarlyStart but it also failed in BSOD

I built the cd version also, moved the setuplodr.bin from the iso to the usb but same result with BSOD

Dont know if its relevant but it looks like its accesing the USB at the time it BSOD.

This time its the full log of the compilation and the setupreg.hiv file both file is the zip file.

Hi Psadi,

I think earlystarter is not the bad boy.
But it shows an important problem: registry permissions.

Please mount setupreg.hiv from your attachment and try to open

ControlSet001\CriticalDeviceDatabase\....
or
ControlSet001\services\....

Most of them are not accessible, because DACL completely removed!

Earlystartet doesn't set any registry permissions.
My first suggestion is to repeat build without DPs Mass Storage Drivers.

:D

Peter

Edit:

Psadi, please try attached script.
(Basic\Build\3 - SetACL.script. This script should run just after hivesFactory)

The script fixes permissions on PE registry hives,
but the reason for corrupted setupreg.hiv you posted is not found.

Please upload original setupreg.hiv from source.
Whats your Host OS?

Thank you

Peter

Attached Files



#17 Lancelot

Lancelot

    Frequent Member

  • .script developer
  • 5013 posts
  • Location:Turkiye/Izmir
  • Interests:*Mechanical stuff and Physics,
    *LiveXP, BartPE, SherpyaXPE,
    *Basketball and Looong Walking,
    *Buying outwear for my girlf (Reason: Girls are stupid about buying bad stuff to make themselves uglier :))
    *Girls (Lyric: Girl,...., You will be a womann, Soon)
    *Answering questions for "Meaning of life",
    *Helping people,

    Kung with LiveXP, Fu with Peter :)
  •  
    Turkey

Posted 09 May 2009 - 06:27 AM

Hi Psadi

thanks for continuing support and log :D

i couldnt reproduce issue with petousb (remind me old days ;) ) ! only if i disable usb support i get bsod screen which is expected (ps: maybe redownloading usb support may help !!)

Thanks for short ;) log :) :D
In your log i noticed you enabled both:
Winlogon / Shell Version & Misc Settings Version
but you should enable only one (wb automatically switches selections ;) ) , Winlogon / Shell Version is default

also you disabled coremain :)

anyway, :(

I built the cd version also, moved the setuplodr.bin from the iso to the usb but same result with BSOD

Easier way: To use create iso with your trials, on createiso script enable "Add Win 2k3sp1........" ( file location is the same with bootsdi) , no need to enable fbwf. Than follow usual petousb way...


Here is what i do:
I already have ufd ntldr bootable so:
i build ;) (xpsp2enu source)
opened petousb
_source path bla:\blablabla\Target\LiveXP
_enable filecopy (overwrite always)
_start

than didnt touch anything on ufd,
just reboot the pc, everything worked nice.
here is the log file of my build ( :) )

http://lancelot.winb...0509_074440.rar

I hope we find the bad boy(s) around with your help.


Edit:
@Psadi , fxscrpt edit previous post


#18 jsgage

jsgage

    Member

  • Members
  • 31 posts
  •  
    United Kingdom

Posted 09 May 2009 - 02:32 PM

same problems with trying to get my live xp build to go on a usb stick and boot
i can get the bootsdi.img to boot from mem via my boot.ini modded PELDR and .sif

but if i prep usbpen with pe2usb and select ..LiveXP/Target as source
when boot im getting

STOP: 0x0000007B (0xF78d2528,0xC0000034,0x00000000,0x00000000)

I didnt quite a while ago using older versions but as most thing change i didnt keep backup
plus there was lot of scripts not out yet ,netframework 1+2 being most needed as you can see
from my log ive got a lot in it. and very few warnings no errors im learning all the time
thanks to you guys esp Lancelot livexp seems to have taken masive jumps now .

2nd problem not sure if related

Also if i build iso it works fine in qemu but when wrote to cdr and boot im getting
MULTIPLE_IRP_COMPLETE_REQUESTS
STOP: 0x00000044 (0X8B099008,0xC0000D62,0x00000000,0x00000000)
STOP: 0x00000044 0X8B098360
STOP: 0x00000044 0X8AF81008
STOP: 0x00000044 0X8B1721A8
STOP: 0x00000044 0X8B0AECD8

only one at a time but ive got a pile of beer mats. a couple were booted on diff machine as this ones
got sata other hasnt .This is because a driver has requested (by using the IoCompleteRequest function)
that an I/O request packet (IRP) needs to be completed, but the packet has already been completed.
so say microsoft http://support.microsoft.com/kb/294876 . Ive searched for dupe driver in build but no joy

going to try adding see what happens

Ive included log1 recompiled saved reghive + log2

just recomplied with 3___SetACL.script added and included new reghive log3 and orig reghive form source
my machines a newish lapptop with sata duel core 2gig mem running multi boot xp pro ,win2000 ,grub and PELDR
the xp pro source is the same one installed and used for building (of cd in folder)

ps
unrelated to above error
trying a simuler setup with Projects,bartpe found error in NetCore.Script v33 [ProjInfo]

IniWrite,"%ProjectInfo%","UPX-Switches","netplwiz.dll,"--best --compress-resources=0"
IniWrite,"%ProjectInfo%","UPX-Switches","netshell.dll,"--best --compress-resources=0"

i only think this is right way as it doesnt error now. im no script god just looking error in log
and trying to find syntax errors most of its above me.

IniWrite,"%ProjectInfo%","UPX-Switches","netplwiz.dll","--best --compress-resources=0"
IniWrite,"%ProjectInfo%","UPX-Switches","netshell.dll","--best --compress-resources=0"

Attached Files

  • Attached File  post.7z   682.01KB   398 downloads


#19 fxscrpt

fxscrpt

    Frequent Member

  • .script developer
  • 328 posts
  •  
    Germany

Posted 09 May 2009 - 04:24 PM

Hello jsgage,

your setupreg.hiv files have no permissions issues. :D



2nd problem not sure if related

Also if i build iso it works fine in qemu but when wrote to cdr and boot im getting
MULTIPLE_IRP_COMPLETE_REQUESTS
STOP: 0x00000044 (0X8B099008,0xC0000D62,0x00000000,0x00000000)
STOP: 0x00000044 0X8B098360
STOP: 0x00000044 0X8AF81008
STOP: 0x00000044 0X8B1721A8
STOP: 0x00000044 0X8B0AECD8

only one at a time but ive got a pile of beer mats. a couple were booted on diff machine as this ones
got sata other hasnt .This is because a driver has requested (by using the IoCompleteRequest function)
that an I/O request packet (IRP) needs to be completed, but the packet has already been completed.
so say microsoft http://support.microsoft.com/kb/294876 . Ive searched for dupe driver in build but no joy

going to try adding see what happens

Ive included log1 recompiled saved reghive + log2

just recomplied with 3___SetACL.script added and included new reghive log3 and orig reghive form source
my machines a newish lapptop with sata duel core 2gig mem running multi boot xp pro ,win2000 ,grub and PELDR
the xp pro source is the same one installed and used for building (of cd in folder)

I'll bet you FBWF.sys makes STOP: 0x00000044.
Disable FBWF or use version 2.0.965.0 / 6.0.6000.20484.

Some hints:

You are running some outdated scripts. Please update to current versions.
You are running WB077b2. Please switch to nonbeta WB076.
Enable Finish\0 RegFactory\RegFactory.script. Else Regfactory scripts (Basic\Shells\Core)
have no effect (excepting copied files.)

Wherefrom is your setupreg.hiv file. Usbpen or %TargetDir%?

:D

Peter

#20 Lancelot

Lancelot

    Frequent Member

  • .script developer
  • 5013 posts
  • Location:Turkiye/Izmir
  • Interests:*Mechanical stuff and Physics,
    *LiveXP, BartPE, SherpyaXPE,
    *Basketball and Looong Walking,
    *Buying outwear for my girlf (Reason: Girls are stupid about buying bad stuff to make themselves uglier :))
    *Girls (Lyric: Girl,...., You will be a womann, Soon)
    *Answering questions for "Meaning of life",
    *Helping people,

    Kung with LiveXP, Fu with Peter :)
  •  
    Turkey

Posted 10 May 2009 - 08:21 AM

Hi jsgage

Thank you for the support

Some more hints:

when there is a problem please dont test with non project scripts :D

and to make life easier with faster builded tests check this log for enabled scripts
(click disable regfactory first than follow the log)
http://lancelot.winb...0509_074440.rar

if you succeed with this build --> usb etc.., than you are on the way for finding the problem :D And with your support we are on the way of finding bad boys.

Cu

#21 Psadi

Psadi
  • Members
  • 7 posts
  •  
    Sweden

Posted 11 May 2009 - 09:19 AM

Psadi, please try attached script.
(Basic\Build\3 - SetACL.script. This script should run just after hivesFactory)

The script fixes permissions on PE registry hives,
but the reason for corrupted setupreg.hiv you posted is not found.

Please upload original setupreg.hiv from source.
Whats your Host OS?

Thank you

Peter


Hi fxscrpt
The computer I used was a domain attached computer running as local admin with Windows XP SP2. To verify I installed Windows XP SP3 in a vmware server not domain attached. I dowloaded a fresh liveXP used defaults settings, changed to BootSDI. Removed all apps. I used Windows XP SP2 as source and it builds without any errors. I checked the setupreg.hiv and for me it looked OK, I upload it so that you can verify. I still get BSOD when booting from the USB. I added the SetACL.script as 4 - SetACL.script.

Psadi

Attached Files

  • Attached File  log.zip   159.84KB   486 downloads


#22 fxscrpt

fxscrpt

    Frequent Member

  • .script developer
  • 328 posts
  •  
    Germany

Posted 11 May 2009 - 01:53 PM

Hi fxscrpt
The computer I used was a domain attached computer running as local admin with Windows XP SP2. To verify I installed Windows XP SP3 in a vmware server not domain attached. I dowloaded a fresh liveXP used defaults settings, changed to BootSDI. Removed all apps. I used Windows XP SP2 as source and it builds without any errors. I checked the setupreg.hiv and for me it looked OK, I upload it so that you can verify. I still get BSOD when booting from the USB. I added the SetACL.script as 4 - SetACL.script.

Psadi

Hi Psadi,

i'm still not able to open registry keys using your setupreg.hiv file.
(i guess same problem for software/default)

For example criticaldevicedatabase > error.jpg.

I have transferred your file to PE for loading as 'SYSTEM'
and listed permissions (see info1.jpg),
then replaced permissions (info2.jpg).

Lets make a try :
Replace your setupreg.hiv file by new one.


Load software registry hive in regedit.exe:

1.
menu > file > load hive > navigate to ..\Target\LiveXP\I386\SYSTEM32\config\software > type tmp for key name.
2.
navigate to HKLM\tmp > right click > select permissions.
3.
add Administrators/System/local service/network service.
4.
for every entry set 'Full Control' in 'Allow' column and clear 'Deny' column.
5.
Click 'Apply'
6.
Click 'Advanced', then select 'Replace permission entries on all ....' , then click 'Apply'
7.
menu > unload hive.


Repeat step 1..7 for \Target\LiveXP\I386\SYSTEM32\config\default file.

Rerun BootSDI.script.

Any success booting USB?

:D

Peter

Attached Thumbnails

  • error.jpg
  • info1.jpg
  • info2.jpg

Attached Files



#23 Psadi

Psadi
  • Members
  • 7 posts
  •  
    Sweden

Posted 11 May 2009 - 07:21 PM

Any success booting USB?

:D

Peter


Nope :D

I tried the above and didnt get it too work. I checked the software and default settings on the USB after this and the permissions didnt follow to the USB device (dont know if they should). I tested to set the permission as your suggestion on the USB device directly but no luck there. This was running with the setACL script.

If I start it in qemu and burn it to a CD it starts fine, its just when I put it on the USB stick with petousb it fails it looks like.

Got any more ideas for me to try ;)

Edit:
Spelling, I need to install dictionary

#24 fxscrpt

fxscrpt

    Frequent Member

  • .script developer
  • 328 posts
  •  
    Germany

Posted 11 May 2009 - 10:46 PM

Nope :D

I tried the above and didnt get it too work. I checked the software and default settings on the USB after this and the permissions didnt follow to the USB device (dont know if they should). I tested to set the permission as your suggestion on the USB device directly but no luck there. This was running with the setACL script.

If I start it in qemu and burn it to a CD it starts fine, its just when I put it on the USB stick with petousb it fails it looks like.

Got any more ideas for me to try ;)

Edit:
Spelling, I need to install dictionary

Psadi, today i will format my stick and check for possible petousb permission alterations.

if i understand right,
1. your posted setupreg.hiv was always from usb stick
2. you can succesfully set permissions using files from %Targetdir%
3. registry permissions didnt follow to the USB stick (yes they should).

:D

Peter

#25 Psadi

Psadi
  • Members
  • 7 posts
  •  
    Sweden

Posted 12 May 2009 - 07:19 AM

Psadi, today i will format my stick and check for possible petousb permission alterations.

if i understand right,
1. your posted setupreg.hiv was always from usb stick
2. you can succesfully set permissions using files from %Targetdir%
3. registry permissions didnt follow to the USB stick (yes they should).

:D

Peter


1. No it was from the %Targetdir%, adding from the usb stick in this post (This is from a non domain computer)

2. Yes, I have no problem setting the permission using regedit and on the system and software hives.

3. When I tried today they did must have made some error before. Though still got BSOD when I booted from the usb stick.

Attached Files






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users