burning DVD failure

Hi there,

I just attempted to burn a DVD on my DELL GX-280 with 2Gb of RAM, 3.8Ghz
CPU. I used a Wscript as such:

Const adFileTypeBinary = 1
index = 1
strISOFile = "c:\users\Alex BB\dvd burn\en_sql_2005_dev_all_dvd.iso"
Set objDiscMaster = CreateObject ( "IMAPI2.MsftDiscMaster2" )
Id = objDiscMaster.Item(index)
Set objRecorder = CreateObject ( "IMAPI2.MsftDiscRecorder2" )
objRecorder.InitializeDiscRecorder(Id)
Set objDataWriter = CreateObject ( "IMAPI2.MsftDiscFormat2Data" )
objDataWriter.Recorder = objRecorder
objDatawriter.ClientName = "ISOTest1"
Wscript.Echo "Writing to disc..."
Set objStream = CreateObject ( "ADODB.Stream" )
objStream.Open
objStream.Type = adFileTypeBinary
objStream.LoadFromFile strISOFile
If objDataWriter.NextWritableAddress = 0 Then
objDataWriter.Write(objStream)
Wscript.Echo "Done"
Else
Wscript.Echo "Cannot write to disc"
End If

I copied the script from this TechNet site (modifying the directory only):

https://www.microsoft.com/technet/scriptcenter/topics/imapi/imapi2-2.mspx#EYH

The burning began and while watching the process in the Task Manager I saw a
huge increase in Memory (Working Set Memory, I think) up to 1.8Gb. Then after
a few minutes an exception was thrown from WScript: Out of Memory.

After I closed the msg window which was modal the memory consumption wound
down slowly and the process was eventually shut down after about a minutes or
so.

My question is: why? I've burned DVDs before with Windows Media Player with
no problem. I've burned some picture images on this machine and attempted to
burn iso images but they all came out sort of hollow, although the eventual
file size was close to what I expected the data did not seem to be there and
I could not use the DVD to install the software. So, I've decided to use a
script since I felt that it would give me a better handle on the process.

Is it a known issue?

Is it possible to improve the script?

Are there other scripts out there that can do the same?

Nore: the iso image I tried to burn is a MSSqlServer eveloper Edition. I am
an MSDN Pro subscriber.

Many thanks in advance.
--
AlexB
.

Relevant Pages

  • Re: Memory problem with Wscript when it is closing
    ... Copy, execute, whatever. ... The memory issue should go away. ... > script which will create another script on a remote machine, ... > Every thing is fine, But sometime, I got run-time error that Wscript ...
    (microsoft.public.scripting.wsh)
  • Re: Problem with ASP on Webserver
    ... No, I know the memory model, I have made my own Virtual memory dump program ... function in the script ... (Accept-Language:) ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Problem with ASP on Webserver
    ... Entrek's TOOLBOX is a lot better for memory stuff. ... function in the script ... (Accept-Language:) ...
    (microsoft.public.windowsce.platbuilder)
  • Critique my code: using Lisp to parse lots of "ps -elf" files in AIX
    ... It's my first use of Lisp at work, ... and another ksh script to analyze the output. ... success using them to diagnose some of their own memory problems, ... an hour to process about an hour's worth of data (i.e. 60 data files). ...
    (comp.lang.lisp)
  • Re: Incude statement - is there such a thing?
    ... I can't imagine any memory usage issues. ... And it that WSF references ... other script files (as the Docs often suggest to be ... > you had 50 statements that you wanted to execute 1000 times in a loop. ...
    (microsoft.public.scripting.vbscript)