A hack, anyone, to turn on dma ?

Franc Zabkar wrote:
| On Wed, 25 Jun 2008 21:32:27 -0400, "PCR" put
| finger to keyboard and composed:
|
|http://www.google.com/search?hl=en&q...-S182F++dma&st
art=10&sa=N
|Google has about 132 for "TSSTcorp CD/DVDW SH-S182F dma". I haven't
|read them all. Here is one...
|
|http://www.dvdplusvideo.com/dvdguide005.html
|Enabling Direct Memory Access or "DMA" for faster DVD copying
|
|That article is speaking of WinXP. It says...
|
|"For repeated DMA errors. Windows XP will turn off DMA mode for a
|device after encountering certain errors during data transfer
|operations. If more that six DMA transfer timeouts occur, Windows
|will turn off DMA and use only PIO mode on that device.
|In this case, the user cannot turn on DMA for this device. The only
|option for the user who wants to enable DMA mode is to uninstall and
|reinstall the device."
|
| I found the following Win XP registry hack, but it doesn't appear to
| apply to Win9x.
|
| Getting back to DMA mode in Windows XP:
|
http://sniptools.com/tipstricks/gett...xp#comment1891

I can't seem to make it fit Win98 either. In Win98, Device Manager
doesn't seem capable of setting PIO or DMA for a controller-- but only
for a device. It does seem that Shadow has DMA set in his Secondary IDE
Controller to which the DVD is connected, anyhow...

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\Class\hdc\0002]
"DevLoader"="*IOS"
"DriverDesc"="Secondary IDE controller (dual fifo)"
"InfPath"="VIAVSD.INF"
"InfSection"="VIAIDE"
"PortDriver"="ESDI_506.pdr"
"ProviderName"="Microsoft"
"DriverDate"="2001\\10\\18"
"IDEDMADRIVE0"=hex:01
"IDEDMADRIVE1"=hex:01
"AutoInsertNotificationDrive0"=hex:01

BUT, going by "DMACurrentlyUsed=00", it ISN'T set in the DVD device.
Device Manager gives him the checkbox for it, but it won't stay set...

[HKEY_LOCAL_MACHINE\Enum\SCSI\TSSTCORPCD/DVDW_SH-S182FS\MF&CHILD0001&PCI
&VEN_1106&DEV_0571&SUBSYS_80ED1043&REV_06&BUS_00&D EV_0F&FUNC_0100]
"Capabilities"=hex:14,00,00,00
"AutoInsertNotification"=hex:00
"SCSITargetID"="0"
"SCSILUN"="0"
"RevisionLevel"="SB02"
"ProductId"="CD/DVDW SH-S182F"
"Manufacturer"="TSSTcorp"
"DeviceType"=hex:05
"Removable"=hex:01
"CurrentDriveLetterAssignment"="I"
"IDEMaster"=hex:01
"DMACurrentlyUsed"=hex:00
"HardwareID"="TSSTCORPCD/DVDW_SH-S182FS,GenCD,SCSI\\TSSTCORPCD/DVDW_SH-S
182FS"
"Class"="CDROM"
"ClassGUID"="{4d36e965-e325-11ce-bfc1-08002be10318}"
"Driver"="CDROM\\0000"
"Mfg"="(Dispositivo padrão de CD-ROM)"
"DeviceDesc"="TSSTcorp CD/DVDW SH-S182F"
"ConfigFlags"=hex:00,00,00,00
"Disconnect"=hex:01
"SyncDataXfer"=hex:00

I see you've made some suggestions. I'm still thinking.

| - Franc Zabkar
| --
| Please remove one 'i' from my address when replying by email.

--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR

