jdoe

Why calling it Windows 7, when it seems that it's just the next version of Vista (6.0 to 6.1)

I thought it was for SP3 RC1 but anyway, there is a typo mistake somewhere

Fyyre, I don't know where you got that but it's not good. "xor eax, eax" and "inc eax" should be 33C040 not 33C041 And at offset EC95 there is no "xor eax, eax" but "xor ecx, ecx" which is 33C9 ----------------------- To permanently disable Windows File Protection - Windows XP Pro SP3 (5.1.2600.3264) Without using the registry. At offset EC84, replace 83F89D7508 by 3BC0EB3290 cmp eax, FFFFFF9D jne 76C6F891 by cmp eax, eax jmp 76C6F8BA sfc_os.zip

awergh, If you tried MASM, I suppose your target is the Windows platform. In my opinion, MASM is the best assembler but it is not free for commercial use (unless you have Visual Studio Pro), but for freeware or personal use it's ok (almost all SDK and DDK include MASM). Finding an IDE for assembly is not easy and I'm surprised that you had problems with RadAsm because I tried it once and seems to be a good one. On the other hand, assembly makes more sense to be coded in text files and use command-line to build your programs. RC.EXE RSRC.RC CVTRES.EXE /MACHINE:X86 RSRC.RES ML.EXE /c /coff PROGRAM.ASM LINK.EXE /SUBSYSTEM:WINDOWS /OUT:PROGRAM.EXE *.OBJ or (console program) LINK.EXE /SUBSYSTEM:CONSOLE /OUT:PROGRAM.EXE *.OBJ or (static library) LINK.EXE -lib /OUT:LIBRARY.LIB *.OBJ The best start is downloading MASM32 Project and looking at the many tutorials and examples. MASM32 Iczelion's Win32 Assembly Homepage MASM Programming Style Microsoft MASM Programmer's Guide Microsoft Macro Assembler Reference ASM Community Messageboard If you don't already have experience with one programming language, assembly may not be the good one to start with but I guess it's not your case. Good luck and don't give up. It takes time but it worth it.

These two links are a good start to understand how to use COM in your applications. Introduction to COM - What It Is and How to Use It COM in plain C

For those who were using my patched SFC_OS.DLL (WFP disabled permanently without dealing with the registry) just post the latest SFC_OS.DLL from SP3 and I'll patch it. I'm curious to see how Microsoft did try to avoid us from disabling it this time

gunsmokingman, I just would like to know if there is a reason why you always use DIM when there is no data types in VBScripts. IMHO, they are useless but why you use them anyway ?

RunOnce

melnib00ne, With DAO 3.6 Set dao = CreateObject("DAO.DBEngine.36") Set db = dao.OpenDatabase("DATABASE.MDB") Set rst = db.OpenRecordset("TABLE") rst.AddNew rst("FIELD") = "Data" rst.Update rst.Close Set dao = CreateObject("DAO.DBEngine.36") Set db = dao.OpenDatabase("DATABASE.MDB") Set rst = db.OpenRecordset("SELECT FIELD1 FROM TABLE WHERE FIELD2='Criteria'") rst.Edit rst("FIELD1") = "Data" rst.Update rst.Close B)

MASM programming is not very popular and there is only very few members here that still use assembly. Don't be surprised that there is no rush for helping you. Moreover, programming is not the main objective of this board. For a real assembly board you should go to The MASM forum

AleXnderRT, For your information... 1) ECX is not a register that need to be preserved 2) Memory freed to soon is when you use memory allocation API like HeapAlloc and use the pointer after a call to HeapFree Did you tried running your VBA module in debug mode and see where it crash ? That way it could be easier to know which DLL function cause the problem. Look your PM for my e-mail address. Regards

Did you build a COM DLL or just a DLL with exported functions ? Maybe it's a register preservation problem or memory freed to soon or a bad pointer or a mistake in COM implementation. Without source code it gonna be hard to help but if I were you I wouldn't search outside your DLL, the problem is in there. I'm a MASM coder so if you don't mind posting the source, I'll look at it.

jcarle, Sure a program doing a scan, every 1 second for example, adds a little cpu activity but if the drive is not connected then it does not create activity on that disk. A call to GetDriveType, PathIsRoot or PathIsDirectory might be somehow a good choice IMHO, depending on which one have the less footprints.

It should looks like this... Set objShell = CreateObject("WScript.Shell") Set objSys = GetObject("winmgmts:{(Shutdown)}").ExecQuery("Select * From Win32_OperatingSystem") strAppExe="mstsc.exe %logonserver%\netlogon\vmware\VM-W2K\vmw-%username%.rdp" objShell.Run strAppExe, , True For Each v In objSys v.Win32Shutdown(0) ' Or Win32Shutdown(4) to force logoff Next I'm not sure about the use of %logonserver% and %username%. Did you really make it work once ?