Re: IRQL_NOT_LESS_OR_EQUAL and EWF

KM,

- yes, i use SDI loader to create a sdi file, then copy all the files
created by TD to the sdi file.

- i didn't include any EWF components in my image, why did you ask
about EWF? is there something i am missing??

--------------------------------------------
i use "sdimgr /writedisk:0" to write the image to my disk, then did
some configurations afterwards, then create a golden image

on my bootable CD, i use "sdimgr /writepart:c:" to write the image to
the target
------------------------------

- yes, the image on my bootable CD is the same as the one i created in
Step 6: golden.sdi

- if i use Ghost to capture the post-FBA and post-Fbreseal image, when
that image generate unique SID once it's written to the target and
then rebooted.

-so far, SDI approach has worked without any problem. my developing
and target machines have the same hardwares(motherboard, hard drive,
and so on), i guess that's why i haven't encounter any problem. will
Ghost approach preserves disk geomertry parameters??

i guess another way i can do it is to copy all the files on c: drive
to my bootable CD, then write a scrip to format the targe and xcopy
those files.

thanks!



KM wrote:
mike,

Please disregard my question about the SDI file size. It wasn't relevant to your issues.

With Ghost you won't end up with 40Gb size. Ghost will only capture the data sectors on the disk and will also compress the image
(you will likely end up with even smaller size than 750M).

When you say "copy the image files to a SDI file", do you mean you used SDI Loader on your dev machine? The thing is that it better
be done on the target to preserve disk geometry parameters. Let me put it this way, to get media to boot you should partition and
format it on target machine. But again, since you got the image booted you may not want to worry about it now.

What EWF mode do you use? Since you are switching from reading *partition* and writing *disk* it should be EWF RAM Reg mode.

And, I suppose, on the step 7 you write a *different* image to CD, not the same golden image you just captured, right?

--
=========
Regards,
KM

KM,

why did you say
------------------------------------------------------------------------------------------------
sdimgr myimage.sdi /writedisk:0 /yes

"The approach is pretty dangerous since SDI doesn't deal with MBR
properly. But since you got your image booted, it is not an issue
for you.
What's the SDI file size?
Did you try using Ghost or other cloning tools?
Or, better, did you try formatting the target partition and [x]copying
all the files and folders of your image over there? "
--------------------

- what is wrong with SDI file?? i am worried now......
- the combine size of my image is about 750MB, my hard drive is about
40GB, if i use Ghost, will that create a image of 40GB, which is not
what i want

here is my process:
1.) build the image using TD
2.) copy the image files to a SDI file, the SDI file size is about
750MB, put this image on the network share ( will run "net use y:
\\192.144.0.1\\shared" to mount it later
3.) boot up to WPE, write the image to the disk
>diskpart
diskpart>select disk 0
diskpart>clean
diskpart>create partition primary
diskpart>select partition 1
diskpart>exit
>sdimgr y:\image.sdi /writedisk:0: /yes
>diskpart
diskpart>select disk 0
diskpart>select partition 1
diskpart>active
diskpart>exit
>exit
4.) reboot to the image on disk, this will run through FBA process, and
etc ( why did you say this approach is dangerous?? shoud i format a
NTFS partition of about 750 MB, then xcopy all the files)
5.) add some software and configurations to the image and run
"fbreseal"
6.) reboot back to WPE, write the image to a SDI file on the network
share
>sdimgr y:\golden.sdi /readpart:c:
7.) create a bootable CD with the image
here is the script on the CD, which i use to write the image to the
target
>diskpart /s format.bat
----------------------format.bat------------------------
>select disk 0
>clean
>create partition primary size=750
>assign letter=c
>select partition 1
------------------------------------------------------------
>sdimgr x:\golden.sdi /writepart:c: /yes
>diskpart /s extend.bat
-------------------extend.bat--------------------
>select disk 0
>select partition 1
>extend disk 0
>active
----------------------------------------------------------
extend.bat will extend the C drive from 750MB to 40GB

could you please let me if you see any problem in my approach. i have
been doing this for a while, have not seen any noticeable problem so
far

thanks!
p.s. i wil look into your suggestions about blue screen later











KM wrote:
Mike,

Comments inline..

i just read somewhere which mentioned always add EWF components in TD
to the image. since i am not booting from read-only media, i don't
understand why i need EWF componennts at all.

Well, read-only media is not only the application of EWF. But if you system specs do not require EWF, you don't need to include
it.

this doesn't happen consistantly on the system, i just installed my
image on a system, it wrote the image to the disk, then reboot; when i
login, it says something like "new hardward detected, it needs to be
rebooted....."(do you know why it always has to be rebooted twice after
writing the image to disk?),

