#1 Burning Software

I'd like to use StarPort Wizard to share a DVD Burner in my workstation to enable several terminal systems to burn directly to disc. Is it possible to install just StarPort Wizard on the (x64) workstation or do I need to install all of StarBurn? Once I've set up the drive config, basically all I need is the Starwind Lite iSCSI server to run in the background so the terminals iSCSI initiators can see the drive. Can anyone tell me how to achieve this?

Hello,
For you configuration the simplest way is:
1)Install StarWind Lite iSCSI server on the workstation with DVD burner.
2)Install StaBurn for each temrinal system (if it's Windows OS). StarPort driver setup is embedded into StarBurn installation wizard and will be installed automaticaly.
3)Mount DVD burner on the termintal system using "Add remote device" wizard from StarBrun application (how to do http://www.starburnsoftware.com/help/index.html?mount_cd_dvd_and_blu-ray_hd-dv.htm).
4)Burn your discs remotely with StarBurn wizards.

P.S.
StarBurn Software provides direct tech support for all paid customers. If you do have purchased license please submit your future queries on support@starburnsoftware.com and do not forget to indicated your order number.

Thanks for the reply. Unfortunately I was looking for a way to use the StarWind/Starport Lite components without having to install the full StarBurn on both machines. I would buy StarBurn if this were possible.

You don't need to install full StarBurn on the server(optical drive) side. You only need to install StarWindLite there.

Again thanks for the response. Sounds promising. Unfortunately I'm not able to get it working, maybe because all my systems are Win7/8 x64? StarwindLite installs correctly on the server and is running as a service. On the terminal however StarBurn doesn't see the server/drive on any port/address I tried.

For testing purposes I attached a burner to the terminal system and with both Starwind Lite and Starburn running on the same system, Starburn/Port sees the burner on its own ip address/port but is unable to connect to it (failure message).
I must be missing something obvious, but can's seem to figure it out. Any help is appreciated

Use Microsoft built-in iSCSI initiator to connect. There are some issues with StarPort (MSFT had effectively banned it because of superior full monolithic SCSI port design). MSFT one should work however.