The Windows XP utility schtasks can be used to view/query/change/run the scheduled tasks from the command line.
Remote machines can be accessed using psexec.
Wednesday, July 1, 2009
Wednesday, June 24, 2009
check shockwave flash versions
The shockwave page has test apps http://www.adobe.com/shockwave/welcome/
Friday, May 22, 2009
viewing windows stored passwords
To access the windows stored passwords for network resources:
rundll32.exe keymgr.dll, KRShowKeyMgr
from:
http://www.windowsnetworking.com/kbase/WindowsTips/WindowsXP/AdminTips/Security/RemoveSavedPasswords.html
http://www.tech-recipes.com/rx/1602/xp_remove_saved_passwords_and_usernames/
rundll32.exe keymgr.dll, KRShowKeyMgr
from:
http://www.windowsnetworking.com/kbase/WindowsTips/WindowsXP/AdminTips/Security/RemoveSavedPasswords.html
http://www.tech-recipes.com/rx/1602/xp_remove_saved_passwords_and_usernames/
Monday, April 13, 2009
Wednesday, April 1, 2009
Managed and unmanaged code
Lessons learned from working in the mixed mode c++ (managed and unmanaged code).
"Managed code calls unmanaged code" is a pinvoke (platform invoke) or IJW (it just works)
"Unmanaged code calls managed code" is called a reverse pinvoke. It is restricted to types that exist the same in both code types i.e. basic types and properly ordered structs of basic types.
The term "managed" is used in 2 different aspects:
compilation target (native vs MSIL)
"#pragma managed" and "#pragma unmanaged" are used to define what the code compiles to
by default all code compiled with the /clr option will be MSIL
NON CLS classes can have mixed compilation - some native and some MSIL - but native code can not use managed types directly
platform target (internal to dotNet vs CLS [Common Language Specification])
CLS code is accessible to managed code and must be compiled to MSIL.
This is where rules about no mixing of managed and unmanaged class inheritance apply. Although it should say that CLS class can not inherit from non-CLS classes and non-CLS class can not inherit from a CLS class.
"Managed code calls unmanaged code" is a pinvoke (platform invoke) or IJW (it just works)
"Unmanaged code calls managed code" is called a reverse pinvoke. It is restricted to types that exist the same in both code types i.e. basic types and properly ordered structs of basic types.
The term "managed" is used in 2 different aspects:
compilation target (native vs MSIL)
"#pragma managed" and "#pragma unmanaged" are used to define what the code compiles to
by default all code compiled with the /clr option will be MSIL
NON CLS classes can have mixed compilation - some native and some MSIL - but native code can not use managed types directly
platform target (internal to dotNet vs CLS [Common Language Specification])
CLS code is accessible to managed code and must be compiled to MSIL.
This is where rules about no mixing of managed and unmanaged class inheritance apply. Although it should say that CLS class can not inherit from non-CLS classes and non-CLS class can not inherit from a CLS class.
Friday, March 6, 2009
windows logging off after clone
After cloning a disk partition, windows xp will remember the disk letter if it saw it before and will reuse that letter when reloading.
The letter needs to be purged from the registry.
see
http://www.goodells.net/multiboot/partsigs.htm for more information.
running regedit (remote) in bartpe allows to edit the registry on the machine to remove the known drive letters.
In case the site goes away the registry key is
The letter needs to be purged from the registry.
see
http://www.goodells.net/multiboot/partsigs.htm for more information.
running regedit (remote) in bartpe allows to edit the registry on the machine to remove the known drive letters.
In case the site goes away the registry key is
[HKEY_LOCAL_MACHINE\System\MountedDevices]
Thursday, February 19, 2009
NFS issue
The issue:
An existing NFS system was failing client connections.
On the client:
mount failed, reason given by server: Permission denied
On the server (Fedora Core 3):
rpc.mountd: authenticated mount request from
The solution was to add the following to /etc/fstab
nfsd /proc/fs/nfsd nfsd auto,defaults 0 0
and remount it by
mount -a
An existing NFS system was failing client connections.
On the client:
mount failed, reason given by server: Permission denied
On the server (Fedora Core 3):
rpc.mountd: authenticated mount request from
The solution was to add the following to /etc/fstab
nfsd /proc/fs/nfsd nfsd auto,defaults 0 0
and remount it by
mount -a
Subscribe to:
Posts (Atom)