Is minlogon macro sample write protected for SDI devices?

[thx]

Hi,

I'm working withthe minlogon macro sample.

I've successfully botted it in VMWare and can work in the console.

When I do run tap.exe from within the VM, I see that devices.pmq is present.

When I shutdown the VM and browse thru the SDI disk file on my WinXP
system, no changes were written to the image?

1. Is this minlogon sample macro somehow defaulting to write protection?

2. Are SDI files write protected by default?

3. Has anyone else seen this B4 with SDI files?

TIA

 

[Brad Combs]

Hello,

To make sure I follow you:

You started VM ware and loaded an SDI file into RAM and booted from it? If
that is the case then yes the SDI file will not save the changes since it's
actually running from RAM.

Is that your setup?

HTH,
Brad

 

[thx]

Hello,

To make sure I follow you:

You started VM ware and loaded an SDI file into RAM and booted from it? If
that is the case then yes the SDI file will not save the changes since it's
actually running from RAM.

Is that your setup?

HTH,
Brad

Yes Brad, exactly what I have.

Would you believe that "sometimes", the devices.pmq file is still
present on the SDI file, when I peruse it from WinXP?

I haven't figured out how, but somehow changes are committed.

I may have started a new console, ie. start command, but don't recall
the exact steps.

Thx

 

[dferencz]

It sounds the like the XPe image is not properly flushing the HD write
cache. Try this: include the XPEPM (embedded power management) utility
in your image, and be sure to shut down with "xpepm -shutdown" before
halting the VMware session.

-- Don