| |
|
Welcome to KnowledgeSutra - Dear Guest | |
USB
#1 Guest_Nightmare90_*
Posted 21 June 2004 - 11:24 AM
I have no problems with getting any of my USB stuff to work in Knoppix 3.4 or Debian or Mandrake 10.0. But all version are only using the USB in the slow mode (v1.1). It would be nice to get it to high speed. In Win2000 I get a huge speed increase. I can copy a 4 meg file in less than 2 seconds in Win2000. On Linux it takes about 7 seconds or about 600KB/s.
Is there some driver that must be loaded to get the speed up?
Using an 80Gig external USB drive in slow mode can be painfull.
Card in question is a Belkin USB 2.0 PCI card.
#2 Guest_Nightmare90_*
Posted 21 June 2004 - 11:25 AM
i was told that this might be a bug in the distro...
I am using Overclockix hd installed which is a knoppix remastered.
this is how my fstab looked like before any changes. NOTE that i do not have a dvd and overclockix auto-named the devices as dvd and cdaudio1
/etc/fstab: filesystem table.
#
# filesystem mountpoint type options dump pass
/dev/hda1 / ext3 defaults,errors=remount-ro 0 1
/dev/hda2 none swap sw 0 0
proc /proc proc defaults 0 0
/dev/fd0 /floppy vfat defaults,user,noauto,showexec,umask=022 0 0
/dev/dvd /dvd iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/cdaudio /cdaudio iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/cdrom /cdrom iso9660 defaults,ro,user,noexec,noauto 0 0
# Added by KNOPPIX
/dev/hdb5 /mnt/hdb5 ntfs noauto,users,exec,ro,umask=000 0 0
# Added by KNOPPIX
/dev/sda1 /mnt/sda1 vfat noauto,users,exec,umask=000 0 0
and this is my mtab
/dev/hda1 / ext3 rw,errors=remount-ro 0 0
none /proc proc rw 0 0
devpts /dev/pts devpts rw,gid=5,mode=620 0 0
usbfs /proc/bus/usb usbfs rw 0 0
/dev/cdaudio /cdaudio iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/cdrom /cdrom iso9660 defaults,ro,user,noexec,noauto 0 0
i click on the cdrom icon and i get an error saying : error kdektop
unable to run the specified command. THe file or folder file:/mnt/cdrom does not exist
same thing for the cd wr
as root i try to create a folder names cdrom in the mnt directory and it does not let me .
From a console i do this: mount /mnt/cdrom and it does not let me . I can see the cdrom and cdaudio folder in the root partition though
I corrected the fstab because i did not mount them in /dev but instead i said /mnt/cdrom
/dev/cdaudio /mnt/cdaudio1 iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/cdrom /mnt/cdrom iso9660 defaults,ro,user,noexec,noauto 0 0
Then, the cdrom worked fine but i was still getting this error for the cdrw
Could not mount device.
The reported error was:
mount: special device /dev/cdaudio does not exist
in the /mnt dir there is a cdrom folder and a cdaudio folder
i just tried burning an ISO image using the cd rw and it worked fine. On the other hand though, when i create a new device cdrw on my desktop , i get the above error
ls -al /dev | grep cd
brw-rw---- 1 root cdrom 29, 0 Apr 14 2001 aztcd0
brw-rw---- 1 root cdrom 41, 0 Apr 14 2001 bpcd
lrwxrwxrwx 1 root root 3 May 17 22:45 cdrom -> sr0
brw-rw---- 1 root cdrom 24, 0 Apr 14 2001 cdu535
brw-rw---- 1 root cdrom 30, 0 Apr 14 2001 cm206cd0
brw-rw---- 1 root cdrom 16, 0 Apr 14 2001 gscd0
brw-rw---- 1 root cdrom 24, 0 Apr 14 2001 lmscd
brw-rw---- 1 root cdrom 23, 0 Apr 14 2001 mcd
lrwxrwxrwx 1 root root 5 May 17 22:40 mcdx -> mcdx0
brw-rw---- 1 root cdrom 20, 0 Apr 14 2001 mcdx0
brw-rw---- 1 root cdrom 20, 1 Apr 14 2001 mcdx1
brw-rw---- 1 root cdrom 20, 2 Apr 14 2001 mcdx2
brw-rw---- 1 root cdrom 20, 3 Apr 14 2001 mcdx3
brw-rw---- 1 root cdrom 20, 4 Apr 14 2001 mcdx4
brw-rw---- 1 root cdrom 17, 0 Apr 14 2001 optcd
brw-rw---- 1 root cdrom 46, 0 Jun 2 2001 pcd0
brw-rw---- 1 root cdrom 46, 1 Jun 2 2001 pcd1
brw-rw---- 1 root cdrom 46, 2 Jun 2 2001 pcd2
brw-rw---- 1 root cdrom 46, 3 Jun 2 2001 pcd3
crw-rw-rw- 1 root tty 2, 221 Apr 14 2001 ptycd
lrwxrwxrwx 1 root root 6 May 17 22:40 sbpcd -> sbpcd0
brw-rw---- 1 root cdrom 25, 0 Apr 14 2001 sbpcd0
brw-rw---- 1 root cdrom 25, 1 Apr 14 2001 sbpcd1
brw-rw---- 1 root cdrom 25, 2 Apr 14 2001 sbpcd2
brw-rw---- 1 root cdrom 25, 3 Apr 14 2001 sbpcd3
brw-rw-r-- 1 root cdrom 11, 0 May 30 2001 scd0
brw-rw---- 1 root cdrom 11, 1 May 30 2001 scd1
brw-rw---- 1 root cdrom 11, 10 May 30 2001 scd10
brw-rw---- 1 root cdrom 11, 11 May 30 2001 scd11
brw-rw---- 1 root cdrom 11, 12 May 30 2001 scd12
brw-rw---- 1 root cdrom 11, 13 May 30 2001 scd13
brw-rw---- 1 root cdrom 11, 14 May 30 2001 scd14
brw-rw---- 1 root cdrom 11, 15 May 30 2001 scd15
brw-rw---- 1 root cdrom 11, 16 May 30 2001 scd16
brw-rw---- 1 root cdrom 11, 2 May 30 2001 scd2
brw-rw---- 1 root cdrom 11, 3 May 30 2001 scd3
brw-rw---- 1 root cdrom 11, 4 May 30 2001 scd4
brw-rw---- 1 root cdrom 11, 5 May 30 2001 scd5
brw-rw---- 1 root cdrom 11, 6 May 30 2001 scd6
brw-rw---- 1 root cdrom 11, 7 May 30 2001 scd7
brw-rw---- 1 root cdrom 11, 8 May 30 2001 scd8
brw-rw---- 1 root cdrom 11, 9 May 30 2001 scd9
brw-rw---- 1 root cdrom 18, 0 Apr 14 2001 sjcd
brw-rw---- 1 root cdrom 15, 0 Apr 14 2001 sonycd
lrwxrwxrwx 1 root root 4 May 17 22:40 sr0 -> scd0
lrwxrwxrwx 1 root root 4 May 17 22:40 sr1 -> scd1
lrwxrwxrwx 1 root root 5 May 17 22:40 sr10 -> scd10
lrwxrwxrwx 1 root root 5 May 17 22:40 sr11 -> scd11
lrwxrwxrwx 1 root root 5 May 17 22:40 sr12 -> scd12
lrwxrwxrwx 1 root root 5 May 17 22:40 sr13 -> scd13
lrwxrwxrwx 1 root root 5 May 17 22:40 sr14 -> scd14
lrwxrwxrwx 1 root root 5 May 17 22:40 sr15 -> scd15
lrwxrwxrwx 1 root root 5 May 17 22:40 sr16 -> scd16
lrwxrwxrwx 1 root root 4 May 17 22:40 sr2 -> scd2
lrwxrwxrwx 1 root root 4 May 17 22:40 sr3 -> scd3
lrwxrwxrwx 1 root root 4 May 17 22:40 sr4 -> scd4
lrwxrwxrwx 1 root root 4 May 17 22:40 sr5 -> scd5
lrwxrwxrwx 1 root root 4 May 17 22:40 sr6 -> scd6
lrwxrwxrwx 1 root root 4 May 17 22:40 sr7 -> scd7
lrwxrwxrwx 1 root root 4 May 17 22:40 sr8 -> scd8
lrwxrwxrwx 1 root root 4 May 17 22:40 sr9 -> scd9
crw-rw-rw- 1 root tty 3, 221 Apr 14 2001 ttycd
as of today , this is my fstab
/etc/fstab: filesystem table.
#
# filesystem mountpoint type options dump pass
/dev/hda1 / ext3 defaults,errors=remount-ro 0 1
/dev/hda2 none swap sw 0 0
proc /proc proc defaults 0 0
/dev/fd0 /floppy vfat defaults,user,noauto,showexec,umask=022 0 0
/dev/dvd /dvd iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/cdaudio /mnt/cdaudio iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/cdrom /mnt/cdrom iso9660 defaults,ro,user,noexec,noauto 0 0
# Added by KNOPPIX
/dev/hdb5 /mnt/hdb5 ntfs noauto,users,exec,ro,umask=000 0 0
# Added by KNOPPIX
/dev/sda1 /mnt/sda1 vfat noauto,users,exec,umask=000 0 0
i do not have a dvd drive but the dvd in the fstab was entered by knoppix , not by me.
in the / root partition i see a folder named cdaudio and another one cdrom
in the /dev directory i see only a cdrom nothing for cdaudio
once again i did not give my cdrw the name cdaudio. It was named like that by default.
ls -al /dev/dvd
lrwxrwxrwx 1 root root 16 May 17 22:45 /dev/dvd -> /KNOPPIX/dev/dvd
i do not have a dvd drive. Myabe knoppix thinks the cdrw is a dvd ???
ls -al /dev/cdrom
lrwxrwxrwx 1 root root 3 May 17 22:45 /dev/cdrom -> sr0
i have 2 IDE devices. one cd rom and one cd rw
please help as this thing is driving me nuts
#4 Guest_Nightmare90_*
Posted 21 June 2004 - 12:34 PM
With hard drive Knoppix installation I've found no way to make the sound system work. Alsa is installed, according to KDE software configuration tables. The enable sound system box is checked on sound configuration panel, but no cigar. SuSE 9.0 runs the sound without any massaging.
What needs to be added or modified to start up Alsa at bootup on hard drive Knoppix installation?
#6 Guest_Nightmare90_*
Posted 21 June 2004 - 12:36 PM
Some of the programs I open takes about 3 minutes to open and some
open right away. For example, konqueror opens in a heartbeat while
kwrite or kview takes forever (3 minutes). Also, opening superkaramba
takes a second, but when trying to open the file dialog to select a theme
you wait a long time. Sometimes even the "Start" menu makes you
wait several minutes.
When starting these programs through konsole showed no errors.
Someone has an idea about this issue?
thank you./
#7 Guest_Nightmare90_*
Posted 21 June 2004 - 12:38 PM
I am trying to edit video under Knoppix (why not, it works perfectly for editing sound [Audacity is really great], photos, etc...). When I connect my Sony camcorder to my computer (a sony vaio) via firewire, I get the following when I run dmesg:
ieee1394: Node added: ID:BUS[0-00:1023] GUID[08004601021bc70c]
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
raw1394: /dev/raw1394 device initialized
scsi singledevice 0 0 1 0
scsi singledevice 0 0 2 0
scsi singledevice 0 0 3 0
scsi singledevice 0 0 4 0
scsi singledevice 0 0 5 0
scsi singledevice 0 0 6 0
scsi singledevice 0 0 7 0
scsi singledevice 1 0 1 0
scsi singledevice 1 0 2 0
scsi singledevice 1 0 3 0
scsi singledevice 1 0 4 0
scsi singledevice 1 0 5 0
scsi singledevice 1 0 6 0
scsi singledevice 1 0 7 0
Everything looks cool, but how do I mount it?
I tried to make a directory in mnt called ieee1394 and mount the raw device:
mount /dev/raw1394 ieee1394
mount: /dev/raw1394 no es un dispositivo de bloques
Which hopefully is understandable as being spanish for "not a recognised block device".
Any idea what I am doing wrong?
#8 Guest_Nightmare90_*
Posted 21 June 2004 - 01:03 PM
Is there a brand that you can disable bios so it boots faster?
What out there that is speedy any maybe configurable from device manager for speed setting or all do it automatically?
What ones work with all devices with no problems?
If you see this thread helps you give it a bump to keep it going
#9 Guest_Nightmare90_*
Posted 21 June 2004 - 01:04 PM
As there are zillions of different systems around the entire globe, there's no way to make a thread that applies to every situation, but there a few basic things you might want to check, before posting a thread.
In this sticky thread, I will include some information on checking:
- memory
- harddrive
- cpu (temperature, voltage)
- mainboard (temperature, voltage)
- power supply
Well, let's get started!
#10 Guest_Nightmare90_*
Posted 21 June 2004 - 01:12 PM
Bad or incompatible memory is one very serious cause of a lot of strange problems. Small errors, to all kinds of strange crashes, can be due to memory problems.
The best tool to check if there's a problem with the memory of your system, is MemtestX86.
This program tests your memory in a very smart way and will give you trustful results.
If you find any errors while checking the memory, it doesn't have to mean your memory is bad. You might want to check a few things, before concluding that the memory is bad.
Possible causes for memory problems:
- bad memory
- CPU problems (CPU voltages too low, overheating, damaged core)
- heat problems
- power problems (memory voltages too low)
- wrong settings (set your BIOS' memory settings to "SPD")
- compatibility problems (with mainboard, chipset or other installed memory modules)
If you can, it might be good to check your memory on an other system (prefferably with different hardware) as well, before concluding the memory itsself is bad.
#11 Guest_Nightmare90_*
Posted 21 June 2004 - 01:13 PM
Modern harddrives are pretty sensible, when it comes to heat, shocks, or running 24/7. Although they don't brake down that easily (except for some bad series, made by IBM and Maxtor), they can be the cause of some pretty annoying problems.
A good tool to check a harddrive is .IBM/Hitachi's Drive Fitness Test.
Another good tool for checking a harddrive on mechanical problems is your ear. If you hear any weird noise, coming from your harddrive, it might be dying.
#12 Guest_Nightmare90_*
Posted 21 June 2004 - 01:14 PM
Modern CPU's don't often get broken, but under certain conditions, they can turn your computer into an electric hell.
For all modern CPUs goes, that heat is a killer. Although the Intel CPUs are protected from overheating (most modern chipsets for AMD have this functionality as well), too much heat is never good.
There are lots of tools that can show your CPU's temperature. The two programs I like best, are SiSoft Sandra and Mainboard Monitor. MBM is really a nice tool for debugging, as it supports logging of all kinds of system readings.
If you own an Intel system (P3/P4), temperatures up to 80C should be no problem, but keeping them at about 50C is the way to go (less is always better!).
If you own an AMD system, temperatures up to 90C should be no problem, but keeping them at about 50~60C is once again the best.
If your CPU is causing troubles, this also can be due to a mainboard that isn't supplying enough power, a not-so-stable PSU (power supply unit) or a VCore (voltage on the CPU core) that is too low. If you think your VCore is the problem, you might want to crank it up a little. This can be done from the BIOS of most systems. Be careful with this though, as a higher VCore will increase the heat the CPU produces.
#13 Guest_Nightmare90_*
Posted 21 June 2004 - 01:15 PM
Mainboards are somewhat harder to check for problems. Some boards are equipped with a diagnostic system (e.g. a display or leds, displaying error messages in case of failures) that can tell you quite a lot, but most boards aren't.
Besides of switching mainboards (or other components), you might want to check out the different voltages on the mainboard. By using either MBM or Sandra (see the CPU paragraph), you can check on what voltages your different lines are running. If the readings are way out of order (11V instead of 12V, or 3.8V instead of 3.3V) there's probably something wrong with either your mainboard or your PSU.
Nowadays, many boards die from leaking capacitors. If there's any brown mess on/beneath the capacitors on your mainboard (usually situated round the CPU socket), you don't have to search anymore for any other possible causes. This is a very common problem. Some manufacturers replace boards with leaking capacitors under warranty, even if the board's too old for receiving warranty!
#14 Guest_Nightmare90_*
Posted 21 June 2004 - 01:16 PM
As I already explained in the mainboard section, many problems can be due to a failing, or too weak power supply. I already told you how to check if the readings of the different powerlines are somewhat correct.
If your PSU runs extremely hot, there's a big chance it can't take the load. This is often the cause with cheap supplies, as they aren't intended for heavy use. Depending on the components of your system, you could need quite a heavy PSU.
For most modern CPU's, a PSU of at least 350W is recommended. If you can get one with a higer capacity, don't hestitate, but buy!
It's pretty likely that some newer systems that are about to be released, will have a CPU consuming over 100W (Intel Prescott). Those systems will need quite a heavy PSU to remain stable.
A small note: rather choose a quality PSU over a cheap one. I know you can get 500W PSUs that cost less than a brand 300W PSU. Please don't buy them.... they suck! Most of them can't do the capacity they are sold for, make lots of noise and will generate even some more heat. No good!
#15 Guest_Nightmare90_*
Posted 21 June 2004 - 01:17 PM
So you want to check your system's stability? Well, there's quite a nice tool to do so: Prime 95. Just run the torture test for some time and see what happens! If you manage to run it for a long time (e.g. 48 hours) without a single crash, your system is stable!
#16 Guest_Nightmare90_*
Posted 21 June 2004 - 01:17 PM
If you overclocked your system, the rules change. If you don't exactly know what you're doing, just undo the overclock and start checking....
-------
Well that's it folks. I hope I helped you out a little. If there are any questions left, feel free to open a thread, sent a PM (especially for info or comments on this thread) or give me a call .
Good luck and happy hunting!
#17 Guest_Nightmare90_*
Posted 21 June 2004 - 01:58 PM
Most of my existing hard disk drives are already occupied for other purposes, mostly full of data so I need to have at least 8 more. I'll probably buy Samsung's 160GB drives again. Or for even more space, I'll choose Western Digital or Seagate 200GB.
#19 Guest_Nightmare90_*
Posted 21 June 2004 - 02:02 PM
I was just wondering when I burn 50% of the time to a DVD-R, the writer fails to burn. The other 50% of the time, it succeeds. I'm only having a problem with DVD-R. For DVD+RW & DVD+R, it burns fine. (0% burn failure so far). Could it be the disc or the burner that's broken? It could be broken when writing to DVD-R. Here's the error log from Nero.
Please advice
Thanks,
Nero version: 6.3.0.3
Recorder: <LITE-ON DVDRW LDW-851S> Version: GS0F - HA 5 TA 0 - 6.3.0.3
Adapter driver: <> HA 5
Drive buffer : 2048kB
Bus Type : default (0) -> ATAPI, detected: ?
CD-ROM: <HL-DT-ST RW/DVD GCC-4521B>Version: 1.00 - HA 3 TA 0 - 6.3.0.3
Adapter driver: <atapi> HA 3
=== Scsi-Device-Map ===
DiskPeripheral : ST3120026AS atapi Port 1 ID 0 DMA: On
DiskPeripheral : ST3120026AS atapi Port 2 ID 0 DMA: On
CdRomPeripheral : HL-DT-ST RW/DVD GCC-4521B atapi Port 3 ID 0 DMA: On
CdRomPeripheral : Generic DVD-ROM 1.0 d346prt Port 4 ID 0 DMA: Off
=== CDRom-Device-Map ===
HL-DT-ST RW/DVD GCC-4521 E: CDRom0
Generic DVD-ROM G: CDRom1
LITE-ON DVDRW LDW-851S F: CDRom3
=======================
AutoRun : 1
Excluded drive IDs:
CmdQueuing : 1
CmdNotification: 2
WriteBufferSize: 83886080 (0) Byte
ShowDrvBufStat : 0
EraseSpeed : 0
BUFE : 0
Physical memory : 2047MB (2096364kB)
Free physical memory: 1418MB (1452552kB)
Memory in use : 30 %
Uncached PFiles: 0x0
Use Static Write Speed Table: 0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Disabled (0)
19.6.2004
Burn DVD Image
10:31:29 AM #1 Text 0 File Reader.cpp, Line 118
Reader running
10:31:29 AM #2 Text 0 File Writer.cpp, Line 124
Writer LITE-ON DVDRW LDW-851S running
10:31:29 AM #3 Text 0 File Burncd.cpp, Line 3101
Turn on Disc-at-once, using DVD media
10:31:29 AM #4 Text 0 File DlgWaitCD.cpp, Line 240
Last possible write address on media: 2297887 (510:38.37, 4488MB)
Last address to be written: 2285999 (507:59.74, 4464MB)
10:31:29 AM #5 Text 0 File DlgWaitCD.cpp, Line 245
Write in overburning mode: FALSE
10:31:29 AM #6 Text 0 File DlgWaitCD.cpp, Line 2085
Recorder: LITE-ON DVDRW LDW-851S, Media type: DVD-R
Disc Manufacturer: VDSPMS - AB 01
Disc Application Code: 64, Disc Physical Code: 193
10:31:29 AM #7 Text 0 File DlgWaitCD.cpp, Line 406
>>> Protocol of DlgWaitCD activities: <<<
=========================================
10:31:29 AM #8 Text 0 File ThreadedTransferInterface.cpp, Line 779
Setup items (after recorder preparation)
0: TRM_DATA_MODE1 (2 - CD-ROM Mode 1, ISO 9660)
2 indices, index0 (150) not provided
original disc pos #0 + 2286000 (2286000) = #2286000/508:0.0
not relocatable, disc pos for caching/writing not required/not required, no patch infos
-> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length 2286000 blocks [LITE-ON DVDRW LDW-851S ]
--------------------------------------------------------------
10:31:29 AM #9 Text 0 File ThreadedTransferInterface.cpp, Line 948
Prepare recorder [LITE-ON DVDRW LDW-851S ] for write in CUE-sheet-DAO
DAO infos:
==========
MCN: ""
TOCType: 0x00; Session Closed, disc fixated
Tracks 1 to 1:
1: TRM_DATA_MODE1, 2048/0x00, FilePos 0 0 4681728000, ISRC ""
DAO layout:
===========
__Start_|____Track_|_Idx_|_RecDep_|_CtrlAdr_
0 | lead-in | 0 | 0x00 | 0x41
0 | 1 | 0 | 0x00 | 0x41
0 | 1 | 1 | 0x00 | 0x41
2286000 | lead-out | 1 | 0x00 | 0x41
10:31:29 AM #10 Phase 24 File dlgbrnst.cpp, Line 1800
Caching of files started
10:31:29 AM #11 Text 0 File Burncd.cpp, Line 4073
Cache writing successful.
10:31:29 AM #12 Phase 25 File dlgbrnst.cpp, Line 1800
Caching of files completed
10:31:29 AM #13 Phase 36 File dlgbrnst.cpp, Line 1800
Burn process started at 4x (5,520 KB/s)
10:31:29 AM #14 Text 0 File ThreadedTransferInterface.cpp, Line 2264
Verifying disc position of item 0 (not relocatable, no disc pos, no patch infos, orig at #0): write at #0
10:31:30 AM #15 Text 0 File dlgbrnst.cpp, Line 1658
Set remaining time: 14:10,233 (850233ms) -> OK
10:31:30 AM #16 Text 0 File DVDR.cpp, Line 1512
Recording mode: Sequential Recording Mode
10:31:30 AM #17 Text 0 File Mmc.cpp, Line 19487
Set BUFE: supported -> ON , SMART-BURN : ON
10:31:30 AM #18 Text 0 File DVDR.cpp, Line 1643
Start write address at LBA 0
DVD high compatibility mode: Yes
10:31:30 AM #19 Text 0 File Cdrdrv.cpp, Line 7941
---- DVD Structure: Physical Format Information (00h) ----
Layer: 0, Address: 0 (0 h), AGID: 0; Length: 2050
Book Type: DVD-R (2), Part Version: 5
Disc Size: 120 mm, Maximum Rate: <not specified> (F h)
Number of Layers: 1, Track Path: Parallel Track Path (PTP), Layer Type: recordable
Linear Density: 0,267 um/bit, Track Density: 0,74 um/track
Starting Physical Sector Number of Data Area: 30000 h (DVD-ROM, DVD-R/-RW, DVD+R/+RW)
End Physical Sector Number of Data Area: 0 h
End Sector Number in Layer 0: 0 h
Data in Burst Cutting Area (BCA) does not exist
Media Specific:
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 - 00 00 00 00 00 00 00 00 ................
10:32:11 AM #20 Text 0 File Cdrdrv.cpp, Line 1277
10:32:11.468 - LITE-ON DVDRW LDW-851S\H5 T0 : Queue again later
10:32:14 AM #21 SCSI -500 File Cdrdrv.cpp, Line 1431
SCSI Exec, HA 5, TA 0, LUN 0, buffer 0x02F36000
Status: 0x02 (0x03, SCSI_ABORTED)
HA-Status 0x10 (0x0A, SCSI_HASTAT_REQUEST_SENSE_FAILED)
TA-Status 0x00 (0x00, OK)
Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)
Sense Code: 0x26
Sense Qual: 0x02
CDB Data: 0x5C 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x0C 0x00 0x00 0x00
Sense Data: 0xF0 0x00 0x05 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00 0x00 0x26 0x02
10:32:14 AM #22 Text 0 File Cdrdrv.cpp, Line 1277
10:32:14.828 - LITE-ON DVDRW LDW-851S\H5 T0 : Queue again later
10:32:19 AM #23 SCSI -500 File Cdrdrv.cpp, Line 1431
SCSI Exec, HA 5, TA 0, LUN 0, buffer 0x028B0000
Status: 0x02 (0x03, SCSI_ABORTED)
HA-Status 0x10 (0x0A, SCSI_HASTAT_REQUEST_SENSE_FAILED)
TA-Status 0x00 (0x00, OK)
Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)
Sense Code: 0x26
Sense Qual: 0x02
CDB Data: 0x2A 0x00 0x00 0x00 0x00 0x20 0x00 0x00 0x20 0x00 0x00 0x00
Sense Data: 0xF0 0x00 0x05 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00 0x00 0x26 0x02
10:32:19 AM #24 CDR -500 File Writer.cpp, Line 301
SCSI command aborted
LITE-ON DVDRW LDW-851S\H5 T0
10:32:19 AM #25 Text 0 File ThreadedTransfer.cpp, Line 229
all writers idle, stopping conversion
10:32:19 AM #26 Text 0 File ThreadedTransfer.cpp, Line 223
conversion idle, stopping reader
10:32:19 AM #27 Text 0 File DVDR.cpp, Line 1847
EndDAO: Last written address was 31
10:36:03 AM #28 Text 0 File dlgbrnst.cpp, Line 1658
Set remaining time: 0:00,000 (0ms) -> OK
10:36:03 AM #29 Text 0 File dlgbrnst.cpp, Line 1658
Set remaining time: 0:00,000 (0ms) -> OK
10:36:03 AM #30 Phase 38 File dlgbrnst.cpp, Line 1800
Burn process failed at 4x (5,520 KB/s)
Existing drivers:
File 'Drivers\PXHELP20.SYS': Ver=2.02.53a, size=17136 bytes, created 6/20/2003 8:36:36 AM (Prassi/Veritas driver for win 2K)
File 'Drivers\atapi.sys': Ver=?.?.?.?, size=86912 bytes, created 8/29/2002 1:27:50 AM (Adapter
#20 Guest_Nightmare90_*
Posted 21 June 2004 - 02:04 PM
Is the CD/DVD print function on this printer any good?
Any thoughts from users please...
Any other comments on this printer welcome too.
(Still unsure if to use compatible inks or get originals for it)
Cheers,
#22 Guest_Nightmare90_*
Posted 21 June 2004 - 02:07 PM
Does anyone have info?
#23 Guest_Nightmare90_*
Posted 21 June 2004 - 02:08 PM
really strangely. I have a Gigabyte GA-7N400 Pro motherboard
with an Athlon +2800. Anyways, when I go to shut down the
computer either by using the power off button or by gracefully
shutting it down via windows, it starts right back up; exactly like
a restart. I don't understand it. I've gone through my wiring
plenty of times. Otherwise the computer runs like a champ; but
this power shut down problem is really frustrating. The only thing
I can do is hold the power button for 4 sec.. But I don't like doing
it that way because windows doesn't go through the shut down
procedure gracefully. This did not happen with my old motherboard
installed. Someone help.
Thanks in advance
#24 Guest_Nightmare90_*
Posted 21 June 2004 - 02:09 PM
Machine is around 6, 7 years old and consist of P200MMX, 64MB ram, some S3 video based VGA (2D)adapter. (Of course, I threw it out to test the TNT2.)
I have tried TNT2 on my machine (AMD 2100Mhz, NF7-S, 512MB DDR ram, WinXP) and it worked without any problems.
Reply to this topic

1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users













