Writing CD-R(W)s from VB - solved
Hi there,
I just finished a big part of my current project (which I started almost 2 years ago, lol), named "flamed!",
and - like the thread's name already says - it's supposed to be a cd-writing soft.
Done in almost pure VB6 (I'll tell u later, how it can be done in "pure" VB), so start to cry, all of you who doubted it!! :bigyello:
Its features are right now:
-Blank CD-RWs (quick and full blank)
-Create ISO9660 images for later burning as data discs (only 35 files and no sub-dirs :blush:, but hey, it works!)
-Audio discs (either there exists a big problem with my cd-writer or you really can write only 2 tracks, and then it will produce an error,
oh, and you can only write 44kHz 16bit stereo wavs. But hey, it works :bigyello: )
-CDDA Ripper with CD-Text reading and FreeDB query (only Wav)
-ISO9660 image burner (seems to be working... it seems...)
-ISO Ripper, rips data tracks to ISO9660 image
-BURN-Proof
-Test-Mode
-Track-At-Once Recording (Disc-At-Once for audio discs planned)
-Sector viewer, browse the content of your disc in raw view
-Advanced information about your drive/inserted disc
-Uses ASPI/SPTI drivers for communication with drives
-a nice and modern UI
-should run with Win9x/Me/NT/2000/XP
using Win9x, you need WMI
Under Win9x/Me it uses ASPI, under NT kernels it automatically shall select SPTI.
You can force the use of ASPI drivers by uncomenting the line
"'m_bUseASPI = True" in frmSplash.
The project comes with the free DLL "ASPIshim.dll" from
http://hochfeiler.it/alvise
because VB can't call the functions of wnaspi32.dll.
To be honest, you can, but then you'd have to compile the project
before running it.
You have to replace some API calls, then it will work.
If you want to know how, I can upload a SE version ;)
The source for the GUI components can be found at PSC.
Last, but not least, I'd really be happy to read some comments
(noo, not that "doesn't work!!" stuff :P )
http://actorics.de/flamed.zip (620 kb)
grz
rm
Re: Writing CD-R(W)s from VB - solved
1) Nice project, can you send some example code?
2) http://actorics.de/flamed.zip link doesn't work!
3) Writes only cds?
4) Is it your code or sharing someone's code?
Re: Writing CD-R(W)s from VB - solved
Quote:
Originally Posted by BramVandenbon
Just to all those who did not know :
recently I discovered in windows 2003 server there is a .exe program that allows you to do this using the commandline.
I believe it is cdburn.exe or something like that.
I didn't know this! Does Flamed work using this cdburn.exe file?
Re: Writing CD-R(W)s from VB - solved
Hmm, no idea, never heard of that program.
And btw, That cdburn is part of a package that can be downloaded from the microsoft website. But a long time ago, so I can not really remember its name. :afrog: good luck though
Re: Writing CD-R(W)s from VB - solved
Quote:
1) Nice project, can you send some example code?
2)
http://actorics.de/flamed.zip link doesn't work!
3) Writes only cds?
4) Is it your code or sharing someone's code?
1) Sure:
http://pscode.com/vb/scripts/ShowCod...56918&lngWId=1
2) ^
3) I guess, you'll understand this limitation by looking at the code...
4) 99% my code.
Quote:
Does Flamed work using this cdburn.exe file?
No.
As descriped: "Uses ASPI/SPTI drivers for communication with drives"
That's the way most of the others CD writing programmes work.
Some comments on Flamed v2 (link above):
Changed some values in the ISO9660 writer class,
suddenly it had a strange behavour.
I hadn't the time to fix it, so it's possible,
that it burns nonsense data CDs.
But the audio CD creation should work.
The ASPI driver implementation is a bit slopy,
it's possible that it won't run on Win9x/Me.
Anyways the project is dead.
But somebody who wants to know,
how this stuff really works, can learn a lot from it.
Re: Writing CD-R(W)s from VB - solved
Thanks rm_03!
By the way...nice code!
:) :) :) :)
Re: Writing CD-R(W)s from VB - solved
btw, just for those interested: in the WindowsXP/Windows2003 Resource kit also the following commands were included.
dvdburn.exe <drive> <image> [/erase]
cdburn.exe <drive> image [/options]
Re: Writing CD-R(W)s from VB - solved
I didn't know it!
As i searched in google i found that UltraISO and some other commercial programs use these two files(cdburn.exe & dvdburn.exe) to copy iso files when user creates them!
That means that many commercial software companies use third party dll/ocx/exe files to make their program nice and famous!
Not good... :o :o :o
Re: Writing CD-R(W)s from VB - solved
Re: Writing CD-R(W)s from VB - solved
Can it "rip" floppy disks too?
Re: Writing CD-R(W)s from VB - solved
It's for low level CD/DVD-ROM access.
Why should it read floppy disks? (http://www.vbcity.com/forums/faq.asp...ystem&#TID6975 ?)
Re: Writing CD-R(W)s from VB - solved
Sorry for jumping in on this thread but, I continue to get the "Unable to set the version compatible component: C:\...\WINDOWS\system32\Flamed.dll" error when I load the project for the first time. I've tried 'Starting with Full Compile' and all it does is sit there running...no Flamed.dll created anywhere. Maybe I'm missing something in the readme.txt?
Re: Writing CD-R(W)s from VB - solved
Greetings rm_03,very nice and handy job with flamed v4 version... I realy like it... u get 5 from me :)
But There IS one little problem with your code....
And situation is like this,when i try to burn data cd everything is ok...
with parameter cDataCD.NextSessionAllowed = True :)
But when i put that cd back for continue burning files on (like continuing multissesion) there i get problems....
Everything works and and track is burned on cd,but is not readable,files burned in first session are there (Track 1) and (track 2 is there too..) but i cant acess the files or see them....
So i can tell for sure that that is bug on all platforms and cd writers...
I tried to code some things in FlamedLib but with no sucess.
I assume and suspect that thing is in FL_CDDataWriter class
in part :
lngNWA = cd.LShift(udtTrack.Track_Next_Writable(0), 24) Or _
cd.LShift(udtTrack.Track_Next_Writable(1), 16) Or _
cd.LShift(udtTrack.Track_Next_Writable(2), 8) Or _
udtTrack.Track_Next_Writable(3)
so i wuld apriciate some hints ideas or so... comon people lets make it Better ! :) and put it together better ....
