Problems with Promise cards?

Stojo303 · **Joined:** Sat Sep 15, 2007 3:54 pm **Posts:** 65

Hello,

I just got another possible problem report from a user. He says that neither my application nor StarBurn will find his device. He is using Windows Vista and thinks that the reason is because of his Promisecard;

"But I got an idea why this doesn't work. Because my motherboard had only 2 SATA slots but I have 2 HD and one DVD device I had to think something out and buyed an device (http://www.promise.com/product/product_ ... duct_id=87 ) called Ultra133 TX2 and it's used to spend one IDE slot to have two more SATA slots so to say. That is, with a high possibilty, the cause that it doesn't work.
I have the newest driver available installed (the driver is vista certified) and everything."

Is this a known issue or would you like me to gather more information (if so, please give me the details since it occurs with StarBurn also) about this specific issue?

Thanks,
Mikael

anton (staff) · **Posted:** Tue Dec 04, 2007 8:29 pm

No it is not. Please send us the log from the device enumeration sequence. I think it's pretty classic "no admin rights" issue rather then something hardware specific.

Stojo303 wrote:

Hello,

I just got another possible problem report from a user. He says that neither my application nor StarBurn will find his device. He is using Windows Vista and thinks that the reason is because of his Promisecard;

"But I got an idea why this doesn't work. Because my motherboard had only 2 SATA slots but I have 2 HD and one DVD device I had to think something out and buyed an device (http://www.promise.com/product/product_ ... duct_id=87 ) called Ultra133 TX2 and it's used to spend one IDE slot to have two more SATA slots so to say. That is, with a high possibilty, the cause that it doesn't work.
I have the newest driver available installed (the driver is vista certified) and everything."

Is this a known issue or would you like me to gather more information (if so, please give me the details since it occurs with StarBurn also) about this specific issue?

Thanks,
Mikael

Stojo303 · **Joined:** Sat Sep 15, 2007 3:54 pm **Posts:** 65

Quote:

No it is not. Please send us the log from the device enumeration sequence.

Can the user generate this log from StarBurn or do I need to implement it?
According to the user, my application hangs during the enumeration process (same in StarBurn, except that StarBurn comes with a cancel opportunity)

Regards,
Mikael

anton (staff) · **Posted:** Tue Dec 04, 2007 10:12 pm

Yes. Please see FAQ on how to generate it.

OK. So I really need where in the enumeration process it does happen

Stojo303 wrote:

Quote:

No it is not. Please send us the log from the device enumeration sequence.

Can the user generate this log from StarBurn or do I need to implement it?
According to the user, my application hangs during the enumeration process (same in StarBurn, except that StarBurn comes with a cancel opportunity)

Regards,
Mikael

Stojo303 · **Joined:** Sat Sep 15, 2007 3:54 pm **Posts:** 65

Thanks I'll take a look in the FAQ and get back to you later about this.

Regards,
Mikael

anton (staff) · **Posted:** Wed Dec 05, 2007 9:07 am

If you'll have any questions please do not hesitate to ask. Also it makes sense to issue your customer with the FindDeviceEx & FindDeviceExEx enumeration samples and capture logs from them. As they are way minimalistic and do only device look up

Just my $0.02... Thanks!

Stojo303 wrote:

Thanks I'll take a look in the FAQ and get back to you later about this.

Regards,
Mikael

Stojo303 · **Joined:** Sat Sep 15, 2007 3:54 pm **Posts:** 65

Quote:

Also it makes sense to issue your customer with the FindDeviceEx & FindDeviceExEx enumeration samples and capture logs from them.

I'm working with the Delphi version of the StarBurn SDK so I don't think (I might have missed them though) that these samples are included for Delphi?

Will it be good enough to send the user the pre-compiled samples?

Thanks,
Mikael

anton (staff) · **Posted:** Wed Dec 05, 2007 2:30 pm

It's OK to send pre-compiled binaries so I think language they were developed with does not matter

Stojo303 wrote:

Quote:

Also it makes sense to issue your customer with the FindDeviceEx & FindDeviceExEx enumeration samples and capture logs from them.

I'm working with the Delphi version of the StarBurn SDK so I don't think (I might have missed them though) that these samples are included for Delphi?

Will it be good enough to send the user the pre-compiled samples?

Thanks,
Mikael

Stojo303 · **Joined:** Sat Sep 15, 2007 3:54 pm **Posts:** 65

Hello Anton and co.

Here comes the logs from the user (He ran FindDevice.exe, FindDeviceEx.exe and FindDeviceExEx.exe):

Code:

----FindDevice.exe----
FindDevice:main(): ENTERed for 1 argument(s)

FindDevice:main(): WARNING! StarBurn_GetId() failed, exception 5, system error 1
26 ( 0x7e )

FindDevice:main(): Probing all CD/DVD/Blu-Ray/HD-DVD devices in the system...

FindDevice:main(): EXITing with failure
----FindDevice.exe end----

----FindDeviceEx.exe----
FindDeviceEx:main(): ENTERed for 1 argument(s)

FindDeviceEx:main(): Probing all CD/DVD/Blu-Ray/HD-DVD devices in the system...