Shadow wrote:
| On Wed, 25 Jun 2008 23:18:48 -0400, "PCR" wrote:
|
|Shadow wrote:
|| On Wed, 25 Jun 2008 21:32:27 -0400, "PCR"
|| wrote:
||
|I'm just not sure that constitutes a complete un/re-install--
|especially as you point it to C:\Windows\Inf for drivers. I'm
|speaking of JUST the DVD-- not all the other stuff. MSInfo, History,
|for it showed...
| Its plug and pray. You plug it in, windows installs it.
|
|TSSTcorp CD/DVDW SH-S182F
|Configuração original Tue Jun 24 22:06:37 2008 para Date
|
|I tend to doubt that actually is the date you first installed it. Do
|you have a CD with its drivers? Are there instructions anywhere on
|how to uninstall it? I might want to completely uninstall & then
|reinstall it-- maybe unless that involves actually unplugging it.
|That might be a little too much trouble.

| I've built computers for over 14 years (mine only). No
| trouble. But the DVDBurner has no drivers, it uses the windows native
| ones.

Alright. That's right. It's the same for my CD-R/W, actually-- "no
drivers are required or have been loaded for this device", Device
Manager says. Sorry. Well, what do you see at...

(1) "Device Manager, CDROM"
(2) D-Clk your DVD there for Properties, Driver tab.
Mine is not a DVD, but is... IDE-CD R/RW 4x4x24.
(3) "Update Driver" button, Next"
(4) "Bolt 'Display a list of all the drivers...', Next"
What shows in the Models box?
Mine says... (CD-ROM Drive) [4-23-1999]
(5) Bolt "Show all hardware"
What shows in the Manufacturers & Models boxes?
Mine shows... (Standard CDROM device) & (CDROM drive).

If yours is not the "standard", perhaps make it so & reboot. (Jot down
exactly what yours is first, so that you may switch back to it later if
desired.) Any difference?

|
|Why did you point it to C:\Windows\Inf for drivers? Where did you
|point it the very first time when you originally installed it?

| I have no other place to point to ..... there are no
| non-windows drivers.

OK, OK-- sorry, that's right. Let's see what it looks like at those
Update Driver requestors.

|
|| Here is my key. DMA is currently "off"
|| .................................................. .......
||
|[HKEY_LOCAL_MACHINE\Enum\SCSI\TSSTCORPCD/DVDW_SH-S182FS\MF&CHILD0001&P
CI
|&VEN_1106&DEV_0571&SUBSYS_80ED1043&REV_06&BUS_00 &DEV_0F&FUNC_0100]
|| "Capabilities"=hex:14,00,00,00
|| "AutoInsertNotification"=hex:00
|| "SCSITargetID"="0"
|| "SCSILUN"="0"
|| "RevisionLevel"="SB02"
|| "ProductId"="CD/DVDW SH-S182F"
|| "Manufacturer"="TSSTcorp"
|| "DeviceType"=hex:05
|| "Removable"=hex:01
|| "CurrentDriveLetterAssignment"="I"
|| "IDEMaster"=hex:01
|| "DMACurrentlyUsed"=hex:00
|
|That looks like the big difference between yours & mine. Did you try
|setting DMACurrentlyUsed to 01 & reboot? To do so...
| Yes, one of the first things I did.
| []'s

I should have known you would. Too bad it didn't work. I'm still
thinking. Try playing with that Update Driver requestor in the meantime.
Also, Zabcar seems to have lots more.


--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
Should things get worse after this,
PCR

On Thu, 26 Jun 2008 20:01:11 -0400, "PCR" wrote:

Shadow wrote:
| On Wed, 25 Jun 2008 23:18:48 -0400, "PCR" wrote:
Alright. That's right. It's the same for my CD-R/W, actually-- "no
drivers are required or have been loaded for this device", Device
Manager says. Sorry. Well, what do you see at...

(1) "Device Manager, CDROM"
(2) D-Clk your DVD there for Properties, Driver tab.
Mine is not a DVD, but is... IDE-CD R/RW 4x4x24.
(3) "Update Driver" button, Next"
(4) "Bolt 'Display a list of all the drivers...', Next"
What shows in the Models box?
Mine says... (CD-ROM Drive) [4-23-1999]
Gives the model of the dvd
(5) Bolt "Show all hardware"
What shows in the Manufacturers & Models boxes?
Mine shows... (Standard CDROM device) & (CDROM drive).
again

