do u need special software or drivers to burn CDRW's?

[jedi]

hey guys i got a hp 9300 cd writer, and for some reason it wont let me burn onto cdrW's. i tried nero, vcdeasy, and cdrwin, but no luck. i downloaded aspi drivers from the vcdhelp tools section, but again no luck. do any of u have an idea of why this is happening? thanks

[KingJohn]

You don't say what software your using Nero ? Have you formatted (erase reWritable) the disk first ?

[jedi]

yes king jon, i have tried nero, cdrwin, and vcd easy. in nero i go to erase media, then quick erase. sometimes i get an SCSI ERROR. but i dont know what that is.

[offline]

Hi,

can you post the error. You will need to install the forceASPI
drivers (not the adaptec ones) and get the latest SCSI device drivers
from HP. People say "Burn and Go Gold" is the best burning
software to use with this drive.

ps: whatever you do - do not attempt to upgrade the flash firmware.

[Teshia]

I too own one of these HP IDE 9100 series burner drives. They work great, but the ASPI drivers didn't, so I went for the Force ASPI drivers. Worked amazing and didn't screw up the existing HP software for writing regular discs (RecordNow) and re-writable discs (DLA), at least that was the case for me in XP, which those drives were not native for.

[KingJohn]

That's funny, force ASPI uses Adaptec drivers, V4.60 to be precise.

ForceASPI is a popular utility that will install version 4.60 (1021) of Adaptec's ASPI drivers, *without* an Adaptec card or software in your system [hence: force]. Force ASPI v1.7 is the latest version.

Force ASPI will also *back-up* your current ASPI configuration. So, if you encounter problems, you can easily restore your original ASPI drivers. The command *dumpASPI* creates a backup of your existing ASPI layer.

If you read the instructions that come with the Adaptec drivers, it tells you exactly how to use the /FORCE command, which is the same thing done with FORCE ASPI does ! AND although the latest release says its V4.70, on most systems V4.60 will be installed.

Adaptec readme.doc

/ FORCE
This option allows the utility to force an upgrade whether the current file installed on the operating system is older or a previous version.

[offline]

That's funny, force ASPI uses Adaptec drivers, V4.60 to be precise.

Funny.. How so?

1) the ForceASPI drivers are more reliable than those released at
adaptec's web site. Many ppl reported and still report problems
with the adaptec release.

2) Even if you have an adaptec SCSI card, the ForceASPI drivers
are still required by many to successfully run their SCSI devices.
Even before ForceASPI, we had Corel's SCSI to fix the huge
number of problems in installing SCSI devices with a non adaptec
card - a marketing ploy to prevent non adaptec solutions gaining
market share.

3) If you don't have a adaptec card you need them to FORCE them to
operate on your pc if you need a ASPI layer (use in DVD ripping etc)

4) The HP cdrw in question is a SCSI device requiring a SCSI ASPI
layer on what is most likely a non adaptec adapter card. The
ForceASPI drivers fix this. Using /FORCE with the adaptec release
will not and does not fix the problem.

<why am I hearing the tune to blackadder all of a sudden>

[jedi]

well msot of the time it says scsi error...cannot perform start track, or end track.

[jedi]

i got force aspi, but its still not working. any other advice?

[KingJohn]

For some reason people think that ForceASPI uses different drivers !! it does not, it uses Adaptec drivers V4.6, if there is no Adaptec device it will force an update, exactly the same way as the original Adaptec drivers work with the /force command.

Download and run the adaptec drivers would mostly install V4.60 NOT 4.70 unless you use the /force command.

If you are the owner of a 3rd party device that requires an ASPI layer to be installed in your operating system, Adaptec suggests that you contact your peripheral manufacturer for a product specific version of the ASPI layer.

You may need "product specific version of the ASPI" anyway, not a generic driver.


jedi, if your writting CDR with no problems, then its not an ASPI error anyway !.

When you got this drive it came with its own programs, have you at any time used those programs to write to a CDR-W ??

[jedi]

king john no i havent used any of the programs of the disc to write a cdrw. so its no a ASPI driver error? because i cant burn a cdrw and i cant even erase it. it says

SCSI error, cant perform start track, or SCSI error cant perform fixation.

[jedi]

BURN & go GOLD? are u able to burn mpg files with this program? or only music?

[offline]

@ jedi did you get the latest SCSI device drivers
from HP?

