I was writing an editor, using the XSLT bound to an XML document to generate a HTML form, which used Javascript to tie into a XML DOM. I wanted to be able to save, and I found a way using a FileSystemObject activex control, but I was just wondering why I couldnt save using the Javascript. Thanks Jesse Rosalia

I am using Javascript, accessing a MSXML4.0 DOMDocument, in conjunction with a .XML and .XSL document. The .XSL document transforms the XML into a web page with a few forms, and a save button. There is javascript code to load the XML document into a DOM object on page load, modify the XML document in memory when the forms are modified, and save the DOM object when a button is pushed, but when I attempt to make a call to the DOM objects save(...) method, it throws a "Access Denied" javascript error. I have written a C++ app with a web browser control which does basically the same thing...browse to the file in the browser, open the file into a DOM (this time in C++, not JScript), and save the DOM in C++ and this works with no problem. Is there some sort of massaging I need to do to the filename, or some permissions I need to adjust to be able to save a file using the DOMDocument object in Javascript? Thanks in advance

Im developing an NDIS adapter driver, to pass standard TCP/IP traffic over a nonstandard medium, and am having problems with ICMP echo request/replies. With the driver set up on 2 machines (IPs 1.2.3.4 and 1.2.3.5), I can drop to a command prompt on 1.2.3.4 and ping 1.2.3.5. An ARP is given to my driver, which is sent to the broadcast address, and 1.2.3.5 sends an ARP reply back to 1.2.3.4. An ICMP echo request is then transmitted from 1.2.3.4 to 1.2.3.5, and it is sent through my driver to 1.2.3.5. It appears to be successful in transmission, as the packet is packaged up in an NDIS_PACKET, and sent up to NDIS, and NDIS calls my MiniportReturnPacket function, however 1.2.3.5 never generates an ICMP reply. I have verified that the IPs and subnet masks are set up correctly, and that even though Im using the same driver on both machines, the MAC address's are unique. Anyone have any ideas as to what could be wrong? Thanks in advance. Jesse Rosalia

Ahhh hah!...Thanks for your reply...as I was formulating a response to this it dawned on me that I never tried to allocate the memory to its prefered size, and check the headers and footers then...in fact you are correct that it does allocate the reported size. This also brought an interesting quirk with calloc to my attention...it will write 0s to the requested size, not the allocated size...very confusing. Thanks for your help...I think I have a good grip on this stuff now. :) -Jesse Rosalia

No, I was using different objects in the 2 different programs...but I think Ive all but answered all the questions I had with that through good ol fashion research and dumb luck :). As for the malloc issue...it doesnt, in my experience, actually allocate the rounded up size in bytes...it allocates what you tell it to, and then reports that it allocated the rounded up size. Am I missing something, or do I need to have something defined somewhere to make this work properly? Thanks for your response, by the way :) -Jesse Rosalia

First question is...when using malloc to allocate memory and _msize to retrieve the size in a Release build, the value _msize returns, and also the value stored in the memory block header is rounded up to the nearest multiple of 8 (i.e. 7 is rounded to 8, 100 is rounded to 104, etc). This is not the case in a Debug build. Is there any way to tell the heap manager not to round up? It wouldnt even be so bad if it allocated the rounded up number of bytes, but as it is, if I tell malloc to allocate 100 bytes, it allocates 100 bytes and then tells me it allocated 104, and that isnt good for so many reasons. ;) Next question is...when you use new to allocate an array of structures, such as... CMyClass *pVar = new CMyClass[count] I have one program which will add 4 bytes to the size passed to the new operator, and store count in those 4 bytes, and I have another program in which it does not do that. Is there a way to turn this functionality on or off? It must be some compile time setting, because in the program where it does that, there is an 'add 4' assembler instruction right before the call to new. Thanks a bunch in advance to whomever can answer these 2 :) -Jesse

Thanks...I couldnt find anything to resolve those functions to strings, however your suggestion of a macro gave me an idea that I made work =) -Jesse

Sweet! Thank a bunch :)

Im not familiar with COM aggregation, but I think I can still shed some light on this subject... The purpose of AddRef() and Release(), and the whole reference counter thing, is to insure that a resource isn't unloaded/deallocated/deleted/otherwise removed from existance before everyone is done using it. For instance, when you create a COM object, the counter gets set to 1. When you are done with this object, you call Release(), which brings the counter to 0. There is code (or should be code, if you are implementing these functions yourself) inside Release() that resembles... if (--m_nRef == 0) delete this; return m_nRef; which says "When my reference counter goes to 0, I delete myself, because I am no longer needed." For these reasons, it is recommended you AddRef() every time you store another copy of a interface pointer, and Release when you are done with that pointer, however you do not need to be that crazy about it if you have absolute apriory knowledge that your pointer will not be pulled out from under you. Keep in mind that CoCreateInstance(Ex) sets the reference counter to 1, and QueryInterface makes an implicit AddRef() call, as does many other functions used in creating/connecting to a COM object. Hope this helps. -Jesse

Actually, I think DCOM is the way you want to go. You can programmatically set everything DCOMCNFG does (look into CoCreateInstanceEx for specifying server, and the AppId registry keys and LSA functions for security settings if they apply). Might I suggest, if you are going to use multiple clients off this server, that you turn your COM dll into an exe. COM dlls require a surrogate (very thin wrapper that does nothing really but provide an executable layer) to run on a remote machine, because frankly they themselves arnt enough to sustain an independant process. DCOM provides a default surrogate, DllHost.exe, which isnt bad, but if your goal is to service multiple clients off that remote server, my suggestion would be to turn your DLL into an EXE. One thing I dont understand is who is the client? If its a web browser, all your objects will be "running" on the server, so you dont need to make your client aware of the objects. If its an application, then there isnt really any issue in just registering the needed classes on that client computer, is there? Hope this helps. -Jesse

With the Microsoft Developer studio add-ins, you declare functions in a COM interface, then call a routine (a member of the Application object) AddCommand, which takes amongst other things a string that contains the names of your functions. These are not exported functions, they are standard STDMETHOD(...) functions (which expands to HRESULT virtual __stdcall ...). Any one have any ideas on how they do this? I know you can export the functions, and then use GetProcAddress to look those functions up my name, but these functions are not exported...they are normal exposed members of a COM interface. Anyone have any ideas on how they get away with this? Thanks in advance. -Jesse

Actually I believe you need to use %.2f to get a precision of 2...what you have will produce a string that containts a number with 2 overall digits -Jesse

Actually I believe you need to use %.2f to get a precision of 2...what you have will produce a string that containts a number with 2 overall digits. -Jesse