It does't.
Does the new hardware identical to the old hardware where you capture the image from?
Do you use system cloning? If you do, what setings you are removing or keeping?

Also, what new hardward is getting detected? If you click on he notificaiton (or go to Device Manager directly) it will show you.

so i rebooted, then i got this
"IRQL_NOT_LESS_OR_EQUAL " error.

Anything on that BSOD screen beside the IRQL_NOT_LESS_OR_EQUAL?

so i turned off the power, rebooted
again, this time, it worked fine.

if i got the error first time, why i didn't get it the second time?
should this happen consistantly instead of randomly??

With the IRQL_NOT_LESS_OR_EQUAL it may happen inconsistently, depending on the faulty driver.

How does your \Windows\SetupApi.log file looks like after the new image deployment?
In other words, what's the difference you can see in that log file if you compare it before and after the new image install?

oh, my image is using NTFS, so i didn't format my disk, just write the

That's fine. You don't have to since you are transfering raw disk data.

image to it directly, will that cause this problem.

diskpart>select disk 0
diskpart>clean
diskpart>create partition primary
diskpart>selection partition 1

Better make this partitioon active.

sdimgr myimage.sdi /writedisk:0 /yes

The approach is pretty dangerous since SDI doesn't deal with MBR properly. But since you got your image booted, it is not an
issue
for you.
What's the SDI file size?
Did you try using Ghost or other cloning tools?
Or, better, did you try formatting the target partition and [x]copying all the files and folders of your image over there?

--
=========
Regards,
KM

KM wrote:
mike,

That is a bad one. I suppose you already looked here:
http://groups-beta.google.com/group/microsoft.public.windowsxp.embedded/search?hl=en&group=microsoft.public.windowsxp.embedded&q=IRQL_NOT_LESS_OR_EQUAL&qt_g=Search+this+group

Do you have EWF enabled on the image? What mode of EWF you use?
Does the BSOD screen show the faulty driver?
Were there any errors in FBALog.txt?
Could you check the Ever Viewer log to see if any error appears there related to the BSOD?

I couldn't quite understand your second sentence. What you meant by "always include EWF in XPE image"?

Are you working with SP2? (EWF on SP1 had some problems on certain MBs).

And, very good approach would be to connect to your target with a KD (Kernel Debugger, WinDbg) from another computer and catch
the
blue screen to investigate more the call stack.

--
=========
Regards,
KM


"mike-ca" <bosanovav1@xxxxxxxxx> wrote in message news:1162493295.151008.48440@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
sometimes when i reboot my XPE, i got blue screen with the message
"IRQL_NOT_LESS_OR_EQUAL".

i googled this, someone suggest to always include EWF in XPE image to
avoid this problem. is that true? i don't understand the connection
here. can anyone explain this to me.

thanks!




.

Relevant Pages

  • Re: IRQL_NOT_LESS_OR_EQUAL and EWF
    ... i don't recall anything on BSOD. ... not EWF required. ... the OS to write to disk: http://msdn.microsoft.com/library/en-us/xpehelp/html/xeconElToritoCDAsDisk.asp. ... created by TD to the sdi file. ...
    (microsoft.public.windowsxp.embedded)
  • Re: IRQL_NOT_LESS_OR_EQUAL and EWF
    ... I forgot that we already discussed the EWF points. ... Ghost would work better around deploying disk data but nothing is perfect. ... created by TD to the sdi file. ... Or, better, did you try formatting the target partition and copying ...
    (microsoft.public.windowsxp.embedded)
  • Re: IRQL_NOT_LESS_OR_EQUAL and EWF
    ... not EWF required. ... Insert the WinXPE SP1 Disk 1 CD ... created by TD to the sdi file. ... Or, better, did you try formatting the target partition and copying ...
    (microsoft.public.windowsxp.embedded)
  • Re: IRQL_NOT_LESS_OR_EQUAL and EWF
    ... i ran tap.exe on my target syste, and rebuilt a image, that seems ... not EWF required. ... the OS to write to disk: http://msdn.microsoft.com/library/en-us/xpehelp/html/xeconElToritoCDAsDisk.asp. ... created by TD to the sdi file. ...
    (microsoft.public.windowsxp.embedded)
  • Re: IRQL_NOT_LESS_OR_EQUAL and EWF
    ... the DVD model on my target is different from the one on my build ... not EWF required. ... the OS to write to disk: http://msdn.microsoft.com/library/en-us/xpehelp/html/xeconElToritoCDAsDisk.asp. ... created by TD to the sdi file. ...
    (microsoft.public.windowsxp.embedded)