Jump to content

Recommended Posts

Posted

Hi,

 

I'm new to IMGBurn but i'm a fan of Lightning UK's work *cough* DVD Decrypter *cough* so i thought i'd give this program a go. However everytime I try to burn an ISO i just get this message: "Failed to set write parameters!". Is there something i'm missing here? What parameters do I need to set. I checked the settings and all seems ok.

 

Any help would be much appreciated ^.^

Posted

As requested:

 

I 08:54:54 ImgBurn Version 2.1.0.0 started!

I 08:54:54 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)

I 08:54:54 Initialising SPTI...

I 08:54:54 Searching for SCSI / ATAPI devices...

I 08:54:54 Found 1 DVD?RW!

I 08:55:04 Operation Started!

I 08:55:04 Source File: D:\Documents and Settings\Gnome\My Documents\My Received Files\Anno 1701 AD.iso

I 08:55:04 Source File Sectors: 1,161,462 (MODE1/2048)

I 08:55:04 Source File Size: 2,378,674,176 bytes

I 08:55:04 Source File Volume Identifier: ANNO1701

I 08:55:04 Source File File System(s): ISO9660, Joliet

I 08:55:04 Destination Device: [4:0:0] ATAPI DVD RW 8XMax 160D (E:) (SCSI)

I 08:55:04 Destination Media Type: DVD-R (Disc ID: TTH02) (Speeds: 2x, 4x)

I 08:55:04 Destination Media Sectors: 2,297,888

I 08:55:04 Write Mode: DVD

I 08:55:04 Write Type: DAO

I 08:55:04 Write Speed: MAX

I 08:55:04 Link Size: Auto

I 08:55:04 Test Mode: No

I 08:55:04 BURN-Proof: Enabled

E 08:55:04 Failed to set Write Parameters!

E 08:55:05 Operation Failed! - Duration: 00:00:01

I 08:55:05 Average Write Rate: N/A - Maximum Write Rate: N/A

Posted (edited)
I 08:55:04 Source File File System(s): ISO9660, Joliet

I 08:55:04 Destination Device: [4:0:0]ATAPI DVD RW 8XMax 160D (E:) (SCSI)

There's two problems right there. If this disc is a DVD Video, then the file systems should be ISO9660, UDF(1.02).

 

And, is the drive really a scsi drive? Despite it saying its a ATAPI :blink: .

 

Your ISO was probably written incorrectly. Try using the Build mode in ImgBurn to build the ISO.

 

[edit] Or if you can't rebuild it, mount it as a virtual drive (Daemon Tools), then copy the files over from it to your harddrive. Then build the ISO.[/edit]

Edited by JasonFriday13
Posted

Ok, I was expecting you to have some mega old CDRW drive or something. It's weird that the set write parameters function would fail on a newer drive.

 

Please get me another log, but this time, before you click the 'Write' button, press the F8 key.

Then once it has errored out and given up, press F8 again.

 

SAVE the log (File -> Save As) and attach it as a file - it'll be much bigger this time due to some additional I/O debugging code.

 

The SCSI thing is also not always a good sign. It either means you're running the drive off a 3rd party IDE card / port on your motherboard or it means your drivers are messed up. There are only 2 makes of 3rd party cards (and chipsets) that work properly with optical drives. SiliconImage 680 and ITE8212

Posted (edited)

Here ya go. I'm using a MSI DVD+/-RW drive btw - don't remember the model (i can find out for u if u want) but i know its got the latest firmware. Its probably about 3-4 years old max.

 

Also, the drive is connected to my motherboard through the usual PATA interface only. No 3rd party PCI cards used (Gigabyte DS4).

ImgBurn.log

Edited by Gnome
Posted

Ahh another 965 chipset board.

 

As I'm sure you know, Intel removed all the PATA interfaces from the 965 chipset so you ARE in fact running from a 3rd party controller.

 

Probably a JMicron one or something. I believe the documents do say that it doesn't support optical drives.

 

I 10:43:21 [4:0:0]ATAPI DVD RW 8XMax 160D (E:) (SCSI)

I 10:43:21 CDB: 5A 00 05 00 00 00 00 00 FC 00