If yours is not the "standard", perhaps make it so & reboot. (Jot down
exactly what yours is first, so that you may switch back to it later if
desired.) Any difference?
it uses the mscdrom.inf from 5-5-1999

I just went crazy, dropped to DOS, renamed my windows folder
"badboy", reinstalled windows in "windows", and ---- the cdrom does
not accept dma, the box is there , but will not stay ticked. So it is
something quite native. The new windows did not even know the DVD
existed, it was a clean install.
So although samsung says the drive is compatible with windows
98, someone made a big booboo with the drivers. Either VIA or Samsung
when they designed the hardware.
I will have to boot linux for my backups. What I hate about
K3b is that it does not support checking the compilation, also it
knackers my long file names.
If you are interested, I can grope around in /proc and see if
linux is using any dma..... I'll do that :P

What I got from linux::
(Sorry about formatting)

name value min max mode
---- ----- --- --- ----
current_speed 66 0 70 rw
dsc_overlap 0 0 1 rw
init_speed 12 0 70 rw
io_32bit 1 0 3 rw
keepsettings 0 0 1 rw
nice1 1 0 1 rw
number 2 0 3 rw
pio_mode write-only 0 255 w
unmaskirq 1 0 1 rw
using_dma 1 0 1 rw

.........................................
[root@localhost ~]# hdparm -v /dev/hdc

/dev/hdc:
IO_support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
HDIO_GETGEO failed: Inappropriate ioctl for device

................................................
[root@localhost ~]# hdparm -i /dev/hdc

/dev/hdc:

Model=TSSTcorpCD/DVDW SH-S182F, FwRev=SB02, SerialNo=
Config={ Fixed Removeable DTR=5Mbs DTR10Mbs nonMagnetic }
RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=unknown, BuffSize=0kB, MaxMultSect=0
(maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
IORDY=on/off, tPIO={min:227,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 *udma2
AdvancedPM=no

* signifies the current active mode
...............................................

driver:
ide-cdrom version 4.61
.................................................. ...
dma:
2: floppy
4: cascade
(this is the same as windows. I cant figure out where the DVD dma
controler is , if the only one that appears is a floppy one...)
.................................................. ....
From dmesg:
The controler:
VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci0000:00:0f.1
ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hdaMA, hdbio
ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdcMA, hddio
................................
The drive:
hdc: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache, UDMA(33)
.....
I could probably dig for more.But this is not a linux group

I still can't understand why windows will not set dma. The
controler/drive has "dma" written all over it ....

Haven't scrolled back through this discussion [likely some of this was
preented]::
http://downloads.viaarena.com/driver...448release.doc
SOME versions had bugs, some lacked support, some were specific, etc,, test
installing various drivers would require ensuring the previous had been
*completely* removed {particularly in the INF folder}.

98 supports DMA but may disable it if your 98 system fails certain tests.
Specifically when the drivers:
1. query the motherboard chip set,
2. query the drive itself, and,
3. test a short pattern of disk reads and writes to see if they are reliable
at DMA speeds.
If any of the three or combination fail, DMA will be disabled upon reboot.
After errors, driver or software, the system may downgrade [permanently].
Particularly true for newer OSs [XP, VISTA].
ONE WAY that WILL kill DMA is to attempt to read a badly burnt or scratched
disk multiple times... another, errors during the copy/burn process

There MAY be a difficulty between the default CDROM drivers supplied
[default IDE INFs] and the actual drive when accessed.
There MAY be BIOS issues, using ACPI in some BIOSs may allow DMA to be used
if not already set.

* It may depend upon other drives attached to the channel, try:
DVD-RW as Device 0 (1st) as Master and the other CD-RW/hard drive as Device
1 (2nd) as Slave.

You might try the potential fixes he
http://www.mdgx.com/98-2.htm#W98DMA - it starts at the VERY top of the DMA
info, scroll down to see the help and potential fixes.
Make sure you look at:
http://download.microsoft.com/downlo...243450USA8.EXE -
contains an updated esdi_506
You can find more DMA fix info he
MDGx Windows 98/98 SE + DOS 7.10 Tricks, Secrets, BUGs + FIXes
http://www.mdgx.com/newtip98.htm - use find DMA on the page in the browser's
search/find.

Cleaning:
And as I have previously posted, it might be advisable to open the drive
case and look at the laser lens. When they get blocked
[dust/dirt/hair/paper, whatever], smogged, or *smoked*, the system will
downgrade speeds and abilities, as will burning software. Sometimes you can
carefully blow them out, sometimes you have to CAREFULLY clean with a
de-natured alcohol moistened q-tip...

--
MEB
http://peoplescounsel.orgfree.com
--
_________


"Franc Zabkar" wrote in message
...
| On Wed, 25 Jun 2008 21:30:50 -0300, Shadow sh@dow put finger to
| keyboard and composed:
|
| On Wed, 25 Jun 2008 17:47:23 -0400, "glee"
| wrote:
|
| "Shadow" sh@dow wrote in message
| . ..
|
| Yes. It shows DMA enabled for both Secondary IDE Channels. I am
starting to think
| the drive itself is going bad.
|
| Well, I just verified that. I had a 3.904 Gb backup to do, did
| it with Nero, in windows 98SE, and it took 93 minutes.
| I then fired up a livecd PClinux and burnt the same project in
| 10 minutes and 4 seconds. using K3b.
| Both times using LG 16x media and programs set to "max speed".
| Both programs reported they were burning at 16x
|
| So it has to be a driver problem.
|
| I find it hard to accept that turning off the DMA setting in Device
| Manager is the root cause of a 9x performance difference.
|
| Does your drive/controller/driver have problems reading as well?
|
| - Franc Zabkar
| --
| Please remove one 'i' from my address when replying by email.

Dang forgot this, IF there are only two drives, both on the same channel,
move the DVD/CDROM drive to the second channel as master...

--
MEB
http://peoplescounsel.orgfree.com
--
_________

"MEB" meb@not wrote in message
...
| Haven't scrolled back through this discussion [likely some of this was
| preented]::
|
http://downloads.viaarena.com/driver...448release.doc
| SOME versions had bugs, some lacked support, some were specific, etc,,
test
| installing various drivers would require ensuring the previous had been
| *completely* removed {particularly in the INF folder}.
|
| 98 supports DMA but may disable it if your 98 system fails certain tests.
| Specifically when the drivers:
| 1. query the motherboard chip set,
| 2. query the drive itself, and,
| 3. test a short pattern of disk reads and writes to see if they are
reliable
| at DMA speeds.
| If any of the three or combination fail, DMA will be disabled upon
reboot.
| After errors, driver or software, the system may downgrade [permanently].
| Particularly true for newer OSs [XP, VISTA].
| ONE WAY that WILL kill DMA is to attempt to read a badly burnt or
scratched
| disk multiple times... another, errors during the copy/burn process
|
| There MAY be a difficulty between the default CDROM drivers supplied
| [default IDE INFs] and the actual drive when accessed.
| There MAY be BIOS issues, using ACPI in some BIOSs may allow DMA to be
used
| if not already set.
|
| * It may depend upon other drives attached to the channel, try:
| DVD-RW as Device 0 (1st) as Master and the other CD-RW/hard drive as
Device
| 1 (2nd) as Slave.
|
| You might try the potential fixes he
| http://www.mdgx.com/98-2.htm#W98DMA - it starts at the VERY top of the DMA
| info, scroll down to see the help and potential fixes.
| Make sure you look at:
|
http://download.microsoft.com/downlo...243450USA8.EXE -
| contains an updated esdi_506
| You can find more DMA fix info he
| MDGx Windows 98/98 SE + DOS 7.10 Tricks, Secrets, BUGs + FIXes
| http://www.mdgx.com/newtip98.htm - use find DMA on the page in the
browser's
| search/find.
|
| Cleaning:
| And as I have previously posted, it might be advisable to open the drive
| case and look at the laser lens. When they get blocked
| [dust/dirt/hair/paper, whatever], smogged, or *smoked*, the system will
| downgrade speeds and abilities, as will burning software. Sometimes you
can
| carefully blow them out, sometimes you have to CAREFULLY clean with a
| de-natured alcohol moistened q-tip...
|
| --
| MEB
| http://peoplescounsel.orgfree.com
| --
| _________
|
|
| "Franc Zabkar" wrote in message
| ...
| | On Wed, 25 Jun 2008 21:30:50 -0300, Shadow sh@dow put finger to
| | keyboard and composed:
| |
| | On Wed, 25 Jun 2008 17:47:23 -0400, "glee"
| | wrote:
| |
| | "Shadow" sh@dow wrote in message
| | . ..
| |
| | Yes. It shows DMA enabled for both Secondary IDE Channels. I am
| starting to think
| | the drive itself is going bad.
| |
| | Well, I just verified that. I had a 3.904 Gb backup to do, did
| | it with Nero, in windows 98SE, and it took 93 minutes.
| | I then fired up a livecd PClinux and burnt the same project in
| | 10 minutes and 4 seconds. using K3b.
| | Both times using LG 16x media and programs set to "max speed".
| | Both programs reported they were burning at 16x
| |
| | So it has to be a driver problem.
| |
| | I find it hard to accept that turning off the DMA setting in Device
| | Manager is the root cause of a 9x performance difference.
| |
| | Does your drive/controller/driver have problems reading as well?
| |
| | - Franc Zabkar
| | --
| | Please remove one 'i' from my address when replying by email.
|
|
|