@ KJ ?? go find someone with a SCSI device on a non Adaptec SCSI
controller and get them to let you use the / FORCE command
with the Adaptec release drivers on their computer. They will
throw you out the window; why? because it often fails.

[KingJohn]

king john no i havent used any of the programs of the disc to write a cdrw. so its no a ASPI driver error? because i cant burn a cdrw and i cant even erase it. it says

SCSI error, cant perform start track, or SCSI error cant perform fixation.

When you got the CD Writer, it also came with some programs ? Nero ? Easy CD ? or even one of HP own programs?. One of those would probably install the correct drivers for your drive.

Install one of those programs, then try a CDR-W with one of those programs.

There are many many people in this forum that have used force ASPI and it has not worked at all.

[vitualis]

There are many many people in this forum that have used force ASPI and it has not worked at all.

But let us characterise it correctly. ForceASPI may not be the cure of all ills but the scenario where ForceASPI doesn't work and the Adaptec installer does is rare indeed. In fact, I can't ever remember anyone posting this scenario.

However, many many people have posted that ForceASPI worked where the Adaptec download did not.

Where ForceASPI doesn't work, it is almost given that the official Adaptec download won't work either.

Regards.

[offline]

But let us characterise it correctly.

thx vitualis for your objective input. some people can never
admit that they are wrong.. even I find it hard sometimes ...hehe

[KingJohn]

There are many many people in this forum that have used force ASPI and it has not worked at all.

But let us characterise it correctly. ForceASPI may not be the cure of all ills but the scenario where ForceASPI doesn't work and the Adaptec installer does is rare indeed. In fact, I can't ever remember anyone posting this scenario.

However, many many people have posted that ForceASPI worked where the Adaptec download did not.

Where ForceASPI doesn't work, it is almost given that the official Adaptec download won't work either.

Regards.

I find it hard to understand why someone would not recommend drivers, that are being universally used by millions worldwide. In fact Microsoft themselves have chosen to add them as part of their operating system.

With millions, no billions of people around the world using the Adaptec drivers, and supplied by most mayor CD Writer Manufacturers under license, there must be a very small amount of people who cannot get them to work.

Some of those people would probably solve the matter with using the /FORCE command. Some of those people would solve the matter by using what came with the writer.

And some of those people will resolve the problem with ForceASPI, however since ForceASPI is very low on the list of solving problems, I personally don't go around preaching it will cure the problem, without following the normal tried and tested rout first.

And I don't go around telling people Adaptec drivers are no good and you should use forceASPI, when they both contain the same product. The ONLY diffrence being the way they are installed.

You don't see posts telling you "I have used the Adaptec installation" simply because the person has already have them on their system working, when they installed the OS !!!

[vitualis]

Well, I've used both Win98 and WinXP and it seems patently clear to me that a clean installation of both yields an ASPI layer that is insufficient. The ASPI Check program makes that obvious.

Thus the point of installing the ASPI layer at all. If these drivers came preinstallated in a totally satisfactory way, neither the Adaptec installer or ForceASPI would be necessary would it?

The issue of using ForceASPI is when someone has a problem to begin with (e.g., burning with CDRDAO). If they don't have a problem with their ASPI layer, the question wouldn't ever have come up. Your hyperbole about "billions" of users is completely irrelevant. Neither ForceASPI or the Adaptec installation is a solution to people without ASPI layer problems.

However, when there is a problem, this is where solutions are relevant. In such a situation, it has been shown time and time again by many many people who have posted in this and other forums that where the Adaptec installer didn't work, ForceASPI did. The converse is not true.

It is hence completely logical and appropriate to recommend the solution with the highest probability of success with the least amount of hassle.

That is, use ForceASPI.

Regards.

[vitualis]

BTW, the most common burning proggy to come with CD-burners now for quite a while is Nero Burning Rom. Such packages will not install the Adaptec ASPI drivers and nor does Nero need them (it has its own drivers).

This is reflected by the comments in these forums. Often, people have been burning happily away with Nero and it all comes unstuck when they try burning with VCDEasy / CDRDAO.

Regards.

[offline]

nor does Nero need them (it has its own drivers).

And the aspi command set from adaptec is also limited, allowing
less functionality than 3rd party drivers, which is why clonecd mounts
its own overlay manager and blindwrite installs a complete replacement.

For most, the aspi problem has only been a issue lately, but those
dealing with high end equipment have dealt with this ever since the
demise of the rll controller.