Jump to content

Blackened2687

Members
  • Content Count

    7
  • Joined

  • Last visited

About Blackened2687

  • Rank
    ISF Newbie

Profile Information

  • Location
    Russia, Krasnodarsky krai, Ust-Labinsk
  1. Blackened2687

    @ Dbminter, what is the model of you're Asus burner ?

    ASUS doesn't manufacture their own drives from long ago. All of them are rebadges of other drives. Here is the list of ASUS internal BD drives I remember: BD-ROM: BR-04B2T / FW 1.0x - LiteOn iHOS104 BD Combo: BC-1205PT / FW 1.0x - Pioneer BDC-202 BC-06B1ST / FW 1.0x - LiteOn iHES106 BC-08B1ST / FW 1.0x - LiteOn iHES108 BC-08B1LT / FW 1.0x - LiteOn iHES208 BC-12B1ST / FW 1.0x - LiteOn iHES112 BC-12B1ST a / FW 1.0x - LG CH12NS28 BC-12B1ST b / FW 1.0x - LG CH12NS30 BC-12B1ST b / FW 3.0x - LG CH12NS40 BC-12B1LT / FW 1.0x - LiteOn iHES212 BC-12D1ST / FW 1.0x - LG CH12NS28 BC-12D2HT / FW 1.0x - LG CH12NS30 BC-12D2HT / FW 3.0x - LG CH12NS40 BD Writer: BW-12B1ST / FW 1.0x - LiteOn iHBS112 BW-12B1ST a / FW 1.0x - LG BH16NS40 (SVC Code NS40) BW-12B1LT / FW 1.0x - LiteOn iHBS212 BW-14D1XT / FW 1.0x - LG BH16NS40 (SVC Code NS40) BW-16D1HT / FW 1.0x - LG BH16NS40 (SVC Code NS40) BW-16D1HT / FW 3.0x - LG BH16NS40 (SVC Code NS50/NS51) If I forgot something - please let me know
  2. Blackened2687

    LabelFlash, Mode Sense and Get Configuration related questions

    You were absolutely right! I haven't parsed this data correctly. I've re-checked the Mode Sense documentation and understood my mistake: I've completely ignored the Block Descriptor Length bytes in Mode Parameter Header, since I've never seen a non-zero value there (which is true for ATAPI/SATA devices). In MMC documentation it's said, that this value should be 8 for legacy SCSI Logical Units, so I've found SCSI-2 specification and read more about mode parameter block descriptors. Since I've never worked with real SCSI drives before, I've never actually seen any block descriptors, so this is quite a discovery for me. So, I just need to check these bytes, and if their value is non-zero, skip a block descriptor following the header. Now everything is recognized correctly. I think I should implement Mode Sense (6), as well, for compatibility purposes. Thank you VERY MUCH for the help! I've learn a lot today.
  3. Blackened2687

    LabelFlash, Mode Sense and Get Configuration related questions

    Many thanks for answers, LIGHTNING UK! So, if you still use Mode Sense command and it works fine even on that problematic controller, I think my issue is hidden somewhere in PLScsi, which I'm using to access the device. Well, at least I now know where to look for the cause of that bug. And the last question I've forgotten to add in the first post: Does ImgBurn use some "special methods" for getting the data from "real" SCSI drives like old Plextor or Yamaha CD-R drives? I've found that Mode Sense - C/DVD Capabilities and Mechanical Status works different for these drives, and I'm getting really strange values for buffer size and read/write capabilities for all media. But ImgBurn shows everything fine, even if the response of Mode Sense command is the same as in my program. Here is the photo, how it looks in ImgBurn and in DVRTool: ImgBurn: DVRTool: But the data returned by Mode Sense command is the same in ImgBurn and DVRTool - how is it possible? ImgBurn log with Debug enabled: I 20:42:24 Initialising Device (\\?\scsi#cdrom&ven_yamaha&prod_crw8424s&rev_1.0g#5&29e7a21d&0&000100#{53f56308-b6bf-11d0-94f2-00a0c91efb8b})... I 20:42:24 Device Address: [4:1:0] I 20:42:24 Drive Letter: (G:) I 20:42:24 Family Tree: I 20:42:24 -> Komputer z procesorem x86 obs³uguj±cy interfejs ACPI I 20:42:24 -> System zgodny ze standardem Microsoft ACPI I 20:42:24 -> Magistrala PCI I 20:42:24 -> Mostek (bridge) Intel(R) 82801 PCI - 244E (VEN_8086&DEV_244E - Intel - pci) I 20:42:24 -> Adaptec AHA-2910C/2915C/2920C/2930C PCI SCSI Controller (VEN_9004&DEV_5078 - Adaptec - aic78xx) I 20:42:24 -> Stacja dysków CD-ROM (YAMAHA CRW8424S SCSI CdRom Device) (Bus Number 0, Target ID 1, LUN 0) I 20:42:24 Device Maximum Transfer Length: 4*294*967*295 I 20:42:24 Device Maximum Physical Pages: 17 I 20:42:24 Device Alignment Mask: 0 I 20:42:24 Device Bus Type (Adapter/Device): SCSI / SCSI I 20:42:24 [4:1:0] YAMAHA CRW8424S 1.0g (G:) (SCSI) I 20:42:24 CDB: 12 00 00 00 60 00 I 20:42:24 CDB Interpretation: Inquiry I 20:42:24 BUFFER: 05 80 02 02 27 00 00 10 59 41 4D 41 48 41 20 20 43 52 57 38 34 32 34 53 20 20 20 20 20 20 20 20 31 2E 30 67 32 30 2F 30 31 2F 30 30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FF FF FF FF FF FF I 20:42:24 [4:1:0] YAMAHA CRW8424S 1.0g (G:) (SCSI) I 20:42:24 CDB: 5A 00 2A 00 00 00 00 00 FC 00 I 20:42:24 CDB Interpretation: Mode Sense (10) - Page Code (0x2A) - CD/DVD Capabilities and Mechanical Status I 20:42:24 BUFFER: 00 24 00 00 00 00 00 08 00 00 00 00 00 00 02 00 2A 14 07 07 71 6F 29 03 0B 06 01 00 10 00 0B 06 00 00 01 61 01 61 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 I 20:42:24 -> Drive 3 - Info: YAMAHA CRW8424S 1.0g (G:) (SCSI) And here is what DVRTool is getting for this drive: 00 24 00 00 00 00 00 08 00 00 00 00 00 00 02 00 2a 14 07 07 71 6f 29 03 0b 06 01 00 10 00 0b 06 00 00 01 61 01 61 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Received data is the same, as in ImgBurn! So, should it be processed differently in order to get necessary values? Thanks!
  4. I'm working on my own program for Pioneer drives, called DVRTool, and struggling with some minor, but annoying issues, related to Mode Sense command. This command seems to work incorrectly on some SATA controllers (namely Marvell 88SE9128 in AHCI mode), and I've read somewhere that it's considered obsolete and Get Configuration should be used instead. But I don't know how to retrieve all the information about drive capabilities with Get Configuration only, so I've decided to ask my questions here. 1. Which command does ImgBurn use to detect LabelFlash capability? In my program I use Mode Sense - Lableflash (5A 00 2D 00 00 00 00 00 FC 00), and if it returns any data, drive is considered LabelFlash-capable. Older version of ImgBurn also used this command (actually, I've stolen this command from there ), but in newer version some other command is used. What is this command? I want to get rid of Mode Sense method, too, but can't find any replacement. By the way, I've noticed long ago that ImgBurn detects iHASx24 B drives as LabelFlash-capable, which is not correct. Why does it happen? 2. Is it possible to get drive buffer size without Mode Sense - C/DVD Capabilities and Mechanical Status? I haven't found this information in any Get Configuration profile... But ImgBurn detects buffer size correctly even on drives connected to Marvell 88SE9128 controller in AHCI mode, when my DVRTool shows buffer size as 0 kiB. Opti Drive Control correctly recognizes drive buffer size on that controller, too. Which command should be used to get the buffer size, except Mode Sense? 3. Is it possible to reliably detect the capability of the drive to read DVD-RW discs? I have found no clear information about that, so I use indirect methods, checking Get Configuration - DVD-R/-RW Write profile presence, and checking MULTI110 bit of Get Configuration - DVD Read response data, but it doesn't work with DVD-ROM drives which can't read DVD-RAM discs (non DVD-Multi drives). Is it possible to reliably detect DVD-RW reading capability for such drives? Which method is currently used in ImgBurn? Thanks in advance!
  5. Blackened2687

    @ Dbminter, what is the model of you're Asus burner ?

    ASUS BW-16D1X-U drives with E101 or E102 firmware are actually Pioneer BDR-209MBK rebadges. ASUS BW-16D1H-U drives with A*** firmware series are LG drives (BH**NS40 or BH**NS50 depending of FW version) and those with E*** firmwares are Pioneer drives (BDR-209MBK of 1st or 2nd revision, depending of FW version). Also, ASUS BW-12D1S-U drives with E*** firmware series (and 1.20, too) are all Pioneer drives (E101/E102 - BDR-206BK, 1.20 - BDR-207BK, E301 - BDR-208BK, E401/E402 - BDR-209MBK of 1st revision). Hope it will help to pick a drive which will satisfy your needs.
  6. Blackened2687

    Question about SCSI CDBs used to detect BDXL capabilities

    Sorry for not replying for a long time - was very busy on my job... I've checked carefully and understood - documentation says, that these bits indicating BD-R ver.2 and BD-RE ver.3 capabilities, but actually BDXL drives use these bits to report BDXL support. Thank you very much for the help! I've implemented this feature in my Pioneer flasher (which I've just released on MyCE forums). Could you please tell two more things: 1. Is there a way to properly detect DVD-RW reading ability? Or should I use DVD-R read bit of "Mode Sense - C/DVD Capabilities" page, or is it better to use "Get Configuration - DVD Read" command? 2. Can I completely replace "Mode Sense - C/DVD Capabilities" command with a batch of "Get Configuration" or other commands to get all the information provided by "Mode Sense - C/DVD Capabilities" CDB? It is considered to be obsolete, but I can't figure out how to, for example, check drive's buffer size, or CD-RW / DVD-R reading capability on the old drives. Thank you very much!
  7. Hello! I'm developing some utilities for drive flashing and want to embed "drive supported media types" section into them. I've used "CD/DVD capabilities" and "get configuration" commands (5A and 46) to get info about CD / DVD / BD / HD DVD read/write support (I still don't understand how to detect DVD-RW read capability, though), but I can't find any info about BDXL formats support detection (BD-R Ver.3 and BD-RE Ver.4) - should I use any other command for detecting these features? I've read MMC documentation I could find, but I've found only the information about BDXL track reserving in these documents. I excuse if I've created this topic in a wrong place. ImgBurn properly detects BDXL reading capabilities on my ASUS BC-12D2HT and BDXL reading/writing capabilities on my Pioneer BDXL drives, but I can't figure out how. I hope my question doesn't violate any forum rules. Thanks in advance!
×

Important Information

By using this site, you agree to our Terms of Use.