I 10:43:21 CDB Interpretation: Mode Sense (10)

I 10:43:21 BUFFER: 00 3A 00 00 00 00 00 00 05 32 01 C4 08 00 00 00 00 00 00 00 00 00 00 96 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 00 00 00 00 00 00 00 00 00 00 00 00 00 00

 

I 10:43:21 [4:0:0] ATAPI DVD RW 8XMax 160D (E:) (SCSI)

I 10:43:21 CDB: 5A 00 85 00 00 00 00 00 FC 00

I 10:43:21 CDB Interpretation: Mode Sense (10)

I 10:43:21 BUFFER: 00 3A 00 00 00 00 00 00 05 32 01 C4 08 00 00 00 00 00 00 00 00 00 00 96 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 00 00 00 00 00 00 00 00 00 00 00 00 00 00

 

I 10:43:21 [4:0:0] ATAPI DVD RW 8XMax 160D (E:) (SCSI)

I 10:43:21 CDB: 55 10 00 00 00 00 00 00 3C 00

I 10:43:21 CDB Interpretation: Mode Select (10)

I 10:43:21 BUFFER: 00 00 00 00 00 00 00 00 05 32 01 C4 08 00 00 00 00 00 00 00 00 00 00 96 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 00 00 00 00 00 00 00 00 00 00

E 10:43:21 SENSE: 70 00 05 00 00 00 00 0A 00 00 00 00 26 00 00 00 00 00 00 00 0F 00 00 84

E 10:43:21 SENSE Interpretation: Invalid Field in Parameter List

 

These 3 function calls at the beginning of the 'Set Write Parameters' code tell me something isn't quite right.

 

The first is getting the current 'write' values, the second is getting the 'default' values, the third is trying to set the unit to defaults, using the values from the second.

 

As you can see from the 'Invalid Field in Parameter List' error, the unit isn't accepting them.

 

That should not be possible and it would seem to me that they're not even reaching the drive.

 

As taken from the MMC 5 specification document:

 

7.2.3.2.2 Page Code in the MODE SELECT Parameter List

The Host may specify a Page Code from any of the pages in Table 653. If the Drive does not support the page

specified by the Page Code, then the command shall be terminated with CHECK CONDITION status and

SK/ASC/ASCQ shall be set to ILLEGAL REQUEST/INVALID FIELD IN PARAMETER LIST.

 

So basically, I think the drivers for the controller chip are blocking these calls and just returning that error because IT think the drive doesn't support them - as would be correct for a HDD I guess!

 

This is of course assuming you've used ImgBurn or DVD Dec to burn using this drive before - but on your previous machine (i.e. Pre Intel 965 chipset motherboard). As I mentioned earlier, I've only ever seen this command fail on old CDR/RW drives before - where they're so old they didn't really follow any MMC specs.

 

EDIT: Oh I also assume your motherboard BIOS is up to date, along with any BIOS for the JMicron chip if that's a separate download. Check you're running the latest drivers for it too.

Posted

So does this mean that i can't burn anything with my drive due to this new M/B? or just with IMGBurn?

 

I can't find any particular driver manufacturer, they all just show Microsoft. Although i vaguely recall Gigabyte boards using JMicron so I wouldn't be suprised.

Posted

The drivers would be on the gigabyte website - under product support for that actual motherboard.

 

To be honest, I don't know how far this issue goes. If the drive won't accept any of my attempts at setting the write parameters, either I'm doing something silly that only this drive doesn't like or no program will be able to set them.

 

Some programs might not care and just attempt to burn anyway - but it would be total fluke if that worked.

 

The only way to know for sure is to try some others! If they work and the I/O they send could be captured, I could make ImgBurn work too.

Posted

have you got your burner and a hard drive on that one ide 80 wire.

 

You would be better off setting burner to master and using sata hard drives.

 

These new motherboards with one ide are IMO stupid.

 

My MSI 975x pue has only one ide so i have my burner as master and a reader on there the rest of my hard drives are all sata, and i just stuck in a sata samsung /tosh/ shd163a (cough)

 

One ide is not good enough for me, though more and more sata roms/writers are appearing still, in non raid sata 1,2 is not much faster than ide.

 

