Destination drive name is buggy

[Handsome Prints]

My new Samsung SH-S203B DVD drive is showing up as "ÿÿÿÿÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ" under Destination in ImgBurn (see attached screenshot). The drive burns perfectly in ImgBurn, but I was just wondering why the name of the drive was showing up like that and if there was a way to correct it. If anyone can shed some light on the matter, it would be most appreciated.

 

Thank you in advance!

 

HP

[LIGHTNING UK!]

Press F8, then Tools -> Search for....

 

Save the log and upload it (or copy + paste)

[Handsome Prints]

Press F8, then Tools -> Search for....

 

Save the log and upload it (or copy + paste)

 

Here's the log:

 

I 14:03:42 ImgBurn Version 2.3.2.0 started!

I 14:03:42 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)

I 14:03:42 Total Physical Memory: 3,143,772 KB - Available: 2,259,244 KB

W 14:03:42 Drive F:\ (FAT32) does not support single files > 4 GB in size.

W 14:03:42 Drive G:\ (FAT32) does not support single files > 4 GB in size.

I 14:03:42 Initialising SPTI...

I 14:03:42 Searching for SCSI / ATAPI devices...

I 14:03:42 Found 1 CD-RW, 1 DVD±RW and 1 DVD±RW/RAM!

W 14:03:47 I/O Interface 'Debug Mode' has been Enabled!

I 14:03:47 [0:1:0] ÿÿÿÿÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ ÿÿÿÿ (H:) (ATAPI)

I 14:03:47 CDB: 00 00 00 00 00 00

I 14:03:47 CDB Interpretation: Test Unit Ready

E 14:03:47 SENSE: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 01 00 00 00 00 00 00 00 00 00 00

E 14:03:47 SENSE Interpretation: Medium Not Present - Tray Closed

I 14:03:48 [0:1:0] ÿÿÿÿÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ ÿÿÿÿ (H:) (ATAPI)

I 14:03:48 CDB: 00 00 00 00 00 00

I 14:03:48 CDB Interpretation: Test Unit Ready

E 14:03:48 SENSE: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 01 00 00 00 00 00 00 00 00 00 00

E 14:03:48 SENSE Interpretation: Medium Not Present - Tray Closed

 

Any ideas Lightning? Thank you in advance. :-)

 

HP

[LIGHTNING UK!]

Yeah you didn't actually do what I needed you to.

 

Once you've pressed F8 to enable debug mode go into the Tools menu and select the 'Search for SCSI / ATAPI devices...' option.

 

Then copy + paste it all again.

[Handsome Prints]

Yeah you didn't actually do what I needed you to.

 

Once you've pressed F8 to enable debug mode go into the Tools menu and select the 'Search for SCSI / ATAPI devices...' option.

 

Then copy + paste it all again.

 

That's exactly what I did, but I guess I didn't let the log run long enough, it looked like it was repeating the last 5 lines in the log over and over, so I stopped it there, but I see now that there are some different lines if I let it run more. OK, I posted a lot more of the log file in the attached document. Thank you again Lightning. :-)

 

HP

ImgBurn_Log.txt

[LIGHTNING UK!]

The first log you posted you must have not done the Tools -> 'Search for...' thing. If you had you'd have had a much bigger log. Debug would of course need to be disabled AFTER the search and not before it! lol

 

Anyway...

 

Ok, you've got big issues somewhere.

 

I 14:51:01 [0:1:0] (H:) (ATAPI)

I 14:51:01 CDB: 12 00 00 00 38 00

I 14:51:01 CDB Interpretation: Inquiry

I 14:51:01 BUFFER: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

I 14:51:01 [0:1:0] ÿÿÿÿÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ ÿÿÿÿ (H:) (ATAPI)

 

The 'Inquiry' command is the one used to get the name of the drive etc.

 

For some reason your machine is returning a buffer full of 'FF'.

 

FF just happens to be that funny 'y' character.

 

What's your drive connected to? A real motherboard chipset SATA port or a 3rd party chipset one? (i.e. jmicron)

 

SATA drives work best when the controller is set to ATA mode rather than RAID or AHCI.

[Handsome Prints]

The first log you posted you must have not done the Tools -> 'Search for...' thing. If you had you'd have had a much bigger log. Debug would of course need to be disabled AFTER the search and not before it! lol

 

Anyway...

 

Ok, you've got big issues somewhere.

 