On Fri, 27 Jun 2008 21:38:11 -0300, Shadow sh@dow put finger to
keyboard and composed:

I just went crazy, dropped to DOS, renamed my windows folder
"badboy", reinstalled windows in "windows", and ---- the cdrom does
not accept dma, the box is there , but will not stay ticked. So it is
something quite native. The new windows did not even know the DVD
existed, it was a clean install.

So although samsung says the drive is compatible with windows
98, someone made a big booboo with the drivers. Either VIA or Samsung
when they designed the hardware.

According to your other posts, it appears that your PCI chipset
registers are being correctly configured for UDMA mode by VIA's
driver. At least that's how it looks to me.

For comparison purposes, I have been looking at the PCI registers for
my own SiS 5513 IDE controller. I have three IDE devices, one of which
(a Ricoh MP6200A CD-writer) doesn't support DMA mode (it fails the Set
Features test at Glen's MS URL), and the PCI registers accurately
reflect this, ie UDMA mode is disabled for the writer, but enabled for
the others. The DMA checkbox also will not stay ticked.

In short, my chipset registers are consistent with the DMA checkbox
whereas yours are not.

I will have to boot linux for my backups. What I hate about
K3b is that it does not support checking the compilation, also it
knackers my long file names.
If you are interested, I can grope around in /proc and see if
linux is using any dma..... I'll do that :P

It would be interesting to see what information your IDE devices
return in response to an ATAPI Identify Device command. Unfortunately
the only utilities I can find that give this kind of information are
suitable for ATA devices (ie hard drives) only. For example, Everest
Home Edition tells you which UDMA modes a drive can support and which
mode is currently active. I found something called BusTrace that
appears to be able to do the job, but it is not free:

http://www.bustrace.com/bustrace7/ap...tify/index.htm

Just out of curiosity, I checked to see whether your writer has the
latest firmware. According to the following URL, it does (SB02, 09
March 2007):

http://www.cdrinfo.com/Sections/Firm...x?DriveId=1413

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

On Fri, 27 Jun 2008 23:07:35 -0300, Shadow sh@dow put finger to
keyboard and composed:

dma:
2: floppy
4: cascade
(this is the same as windows. I cant figure out where the DVD dma
controler is , if the only one that appears is a floppy one...)