FindDeviceEx:FindDeviceEx_QueryDevice(): Probing device name 'G:' for CD/DVD/Blu
-Ray/HD-DVD device... OK!
FindDeviceEx:FindDeviceEx_QueryDevice(): Found CD/DVD/Blu-Ray/HD-DVD device 'HL-
DT-ST' 'DVDRAM GSA-H10N ' 'JL10'
FindDeviceEx:FindDeviceEx_QueryDevice(): With 2097152 UCHAR(s) of cache
FindDeviceEx:FindDeviceEx_QueryDevice(): Reads: CD-R: Yes, CD-RW: Yes, DVD-ROM:
Yes, DVD-R: Yes, DVD-RAM: Yes
FindDeviceEx:FindDeviceEx_QueryDevice(): Writes: Test mode: Yes, CD-R: Yes, CD-R
W: Yes, DVD-R: Yes, DVD-RAM: Yes
FindDeviceEx:FindDeviceEx_QueryDevice(): Reads: DVD+RW: Yes, DVD+R: Yes, DVD+R D
L: Yes, Writes: DVD+RW: Yes, DVD+R: Yes, DVD+R DL: Yes
----FindDeviceEx.exe end----

----FindDeviceExEx.exe----
FindDeviceExEx:main(): ENTERed for 1 argument(s)

FindDeviceExEx:main(): Probing all CD/DVD/Blu-Ray/HD-DVD devices in the system..
.

FindDeviceExEx:FindDeviceEx_QueryDevice(): Probing device name 'CdRom0' for CD/D
VD/Blu-Ray/HD-DVD device... OK!
FindDeviceExEx:FindDeviceEx_QueryDevice(): Found CD/DVD/Blu-Ray/HD-DVD device 'H
L-DT-ST' 'DVDRAM GSA-H10N ' 'JL10'
FindDeviceExEx:FindDeviceEx_QueryDevice(): With 2097152 UCHAR(s) of cache
FindDeviceExEx:FindDeviceEx_QueryDevice(): Reads: CD-R: Yes, CD-RW: Yes, DVD-ROM
: Yes, DVD-R: Yes, DVD-RAM: Yes
FindDeviceExEx:FindDeviceEx_QueryDevice(): Writes: Test mode: Yes, CD-R: Yes, CD
-RW: Yes, DVD-R: Yes, DVD-RAM: Yes
FindDeviceExEx:FindDeviceEx_QueryDevice(): Reads: DVD+RW: Yes, DVD+R: Yes, DVD+R
 DL: Yes, Writes: DVD+RW: Yes, DVD+R: Yes, DVD+R DL: Yes

FindDeviceExEx:FindDeviceEx_QueryDevice(): Probing device name 'CdRom1' for CD/D
VD/Blu-Ray/HD-DVD device...

FindDeviceExEx:FindDeviceEx_QueryDevice(): StarBurn_CdvdBurnerGrabber_CreateExEx
() failed, exception 17, status 31, text 'CStarBurn_ScsiTransportSxxx::CStarBurn
_ScsiTransportSxxx(): Unable to locate device with device name 'CdRom1''

FindDeviceExEx:main(): WARNING! FindDevicEx_QueryDevice( 'CdRom1' ) failed with
exception number 17 ( 0x11 )
----FindDeviceExEx.exe end----

Hope this helps, feel free to ask for more details if needed.

Regards,
Mikael

anton (staff) · **Posted:** Wed Dec 05, 2007 8:45 pm

This is really a console output and not a debug logs but it really helped to find out what's wrong. Only FindDevice did not work b/c it failed to locate exported only in the WNASPI32.DLL. This happens when you use alien (non RDS) ASPI layer. So please either make sure WnASPI32.dll near your app executable belongs to the Rocket Division Software or use SPTI or SPTD device access methods. That's it

Stojo303 · **Joined:** Sat Sep 15, 2007 3:54 pm **Posts:** 65

Thanks for the update Anton!

I will do some more tests tomorrow (ensure that the user has the wnaspi32.dll). I thought that I forced SPTI, but that may be for the actual burning only and not for the find device methods.

Anyway, thanks for the great help!

Regards,
Mikael

anton (staff) · **Posted:** Wed Dec 05, 2007 10:36 pm

Please stick with one transport per time. And also let me know if you'd need unified STPI/SPTD device lookup code. Thanks!

Stojo303 wrote:

Thanks for the update Anton!

I will do some more tests tomorrow (ensure that the user has the wnaspi32.dll). I thought that I forced SPTI, but that may be for the actual burning only and not for the find device methods.

Anyway, thanks for the great help!

Regards,
Mikael

Stojo303 · **Joined:** Sat Sep 15, 2007 3:54 pm **Posts:** 65

Quote:

Please stick with one transport per time. And also let me know if you'd need unified STPI/SPTD device lookup code. Thanks!

I tried to force STPI with the following code: (Delphi code)

Code:

  FDeviceFinder := TsbDeviceFinder.Create;
  FDeviceFinder.TransportType := ttSpti;

I think this should force SPTI, or am I wrong?

Anyway, that caused the same problem from the user (after waiting 5 minutes no devices were found), so maybe WNASPI32.DLL is a must?

Regards,
Mikael

Stojo303 · **Joined:** Sat Sep 15, 2007 3:54 pm **Posts:** 65

Got another update (sorry for spamming):

If the user ensures that WNASPI32.DLL is available the issue will still remain. Maybe because of the forced SPTU transport type?

Regards,
Mikael

anton (staff) · **Posted:** Thu Dec 06, 2007 9:06 pm

FindDeviceEx sample worked fine. So I think the problem is not in the StarBurn core rather it's your problem (your app). So I need debug log from your application to find out what's broken

Stojo303 wrote:

Got another update (sorry for spamming):

If the user ensures that WNASPI32.DLL is available the issue will still remain. Maybe because of the forced SPTU transport type?

Regards,
Mikael

#1 Burning Software

Problems with Promise cards?

Who is online