I 14:51:01 [0:1:0] (H:) (ATAPI)

I 14:51:01 CDB: 12 00 00 00 38 00

I 14:51:01 CDB Interpretation: Inquiry

I 14:51:01 BUFFER: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

I 14:51:01 [0:1:0] ÿÿÿÿÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ ÿÿÿÿ (H:) (ATAPI)

 

The 'Inquiry' command is the one used to get the name of the drive etc.

 

For some reason your machine is returning a buffer full of 'FF'.

 

FF just happens to be that funny 'y' character.

 

What's your drive connected to? A real motherboard chipset SATA port or a 3rd party chipset one? (i.e. jmicron)

 

SATA drives work best when the controller is set to ATA mode rather than RAID or AHCI.

 

Could you kindly let me know where I need to look to see if I have a real motherboard chipset SATA port or a 3rd party chipset one? Under "System Information", "Device Manager", or the do I need to enter the BIOS? For your reference, my computer is a Dell Dimension XPS Gen 4 purchased in May 2005, not sure if that says anything about the motherboard.

 

The controller is set to the default mode, not sure what the name is. I'll reboot and take a look and post back. All I can remember is that there are three options. I don't have a RAID drive, so I guess that would rule out RAID mode.

 

I could also try swapping the SATA cable between the new DVD drive and my hard drive to see if perhaps the new SATA cable I bought for the DVD drive is not working properly. The brand name is Dynex. Or I could just go out and buy another one, maybe that would be simpler. Are there brands that are more reliable than others?

[LIGHTNING UK!]

As it's just the one command that's not working correctly I doubt it's the cable. Still worth swapping it out though I guess.

 

To be honest, I've no idea what could possibly cause that at all. Any chance you could try the drive in another PC?

 

You'll need some sort of system info program to tell you what it's connected to - controller wise.

 

The 'ATAPI' bit isn't normal for XP and a controller running in (S)ATA mode though. It looks more like AHCI.

 

Assuming you have an Intel chipset on that board, try installing the latest Intel Matrix driver (and the chipset one whilst you're at it).

 

http://www.intel.com/support/chipsets/inf/

 

http://support.intel.com/support/chipsets/imsm/

[Handsome Prints]

As it's just the one command that's not working correctly I doubt it's the cable. Still worth swapping it out though I guess.

 

To be honest, I've no idea what could possibly cause that at all. Any chance you could try the drive in another PC?

 

You'll need some sort of system info program to tell you what it's connected to - controller wise.

 

The 'ATAPI' bit isn't normal for XP and a controller running in (S)ATA mode though. It looks more like AHCI.

 

Assuming you have an Intel chipset on that board, try installing the latest Intel Matrix driver (and the chipset one whilst you're at it).

 

http://www.intel.com/support/chipsets/inf/

 

http://support.intel.com/support/chipsets/imsm/

 

Thank you. Actually it seems as though it was the SATA cable. I went out and bought a new cable and after replacing the old SATA cable with the new one, the drive was labelled properly when I ran ImgBurn.

 

Before putting in the new cable though, I did run the Windows System Information utility, and I saw the following two items listed under "Hardware Resources -> I/O":

 

Intel® 82801FB/FBM SMBus Controller - 266A

Intel® 82801FR SATA AHCI Controller

 

You were right about AHCI. Not sure what that means though?

 

I also checked the BIOS, and these are four boot options (with a short descrtiption in parentheses):

 

1. RAID Autodetect/AHCI (RAID if signed, otherwise AHCI)

2. RAID Autodetect/ATA (RAID if signed, otherwise ATA)

3. RAID On (RAID on every boot)

4. Combination (SATA/PATA combination)

 

The default boot mode is option 1.

 

Anyway, everything is in order, so I am guessing that the controller and boot mode are OK. Looks like it won't be necessary to install the latest Intel Matrix driver and the chipset after all... :-)

 

I'm really impressed with ImgBurn, what a great program. All the configuration options so easy to locate, plus the handy log file, and the fact that it verifies the disc before burning. Thank you for all your help. Just out of curiosity, are you one of the developers?

Edited November 10, 2007 by Handsome Prints

[LIGHTNING UK!]

I am THE developer!

 

As the Highlander bloke says, "There can be only one"

[dontasciime]

What your a car

 

 

[kevdriver]

What your a car

 

 

 

[volvofl10]

Aha , so its your fault most of my photos are missing when they come back from Jessops