AIUI, the IDE controller does not do DMA via the motherboard's DMA
chips. It is a bus mastering controller which means it performs those
DMA functions itself. In contrast, the floppy controller can't do DMA
on its own, so it needs a DMA channel to access one of the
motherboard's 8237 DMA chips (or compatible equivalent).

If it helps, I'll scan the relevant section of IBM's PC AT Technical
Reference manual and post it on my web space.

................................................. ....
From dmesg:
The controler:
VP_IDE: VIA vt8237 (rev 00) IDE UDMA133 controller on pci0000:00:0f.1
ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hdaMA, hdbio
ide1: BM-DMA at 0xfc08-0xfc0f, BIOS settings: hdcMA, hddio
...............................
The drive:
hdc: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache, UDMA(33)
....
I could probably dig for more.But this is not a linux group

I still can't understand why windows will not set dma. The
controler/drive has "dma" written all over it ....

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

Thank you all for your suggestions. I now have DMA, on by
default, I did not even have to check the box.
How ? I jumpered the drive to slave .(It was master, on
secondary ide, is now slave)
Why ?
I have no idea. I tried rejumpering it to master and it
insists it's not capable of DMA. Jumpered to slave ... my DMA back.

Windows must have some horrible obscure place where it keeps a
log of bad CDRoms, I must have used a bad CDrom, and it registered the
first channel of ide 1 as "bad" with the samsung writer.

The only file that seems to be updated is mscdrom.pnf. Shall I
delete it and see what happens ?
:P

On Jun 28, 11:22*am, Shadow sh@dow wrote:
* * * * Thank you all for your suggestions. I now have DMA, on by
default, I did not even have to check the box.
* * * * How ? I jumpered the drive to slave .(It was master, on
secondary ide, is now slave)
* * * * Why ?
* * * * I have no idea. I tried rejumpering it to master and it
insists it's not capable of DMA. Jumpered to slave ... my DMA back.

* * * * Windows must have some horrible obscure place where it keeps a
log of bad CDRoms, I must have used a bad CDrom, and it registered the
first channel of ide 1 as "bad" with the samsung writer.

* * * * The only file that seems to be updated is mscdrom.pnf. Shall I
delete it and see what happens ?
* * * * :P

The PNF files are of no consequence in Win98, they are simply machine
versions of the similar named INF files and they have already been
used and thus useless space takers to be deleted in the first place.
Win98 will mount an inf file and produce the corresponding PNF file
anytime it needs to use an INF file. NT systems have the pnf
extension officially registered as a "Preconfigured INF file" or
somesuch thing.

Your CDROM drive obviously likes to be the slave device, some want to
be masters. The usual fix for getting DMA boxes to stay checked for
CDROM drives is to just fix the same DMA issue for the systems IDE
drives, BUT...

Windows 98 has a built in broken DMA system so as to be able to use
Bus Mastering software to get it all going correctly (I assume, there
being no other excuse). I refer you to Mshdc.inf, and it's
[ESDI_AddReg] section:
HKR,,DriverDesc,,"ESDI Port Driver"
HKR,,DevLoader,,*IOS
HKR,,PortDriver,,ESDI_506.pdr

And Diskdrv.inf and it's [DiskReg] section:
HKR,,,,%DiskClassName%
HKR,,EnumPropPages,,"iosclass.dll,EnumPropPages"
HKR,,SilentInstall,,1
HKR,,NoInstallClass,,1
HKR,,Icon,,"3"

If you will add:
HKR,,IDEDMADrive0,3,01
HKR,,IDEDMADrive1,3,01

to both sections, and then save the inf files back to your inf
folder. Then remove your IDE drives from the Device Mangler and then
reboot, Windows will re-find them and install them with the DMA boxes
already checked.
http://www.microsoft.com/whdc/archive/idedma.mspx

This is a "fix" for DMA issues over at msfn forums and it works -
Windows 98 was built with a broken DMA to begin with. If you fix your
inf files and put them in the Windows\Options\Cabs folder then the
next time install Windows over the top of itself it will be set up
with a working DMA system, it's automatic.