Maybe your burner has had it or the board just does not like it, have you got an external caddy you could stick drive in and burn via usb2 to test drive etc.

 

Not sure if there is another ide on that board eg a third party one, jbmicron do see to get the job when a 3rd party ide is required, as mentioned make sure your mb bios is updated to a stable one, look out for any other bioses for 3rd party ide etc) i think in your mobo though its dedicated to southbridge ich8r.

Posted

We're lucky with our 975 chipsets, at least we get 1 real Intel IDE on the ich7r chip, the 965 (as this chap has), doesn't have any real ones, just the JMicron one!

 

For most people I guess thats not an issue but I've always had 4 IDE optical drives in my pc (and then using just scsi or sata hdds). Going down to 2 was bad enough, I could never live with 0!

 

I'm sure it wouldn't have killed Intel to keep 2 IDE channels Grrrrrr.

Posted

Dunno why all mobo manufacturers are going down this route, nforce5/6 Intel 965/975, i think Ati new chipset is the same.

 

It's like they think the ide is a bottleneck, well if it is and i seriously doubt it, i will put up with it, I want 4 ide and 10 sata1/2 (i would settle for 8 sata1/2)

 

 

I hope that gigabyte board is faster than their ****** servers ffs 6k a second for a 7 meg file.

 

make sure your using latest chipset drivers for mobo as well.

 

Storage ICH8R Southbrigde

- 1 FDD connector supported by I/O controller, allowing connection of

1 FDD device

- 6 SATA 3Gb/s connectors (SATAII0, SATAII1, SATAII2, SATAII3, SATAII4,

SATAII5), allowing connection of 6 SATA 3Gb/s devices

- Supports data striping (RAID 0), mirroring (RAID 1),

striping + mirroring (RAID 0+1), RAID 5, and RAID 10 for Serial ATA GIGABYTE SATA2 Controller

- 1 IDE connectors with UDMA 33/ATA 66/ATA 100/ATA 133 support,

allowing connection of 2 IDE devices

- 2 SATA 3Gb/s connectors (GSATAII0, GSATAII1), allowing connection

of 2 SATA 3Gb/s devices

- Supports data striping (RAID 0), mirroring (RAID 1) and JBOD for

Serial ATA

Posted (edited)

well, my bios is up-to-date. And the motherboard update website shows no newer drivers. In fact it only shows one, and it happens to be an older version than the one I have currently (Marvell Yukon Gigabit LAN Driver).

 

So far - no success. Not sure exactly which driver I should be looking at for this issue though. The website is http://tw.giga-byte.com/Support/Motherboar...ame=GA-965P-DS4 .

 

Also, my optical drive is already set to master from a long time ago. And my HD is a sata2 and is connected as such. I do have a IDE>sata interface converter though. I could use it on my optical drive if that makes any difference. Though i did hear that burning programs such as Nero don't work with sata optical drives.

 

EDIT: Gah, i just noticed that WMP11 can't burn either - it just shows a pic saying "connect a burner and restart the player". Somewhere along the line this pc has lost the ability to recognize my optical drive for what it actually is - a single layer dvd+/-RW burner. This is getting annoying now. :(

 

EDIT: See what I mean?

post-4978-1164069719_thumb.png

Edited by Gnome
Posted

Why do you think it's lost the ability to see your burner for what it is?

 

Because it says 'CdRom' in device manager? It always does that, all mine on my ITE card say the same thing.

Posted

Ok, maybe I was wrong about it not seeing my dvd burner but then why doesn't WMP11 recognise it?

 

Also, as requested:

post-4978-1164181338_thumb.png

Posted

WMP11 probably uses the IMAPI service for burning so you have to make sure that's enabled.

 

It might also decide it's not a burner because it won't accept the commands a burner should do - i.e. the 'Set Write Parameters' one!

  • 5 weeks later...
Posted

At last I have the solution. I dumped my old MSI drive (a pity really) and baught a SOny DRU-830A. Everything works fine now and I can finally burn DL discs - no more DVD compression for me! :D Oh wait, did i say that out loud? ^_~

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

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