Re: EWF RAM
- From: "Richard" <REMOVE AT-DOTrwskinnerAT@awesomenetDOTnet>
- Date: Thu, 11 Aug 2005 12:22:47 -0500
It's a Winlogin Image.
Yes, I perform the command "EWFMGR C: Commit" - Sorry, do not have the exact
syntax in front of me but I'm sure that is what it is.
Yes, the timer was for grins, I could do away with it.
Since this is being done from a batch file on a remote laptop, we use the
PSTools, normally all the changes are made without any problem, just
occassionally this happen on reboot, and we are not modifying any OS Files
at all.
We use PSKill to close the applications, Normal Dos copy over the network
(Mapped drive), use PSExec to do the EWFMGR Commit, we Use PSShutdown to
restart the target.
Richard
"Slobodan Brcin (eMVP)" <sbrcin@xxxxxx> wrote in message
news:uHHWRimnFHA.860@xxxxxxxxxxxxxxxxxxxxxxx
> Richard,
>
> Minlogon or winlogon image?
>
> By commit you mean perform commin of EWF, right? This you can do at any
> time that you want. Actual commit is done during the
> gracefull shutdown.
>> Performs a shut down restart with a 15 second timer.
> If you count 15 seconds from EWF commit then there is no need to it, since
> commit operation just set one flag in driver and nothing
> more. Like I said actual commit happens during the shutdown after file
> system is closed.
>
> What API command or utility do you use for computer restrart? You must
> use "gracefull" shutdown. Meaning that if you use some
> higher level programs they should be notified that windows is shuting down
> so that they can close and write their infos.
> Look at function ExitWindowsEx also there are native api functions that
> will skip this shutdown notification.
>
> Regards,
> Slobodan
>
>
>
>
> "Richard" <REMOVE AT-DOTrwskinnerAT@awesomenetDOTnet> wrote in message
> news:OLSxHRmnFHA.2472@xxxxxxxxxxxxxxxxxxxxxxx
>> Here it is again, slightly worded better. I sure hope someone has a
>> pointer
>> or two. We are in really trying to locate this bug and fix it.
>>
>> Over last couple of months we have had some systems hang after performing
>> an
>> upgrade. Let me explain our process/
>>
>> VIA 667 mhz + XPe SP1 + Headless Device + EWF RAM Reg Component + 256
>> megs
>> Ram + 256 Meg Sandisk Industrial
>>
>> We thought it was DUA so we went a different route by running a batch
>> file
>> which maps a drive, and does all the work.
>>
>> A tech plugs into it with laptop and remote desktops to it. He then runs
>> a
>> small batch file on his Laptop to upgrade a few files.
>>
>> Complete Listing of the files that get copied - No DLL's or anything
>> else...
>> 1 Single Exe. file 1.20 megs - Application
>> 1 Single Exe. file 425k - Shell
>> 1 Single Text File 294 Bytes - Version Information
>>
>>
>> Example of the batch file....
>> Maps a local drive on the laptop to the Target.
>> PSKill shuts down the application and shell on the Target, so the file
>> can
>> be copied over the old one.
>> Performs a Commit,
>> Performs a shut down restart with a 15 second timer.
>> Target reboots
>>
>> There is a 5 second delay between each command in the above batch file.
>> The
>> batch file works fine.
>>
>> Each Step of the Batch file has its output redirected to a log file on
>> the
>> techs laptop, showing each command was sucessful, including the commit.
>>
>> Now, after the system is restarted, it hangs at the Windows XP Logo
>> Screen
>> and that is where it stops. I can see it probe the USB and see it probe
>> the
>> com ports like normal, but it hangs as mentioned above.
>>
>> If I remove the CF, I can see all the files okay in a reader. If I copy
>> a
>> new image to it, it works fine.
>>
>> Again, this occurs in both DUA and with the Batch file, but randomly.
>>
>> Any idea why this happens or what file may be getting corrupted? In XPe,
>> do
>> buffers need to be flushed or anything?
>>
>> Thanks,
>> Richard
>>
>>
>>
>>
>
>
.
- Follow-Ups:
- Re: EWF RAM
- From: KM
- Re: EWF RAM
- References:
- EWF RAM
- From: Richard
- Re: EWF RAM
- From: Slobodan Brcin \(eMVP\)
- EWF RAM
- Prev by Date: Re: PID and MSDNAA
- Next by Date: First Embedded Image is running!
- Previous by thread: Re: EWF RAM
- Next by thread: Re: EWF RAM
- Index(es):
Relevant Pages
|