Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: 4 out of 5 Burned Sony Data DVD's contains CRC error ?!? (Compression/Redundancy Tool needed ?!?)

15 views
Skip to first unread message

Skybuck Flying

unread,
Oct 30, 2009, 12:09:10 AM10/30/09
to
Anyway... what I would need for good backup purposes on DVD's is something
better than WinRar.

I need some sort of compression tool, which does do compression... but which
also adds redundancy...

So that it can at least recover from single bit errors ?!? (Maybe even
multiple bit errors ?!?)

Just detecting bit errors like WinRar does is not really enough... since bit
errors seems to happen more often than not.

Does such a "compression/redundancy tool" already exist ?!?

Bye,
Skybuck.


Skybuck Flying

unread,
Oct 30, 2009, 12:21:31 AM10/30/09
to
Hmm interesting I came across this website which claims WinRar can add error
correcting codes to archives...

http://hubpages.com/hub/Interesting-aspects-about-Win-Rar-software

As far as I know the wizard doesn't show it... during compression
decisions...

So apperently this is a tool/feature that can be applied to archives after
they are created...

And indeed WinRar does have a "command" called: "protect archive from
damage".

I am going to try this feature out and see how it works out...

And then I am gonna try one last burn and see if it can actually recover
from bit errors ! ;) :)

Later I might "study" the bad burns to see what kind of bit errors
occured... or maybe not since my time is valuable too you know... me don't
have much time to fuck around like this ! ;)

Bye,
Skybuck.


Skybuck Flying

unread,
Oct 30, 2009, 12:28:45 AM10/30/09
to
This could be a nice feature... since the ammount of compressed data is only
2.7 GB and DVD has room for 4.7 GB...

Though I also believe more data on DVD is more potential for problems...
especially outer rings...

There are multiple rar's which need to be "protected from damage"... so some
rars might move more closer to outer rings which makes it a bit more risky
but ok... maybe the recovery data can recover from that... it's worth a
try...

I do which this tool was a bit more flexible... so that I could protect all
files... not just rar's...

I shall put the remaining files in a rar as well so that they can be
protected as well..

I also wish this tool had some kind of calculator for all files... to
calculate the percentage...

Or even better just specify the "free space" on dvd...

But ok... it doesn't have that and for now it's guess work...

So far my calculation seems to be around 71% of extra records could be
added... assuming Sony didn't lie and 4.7 GB actually means 4.7 GB ;)

For now I will go with 70% to be on the same side... The default seems to be
1%... so 70% seems to be much more !

Almost double ! ;)

So here goes... to be continued... I fear this is gonna be an allocation
problem... like oh shit... it didn't fit ?! :)

I guess most important files should go first... then other files might
receive a little bit less or so to make it fit after all ;) Unless it gets
to bad ;)

Bye,
Skybuck.


Skybuck Flying

unread,
Oct 30, 2009, 12:29:18 AM10/30/09
to
Hmm one last thing... I can't compress WinRar351.exe ofcourse... it needs to
remain the way it is... but the rest could do ! ;)

Bye,
Skybuck.


Skybuck Flying

unread,
Oct 30, 2009, 12:37:28 AM10/30/09
to
Hmm that's kinda stupid...

The redundancy information seems to be limited to only 10% ?!?

That does make it a no brainer to try it out... but I wonder if it's gonna
work at all...

But might as well spent another sony dvd on it... since I got plenty of
those things...

Kinda interesting to see if it's gonna work or not...

Bye,
Skybuck.


Skybuck Flying

unread,
Oct 30, 2009, 1:16:41 AM10/30/09
to
Ok,

Another bad toaster for the closet.

Conclusions:

1. DVD technology might be nice for audio, but is bad for data.
2. WinRar repair feature sux.

At least with these multiple bad toastest it's possible to still recover
some data...

Each DVD has certain files which work... which didn't work on others and
vice versa...

So with a bit of luck all might be recovered...

But for me this won't do... It's pretty crazy having to collect multiple
dvd's just to be able to restore
something successfull... just testing what's working and what's not working
costs a shit load of time !

So not gonna do that... for now I will have to rely on good faith and hoping
that some files are ok...

I think so since I already spent a shit load of time on testing it out with
WinRar's "test" feature which indicates crc32 failures on some files and
some not.

Kinda sux... I kinda regret buying 500 of these dvd's in the past... since
they so bad... or my drive bad... or the technology bad... who knows ;)

At least I can give them away for free... as audio dvd's when somebody has
audio dvd's... but I know of nobody that has audio dvd's lol ;) :)

Or it can keep trying and getting a good burn...

Maybe the verbatin disks will give better results but I doubt it...

I shall have to find another backup strategy in the future or maybe near
future...

Backing up everything to backup harddisks seems best to me...

Bye,
Skybuck.


Skybuck Flying

unread,
Oct 30, 2009, 1:30:54 AM10/30/09
to
So many bad burns warrants a further investigation...

On the label on the sony cake... it says:

www.dvdrwservices.com

Which takes me to this compatibility list via the faq:

http://www.dvdrw.com/why/compatoverview.htm

Surprise Surprise ! The BenQ drive is not on the list ?!

Quite remarkable ?!

I feel a conspiracy theory coming on... or another explanation or even a
third explanation so there are now three possibilities:

Possibilities:

1. BenQ drive is utter crap.
2. Anybody know on compatibility list gets intensively fucked by some secret
code or procedure or whatever.
3. Sold media is crap or only suitable for their drives... which is pretty
much the same as step 2.

This kinda sux.

One last thing I could try is go over to my mother's place which has a cheap
HP computer... which also has a DVD drive... I don't know which one yet...
but maybe it's on the compatibility list... and then see if it does any
better burning...

This would require sending my stuff over via the internet... fortunately I
have my own protected file transfer tool... with a bit of help of remote
desktopping it should be able to do that and pull it off ! ;)

Then I can try a burn there... !

If that fails then I am gonna say fuck it ! ;) :)

Last time I buy BenQ that's for sure... and last time I buy anything that's
not on some fucking compatibility list ?!

Be it cd, dvd, flash/ssd or whatever ?! ;)

Bye,
Skybuck.

Skybuck Flying

unread,
Oct 30, 2009, 1:32:41 AM10/30/09
to

"Skybuck Flying" <Blood...@hotmail.com> wrote in message
news:9a6e9$4aea7a0c$d53372a9$54...@cache3.tilbu1.nb.home.nl...

> So many bad burns warrants a further investigation...
>
> On the label on the sony cake... it says:
>
> www.dvdrwservices.com
>
> Which takes me to this compatibility list via the faq:
>
> http://www.dvdrw.com/why/compatoverview.htm
>
> Surprise Surprise ! The BenQ drive is not on the list ?!
>
> Quite remarkable ?!
>
> I feel a conspiracy theory coming on... or another explanation or even a
> third explanation so there are now three possibilities:
>
> Possibilities:
>
> 1. BenQ drive is utter crap.
> 2. Anybody know on compatibility list gets intensively fucked by some
> secret code or procedure or whatever.

Typo corrected, not that it matters much but ok:

2. Anybody not on compatibility list gets intensively fucked by some secret

Skybuck Flying

unread,
Oct 30, 2009, 1:34:35 AM10/30/09
to
Actually since I had one good burn... I could simply take that DVD over
there and read it and such...

Add some file hashing info via e-mail just in case to tell if it read good
and it should be fine...

Then I can test if it can motherfucking read it... and then I can try and
re-burn it... to get some more duplicates ! ;)

One for the "safe/fault" and one for me ! ;) :)

Bye,
Skybuck =D


Skybuck Flying

unread,
Oct 30, 2009, 1:38:58 AM10/30/09
to
Another company fucking skybuck up the ass:

I hate these motherfucking son of bitches !

This should be disallowed:

BenQ drives appear to be Philips drives !

I would have never bought it if I knew it had any Philips components in it
?!

Philips = Always bad for computers at least.

But maybe cd and dvd technology is bad in general...

But still... this should be outlawed !

Selling under different names ! BAH !

Bye,
Skybuck.


Skybuck Flying

unread,
Oct 30, 2009, 1:39:35 AM10/30/09
to
Oh forgot the link, here is a link:

http://www.videohelp.com/forum/archive/are-all-philips-benq-t309243.html


Bye,
Skybuck.


Skybuck Flying

unread,
Oct 30, 2009, 2:01:59 AM10/30/09
to
Maybe this failure log will be informative or helpfull for somebody out
there ?! ;)

Nero failure log 1:

"
Skybuck
.
1A20-8203-0139-2394-4252-0541*
1A41-70C1-M030-2482-5012-8431
1A42-0809-4030-2329-9503-7413
1A43-0609-4030-2312-3383-8659
1A44-0609-9130-2159-2652-6444
1A45-0609-9030-2448-3213-9734
1A46-70C1-M010-2526-3804-8791
1A47-0609-9030-2261-0221-1250
1A4A-0609-9130-2091-2397-1890
1A4C-80C1-M030-2400-5364-4495
1A4E-70C1-M030-2177-1260-3953
1A4K-90C1-M040-2753-1220-2853
1A4M-60C1-M080-2116-1504-4469
4A40-80C1-M050-2200-1340-5954
5A49-60C1-M020-2313-0112-7338

Windows XP 5.2
IA32
WinAspi: -
ahead WinASPI: File 'C:\Tools\Nero 6\nero\Wnaspi32.dll': Ver=2.0.1.74,
size=164112 bytes, created 10/26/2004 5:35:32 PM
Nero Version: 6.6.0.14
Internal Version: 6, 6, 0, 14d
(Nero Express)
Recorder: <BENQ DVD LS DW1655> Version: BCDB - HA 1 TA 0 -
6.6.0.14
Adapter driver: <atapi> HA 1
Drive buffer : 2048kB
Bus Type : default (0) -> ATAPI, detected: ATAPI
CD-ROM: <BENQ DVD LS DW1655 >Version: BCDB - HA 1 TA 0 -
6.6.0.14
Adapter driver: <atapi> HA 1

=== Scsi-Device-Map ===
CdRomPeripheral : BENQ DVD LS DW1655 atapi Port 1 ID 0
DMA: On
DiskPeripheral : HDS725050KLA360 nvata64 Port 2 ID 0
DMA: Off
DiskPeripheral : HDS725050KLA360 nvata64 Port 3 ID 0
DMA: Off
CdRomPeripheral : QZAZK KTINW5MV0 1.03 ato39a6y Port 4 ID 0
DMA: Off

=== CDRom-Device-Map ===
BENQ DVD LS DW1655 E: CDRom0
QZAZK KTINW5MV0 F: CDRom1
=======================

AutoRun : 1
Excluded drive IDs:
WriteBufferSize: 83886080 (0) Byte
ShowDrvBufStat : 0
BUFE : 0
Physical memory : 2047MB (2096564kB)
Free physical memory: 1240MB (1270416kB)
Memory in use : 39 %
Uncached PFiles: 0x0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Disabled (0)

30.10.2009
ISO compilation
2:20:53 AM #1 Text 0 File Isodoc.cpp, Line 6314
Iso document burn settings
------------------------------------------
Determine maximum speed : FALSE
Simulate : FALSE
Write : TRUE
Finalize CD : TRUE
Multisession : FALSE
Burning mode : DAO
Mode : 1
ISO Level : 1 (Max. of 11 = 8 + 3 char)
Character set : ISO 9660
Joliet : TRUE
Allow pathdepth more than 8 directories : TRUE
Allow more than 255 characters in path : TRUE
Write ISO9660 ;1 file extensions : TRUE

2:20:53 AM #2 Text 0 File Reader.cpp, Line 127
Reader running

2:20:53 AM #3 Text 0 File Writer.cpp, Line 122
Writer BENQ DVD LS DW1655 running

2:20:53 AM #4 ISO9660GEN -11 File geniso.cpp, Line 3297
First writeable address = 0 (0x00000000)

2:20:53 AM #5 Text 0 File Burncd.cpp, Line 3230
Turn on Disc-At-Once, using DVD media

2:20:53 AM #6 Text 0 File DlgWaitCD.cpp, Line 267
Last possible write address on media: 2295103 (510:01.28, 4482MB)
Last address to be written: 1453919 (323:05.44, 2839MB)

2:20:53 AM #7 Text 0 File DlgWaitCD.cpp, Line 279
Write in overburning mode: NO (enabled: CD)

2:20:53 AM #8 Text 0 File DlgWaitCD.cpp, Line 2433
Recorder: BENQ DVD LS DW1655, Media type: DVD+R

2:20:53 AM #9 Text 0 File DlgWaitCD.cpp, Line 445
>>> Protocol of DlgWaitCD activities: <<<
=========================================

2:20:53 AM #10 Text 0 File ThreadedTransferInterface.cpp, Line 830
Setup items (after recorder preparation)
0: TRM_DATA_MODE1 ()
2 indices, index0 (150) not provided
original disc pos #0 + 1453920 (1453920) = #1453920/323:5.45
relocatable, disc pos for caching/writing not required/ required, no
patch infos
-> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length
1453920 blocks [BENQ DVD LS DW1655]
--------------------------------------------------------------

2:20:53 AM #11 Text 0 File ThreadedTransferInterface.cpp, Line 1043
Prepare recorder [BENQ DVD LS DW1655] 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
2977628160, ISRC ""
DAO layout:
===========
__Start_|____Track_|_Idx_|_CtrlAdr_|_RecDep__________
0 | lead-in | 0 | 0x41 | 0x00
0 | 1 | 0 | 0x41 | 0x00
0 | 1 | 1 | 0x41 | 0x00
1453920 | lead-out | 1 | 0x41 | 0x00

2:20:53 AM #12 Phase 24 File dlgbrnst.cpp, Line 1832
Caching of files started

2:20:54 AM #13 Text 0 File Burncd.cpp, Line 4114
Cache writing successful.

2:20:54 AM #14 Phase 25 File dlgbrnst.cpp, Line 1832
Caching of files completed

2:20:54 AM #15 Phase 36 File dlgbrnst.cpp, Line 1832
Burn process started at 16x (22,160 KB/s)

2:20:54 AM #16 Text 0 File ThreadedTransferInterface.cpp, Line 2643
Verifying disc position of item 0 (relocatable, disc pos, no patch infos,
orig at #0): write at #0

2:20:54 AM #17 SCSI -1066 File Cdrdrv.cpp, Line 1182
SCSI Exec, HA 1, TA 0, LUN 0, buffer 0x05236200
Status: 0x04 (0x01, SCSI_ERR)
HA-Status 0x00 (0x00, OK)
TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND)
Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)
Sense Code: 0x24
Sense Qual: 0x00
CDB Data: 0xAD 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x08 0x04 0x00 0x00
Sense Data: 0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x12
0x00 0x00 0x00 0x00 0x24 0x00

2:20:54 AM #18 CDR -1207 File DVDR.cpp, Line 4946
Book Type automatically set to: Current recorder setting

2:20:54 AM #19 Text 0 File DVDPlusRW.cpp, Line 655
Start write address at LBA 0
DVD high compatibility mode: Yes

2:25:13 AM #20 Text 0 File WriterStatus.cpp, Line 116
<BENQ DVD LS DW1655 > start writing Lead-Out at LBA 1453920
(162F60h), lenght 0 blocks

2:25:13 AM #21 Text 0 File ThreadedTransfer.cpp, Line 228
all writers idle, stopping conversion

2:25:27 AM #22 Phase 37 File dlgbrnst.cpp, Line 1832
Burn process completed successfully at 16x (22,160 KB/s)

2:25:27 AM #23 Phase 78 File dlgbrnst.cpp, Line 1832
Data verification started

2:29:04 AM #24 Text 0 File ThreadedTransfer.cpp, Line 228
all writers idle, stopping conversion

2:29:04 AM #25 SectorVerify 11 File Cdrdrv.cpp, Line 9853
Sector 173976 on disc has different content to source

2:29:04 AM #26 Phase 81 File dlgbrnst.cpp, Line 1832
Data verification failed


Existing drivers:
File 'Drivers\InCDfs.SYS': Ver=4, 3, 12, 0, size=99200 bytes, created
1/27/2005 6:08:02 PM (InCD4 driver for win NT/2K/XP)
File 'Drivers\InCDpass.SYS': Ver=4, 3, 12, 0, size=28928 bytes, created
1/27/2005 6:07:34 PM (InCD4 driver for win NT/2K/XP)
File 'Drivers\InCDrec.SYS': Ver=4, 3, 12, 0, size=8704 bytes, created
1/27/2005 6:08:08 PM (InCD4 driver for win NT/2K/XP)

Registry Keys:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon
"

Bye,
Skybuck.


Skybuck Flying

unread,
Oct 30, 2009, 2:03:20 AM10/30/09
to
Failure log 2:

I hope those ain't activation keys... if so then fuck nero you stupid dumb
son of bitches ! HAHA ! ;)
(Maybe nero don't work so well with BenQ drives who knows ?! ;) Maybe I
should give BenQ burning software a try or so ? hmmm...)

Free physical memory: 1278MB (1308940kB)
Memory in use : 37 %


Uncached PFiles: 0x0
Use Inquiry : 1
Global Bus Type: default (0)
Check supported media : Disabled (0)

30.10.2009
ISO compilation
3:49:00 AM #1 Text 0 File Isodoc.cpp, Line 6314


Iso document burn settings
------------------------------------------
Determine maximum speed : FALSE
Simulate : FALSE
Write : TRUE
Finalize CD : TRUE
Multisession : FALSE
Burning mode : DAO
Mode : 1
ISO Level : 1 (Max. of 11 = 8 + 3 char)
Character set : ISO 9660
Joliet : TRUE
Allow pathdepth more than 8 directories : TRUE
Allow more than 255 characters in path : TRUE
Write ISO9660 ;1 file extensions : TRUE

3:49:00 AM #2 Text 0 File Reader.cpp, Line 127
Reader running

3:49:00 AM #3 Text 0 File Writer.cpp, Line 122


Writer BENQ DVD LS DW1655 running

3:49:00 AM #4 ISO9660GEN -11 File geniso.cpp, Line 3297


First writeable address = 0 (0x00000000)

3:49:00 AM #5 Text 0 File Burncd.cpp, Line 3230


Turn on Disc-At-Once, using DVD media

3:49:00 AM #6 Text 0 File DlgWaitCD.cpp, Line 267


Last possible write address on media: 2295103 (510:01.28, 4482MB)
Last address to be written: 1453919 (323:05.44, 2839MB)

3:49:00 AM #7 Text 0 File DlgWaitCD.cpp, Line 279


Write in overburning mode: NO (enabled: CD)

3:49:00 AM #8 Text 0 File DlgWaitCD.cpp, Line 2433


Recorder: BENQ DVD LS DW1655, Media type: DVD+R

3:49:00 AM #9 Text 0 File DlgWaitCD.cpp, Line 445


>>> Protocol of DlgWaitCD activities: <<<
=========================================

3:49:00 AM #10 Text 0 File ThreadedTransferInterface.cpp, Line 830


Setup items (after recorder preparation)
0: TRM_DATA_MODE1 ()
2 indices, index0 (150) not provided
original disc pos #0 + 1453920 (1453920) = #1453920/323:5.45
relocatable, disc pos for caching/writing not required/ required, no
patch infos
-> TRM_DATA_MODE1, 2048, config 0, wanted index0 0 blocks, length
1453920 blocks [BENQ DVD LS DW1655]
--------------------------------------------------------------

3:49:00 AM #11 Text 0 File ThreadedTransferInterface.cpp, Line 1043


Prepare recorder [BENQ DVD LS DW1655] 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
2977628160, ISRC ""
DAO layout:
===========
__Start_|____Track_|_Idx_|_CtrlAdr_|_RecDep__________
0 | lead-in | 0 | 0x41 | 0x00
0 | 1 | 0 | 0x41 | 0x00
0 | 1 | 1 | 0x41 | 0x00
1453920 | lead-out | 1 | 0x41 | 0x00

3:49:01 AM #12 Phase 24 File dlgbrnst.cpp, Line 1832
Caching of files started

3:49:01 AM #13 Text 0 File Burncd.cpp, Line 4114
Cache writing successful.

3:49:01 AM #14 Phase 25 File dlgbrnst.cpp, Line 1832
Caching of files completed

3:49:01 AM #15 Phase 36 File dlgbrnst.cpp, Line 1832


Burn process started at 16x (22,160 KB/s)

3:49:01 AM #16 Text 0 File ThreadedTransferInterface.cpp, Line 2643


Verifying disc position of item 0 (relocatable, disc pos, no patch infos,
orig at #0): write at #0

3:49:01 AM #17 SCSI -1066 File Cdrdrv.cpp, Line 1182


SCSI Exec, HA 1, TA 0, LUN 0, buffer 0x05236200
Status: 0x04 (0x01, SCSI_ERR)
HA-Status 0x00 (0x00, OK)
TA-Status 0x02 (0x01, SCSI_TASTATUS_CHKCOND)
Sense Key: 0x05 (KEY_ILLEGAL_REQUEST)
Sense Code: 0x24
Sense Qual: 0x00
CDB Data: 0xAD 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x08 0x04 0x00 0x00
Sense Data: 0x70 0x00 0x05 0x00 0x00 0x00 0x00 0x12
0x00 0x00 0x00 0x00 0x24 0x00

3:49:01 AM #18 CDR -1207 File DVDR.cpp, Line 4946


Book Type automatically set to: Current recorder setting

3:49:01 AM #19 Text 0 File DVDPlusRW.cpp, Line 655


Start write address at LBA 0
DVD high compatibility mode: Yes

3:53:14 AM #20 Text 0 File WriterStatus.cpp, Line 116


<BENQ DVD LS DW1655 > start writing Lead-Out at LBA 1453920
(162F60h), lenght 0 blocks

3:53:14 AM #21 Text 0 File ThreadedTransfer.cpp, Line 228


all writers idle, stopping conversion

3:53:29 AM #22 Phase 37 File dlgbrnst.cpp, Line 1832


Burn process completed successfully at 16x (22,160 KB/s)

3:53:29 AM #23 Phase 78 File dlgbrnst.cpp, Line 1832
Data verification started

3:57:05 AM #24 Text 0 File ThreadedTransfer.cpp, Line 228


all writers idle, stopping conversion

3:57:06 AM #25 SectorVerify 11 File Cdrdrv.cpp, Line 9853
Sector 369657 on disc has different content to source

3:57:06 AM #26 Phase 81 File dlgbrnst.cpp, Line 1832

Skybuck Flying

unread,
Oct 30, 2009, 2:11:54 AM10/30/09
to

"Skybuck Flying" <Blood...@hotmail.com> wrote in message
news:d096a$4aea81a5$d53372a9$89...@cache3.tilbu1.nb.home.nl...

> Failure log 2:
>
> I hope those ain't activation keys... if so then fuck nero you stupid dumb
> son of bitches ! HAHA ! ;)
> (Maybe nero don't work so well with BenQ drives who knows ?! ;) Maybe I
> should give BenQ burning software a try or so ? hmmm...)

Actually "Nero Software" came with the BenQ drive... So I am already using
it... :(

Only other software for "dvd drives" that came with my PC/Drive(?) is WinDVD
suite...

Not sure if it's usuably for making Data DVD's... Hmm...

I'll give it a try.

Bye,
Skybuck.


Skybuck Flying

unread,
Oct 30, 2009, 2:17:47 AM10/30/09
to
Also I wonder if Windows XP Pro x64 can simply burn stuff to DVD's... maybe
that will work...

I think windows media player might be able to do it... it seems to have some
burning capabilities or maybe that was a special program on somebody's
computer system ;) :)

For now I am gonna try WinDVD Creator 2... installed... bitched a bit about
64 bit... but seemed to install...

Needs a reboot... rebooting now...

Bye,
Skybuck.


Skybuck Flying

unread,
Oct 30, 2009, 2:31:53 AM10/30/09
to
Well that was pretty confusing... Apperently WinDVD Creator 2 is part of a
WinDVD suite...

which is again called Intervideo launcher/whatever...

It's a "suite of 4 programs"

PhotoAlumb 1.0
DvdCopy 2.5
WinDVD Creator 2
Disc Master 2.5

The auto launcher didn't pop because I have it disabled... it says WinDVD
suite so I thought WinDVDCreator2 must be it... I thought wrong...

This time after reboot I decided to install the launcher as well and the
other 3 programs as well.. it looks handy...

I think Disc Master 2.5 is actually the thing I needed.

Again it requires a reboot...

Something interesting happened though... I think it fucked with my logon and
logoff scripts...

Those settings are probably gone... which means my file disk images weren't
be mounted properly...

So apperently these setup programs use logon scripts ?!? Me not sure yet...
not much of problem... just extra work for me... but could be problem if I
die and somebody else uses my computer they won't know how to fix it ! ;)
Unless I switch back to using batchfiles for startup folder.. but then log
off won't work... when user switching... so windows has lot's and lot's of
issues ! ;) but then... windows can also do much much much... probably much
more then ubuntu or any other operating system out there ?! But I might
wrong... but I don't think so... point of the story... so many
possitibilities... so many combinations... sooner or later it's gonna
trigger all kinds of untested unknown or ill known problems ! ;)

Rrrrrebooting.. the dreaded reboot.

Bye,
Skybuck.


Skybuck Flying

unread,
Oct 30, 2009, 2:37:47 AM10/30/09
to
BY THE WAY this software came with my asus motherboard... it says it only
works with asus motherboards !

I feel like I own something special !!! Big fucking whoopie ! ;) :)

Ok time to give it a try ! ;) :)

This could rule out if it's a nero issue or not...

This gonna be interesting... I wonder what it's gui will be like...

Bye,
Skybuck.


Skybuck Flying

unread,
Oct 30, 2009, 2:39:21 AM10/30/09
to
Oh by the way.. the logon and logoff script is working again... maybe the
first time it just took a bit of time or something... or maybe it restored
it... I don't know...

Ok time to test "Intervideo WinDVD Suite, Disc Master 2.5 that only works on
Asus motherboards" !

That's a whole mouth of come for you ! ;) :)

Bye,
Skybuck LOL.


Skybuck Flying

unread,
Oct 30, 2009, 3:19:35 AM10/30/09
to
Ok,

Disc Master 2.5 just finished burning a DVD... and again a bit error in one
WinRar file... this was during less ideal circumstances...-> internet was
on...

Not bad... it seems Disc Master 2.5 might perform slightly better but it
could also be a fluke of luck.

End result is:

Still a corrupted file which is still bad. (Disc master did not do any
verifications so had to do it myself with WinRar.)

That's already 6 bad discs out of 7 ?!

I am really starting to wonder if it's maybe a WinRar bug... I don't think
so... some day I will write a special program which will do bit by bit
comparision... but for now I trust my hd... I trust winrar...

I shall do one last time... and simply do a copy... from hd to hd to see if
that gives any problems.

One last note: With winrar it is possible to keep "damaged/broken files"...
for applications/games this might be acceptable if the bit errors are in
images or whatever... but for me... for my information and especially for my
source code this is pretty much unacceptable... I want a perfect copy of my
source code and not having to worry about any possibly bugs because of bit
errors... In other words this is pissing me off a little bit... just a tiny
little bit... yes this is what I am like when I am litttttle bit pissy ;) :)
Little things not working pisses me off too. Little things can have big
consequences ! ;) ;) :) :P* ;) :)

OH MY GOD WHAT THE FUCK ?!>!>!>!>!>!?!?!?!?!?!?!?

My HD to HD transfer failed as well ?!? It says CRC32 corruption error ?!?
OH OH...

This could mean a couple of things:

1. Windows XP user account corruption causes file/file system corruption ?!?
2. PC RAM is bad ?!?
3. Harddisk is getting bad ?!? OHOH.
4. File system is corrupt again ?!?
5. Windows has big bugs ?!? Maybe windows update fucked it ?!?
6. Path through computer is fucked ?!?
7. Motherboard is fucked ?!?
8. WinRar is fucked ?!?
9. Explorer is fucked ?!?

OH OH OH OH OH OH OH OH OH OH OH OH OH OH BIG OHOHOHOHOHOOOOOO.

I HAVE NO TIME FOR THIS BULLSHIT THAT MAKES IT AN EXTRA BIG
OOOOOOOHHHHHHHOOOOOOOOOOOOO ;) :)

WTF I AM GETTING CONFUSED I SIMPLY CANT BELIEVE THIS SHIT
AHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH.

OHOHOHOHOHOHOHOHOHOHOHOHOH I JUST HAD A TERRIBLY THOUGHT:

Maybe "cleaning the dust filters of the antec 1200 case while the harddrives
were spinning IS A BAD THING TO DO ?!?!?!? Maybe it caused damage ?!?!? OH
SHIT."

I AM SO FUCKED RIGHT NOW I CANT BELIEVE IT.

I am gonna do one last copy hd-to-same-hd test... WTF ?!

Hmmm this time it did pass the WinRar test...

I did notice the unpacked file size is exactly 2^31... so it could be a
integer/bug winrar thingy...

Maybe it depends on testing order or so... gonna test other files to see
what happens gjez...

OH MY FUCKING GOD. WTFFFFFFFFF?! MY SECOND WORST NIGHTMARE !

IT SAYS FILE IS FUCKING CORRUPT ?! WTF ?! IT'S 5.5 GB EXTRACTED ?! OH MY
FUCKING GOD.

WTF IS GOING ON... I HOPE THIS IS A WINRAR BUG OTHERWISE I AM SERIOUSLY
FUCKED ! LOL.

NO PLS DONT TELL ME MY HD IS FUCKED ?!

THIS BETTER NOT BE A FUCKING WINDOWS BUG OTHERWISE I AM SWITCHING TO UBUNTU
OR SOMETHING FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFUUUUCCCCCCCCCKKKKKKK.

I DONT KNOW WHAT TO DO.

I NEED A PLAN TO SAVE MY COMPUTER FROM OTHER DESTRUCTION.

BUT I DONT KNOW WHAT THE PROBLEM IS OH MY GOD I AM FUCKED FOR NOW.

Maybe it just a windows copy bug... I have seen this mentioned before in
FUCKING VISTA.

FUCK.

Maybe I should try a Knoppix cd or something or linux cd and try to mount
ntfs and do a copy... but that kinda dangerous.

I AM SO FUCKED.

But for now maybe hoping on WinRar bug is good... but I don't think it's a
winrar bug but it could be...

First thing I need to do is write a bit by bit decent comparision program...
but I fear the worst !

SHIT. WTF ?! Could this be related to corrupted user account WTF ?!

Did Microsoft FUCK MY OPERATING SYSTEM TO FORCE SWITCH TO VISTA OR WINDOWS 7
?!

WHO KNOWS.

This will have to be confirmed by others.

So I go post a message now... later... I need to keep and stay cool ;) :)

Bye,
Skybucks...


CellShocked

unread,
Oct 30, 2009, 3:20:12 AM10/30/09
to


The tools that are in place are beyond the comprehension of Usenet group
abusing retards like you.

AFTER you find out what posting conventions and protocols are, and AFTER
you start following them, you MIGHT get better answers to your wildly
STUPID question from the perspective of nearly all the groups you have
decided to INVADE with your stupid horseshit.

Skybuck Flying

unread,
Oct 30, 2009, 3:43:45 AM10/30/09
to
HOLYSHIT.

I just wrote a brand new file comparision tool... to be 100% sure that the
code is good.

And the corruption IS REAL !

OH OH.

No idea yet what is causing it... but it's real !

Bye,
Skybuck.


Skybuck Flying

unread,
Oct 30, 2009, 4:10:19 AM10/30/09
to
I did one last check:

1. I reboot the PC to make sure it's not some corruption in the file system
cache.

2. Re-run the compare files tool, same position pops up: 316.802.701

Unless other people have the same offset/position as damaged then it's
probably just a problem with one of my hd-disks...

Big shit though... this means I will have to stop using my "Dream PC" which
can now be rightfully called "Nightmare PC" until I get new harddisks...
this also means the Antec 1200 case could be risky... especially when
cleaning dustfilters while hd's are on... this could also mean placing tower
on table is bad because of bumps against table or so... which might kill
hd's ?! BIG SHIT... can't place PC on ground because of dust.

Only solution is to make a remote computer... in a far away location from
me... so it wouldn't be affected by dust... or bangs... then I would need
super long monitor cable... to be able to work with the damn thing...

This could be a bit dangerous such a long monitor cable... alternatively...

I could place pc on a seperate table which could take care of most bangs
probably... it would still be a bit risky... and bang sensitive if I bang
against other table...

It could also be a matter of high usage... maybe Microsofts ! flight
simulator x had a little bit to do with it.. it has a huge load of files and
places extra stress on the file system which is bad. I recently deleted it
to get rid of it and its load on file system... to late now... this kinda
sucks...

I am also surprised the harddisk doesn't mark it as a bad sector... maybe
it's already way passed being able to divert to unused space... this could
be a bad sign...

Maybe it's not the hd that's bad... maybe it's just windows corrupted user
account but I doubt it somehow...

Smart thing to do would be to get new hd's copy the whole motherfucker... do
a file by file... byte by byte comparision to know if everything was copied
properly... this gonna take a bitching long time but ok...

As long as I don't delete and put anything new on the disk it should be ok.
I hope...

So far it seems C: drive is fucked... maybe D: drive still ok.

I guessed I made that data backup just in time ! I was about due... and the
user account corruption was also a bad sign... so I thought I better make
that backup just in case... and not a moment to late it seems !

Anyway this does prove that windows is good at detecting corruption even if
it's in weird ways... as long as the user "listens" to the system and pays
attention and is sensitive and googles around this will become apperent...

Windows update was failing which was the first sign of trouble. Somebody
mention user account corruption which was the second sign of trouble ?!? or
maybe primary cause... me not sure yet...

Ram trouble can probably be ruled out... since after fresh reboot... same
location would be unlikely...

Winrar bug can be ruled out... definetly not winrar bug.

Scary !

Now I run the risk of losing my whole system which took years to build and
gather ?! Shitty ?!

I don't want that to happen even if Windows is sometimes a piece of shit ;)
:) It mostly works ok. Just sometimes explorer.exe hangs... and shit like
that... 99% statisfcation... 1% annoyances... SHIT.

So much trouble with this pc it's fricking unbelievable... but then again
this is the first PC which I spent day and night behind it... so sooner or
later something gonna pop up... To bad it has to happen/end like this lol.

To all "good ?" things come an end I guess... I had 3 years of fun with
it...

1. with at least two bad motherboard deaths...
2. one graphics card had to be removed/overheat...
3. gigaworks s750 death.
4. memory ram chip death.
5. pc case replacement was needed
6. cpu fan replacement was needed. original was too loudy..
7. paste shit needed/
8. new mouse needed.

Even motherboard started to wear and tear... at least three letters gone
lol.

Shit you may call me a heavy user... the mother/dad of all son of bitches :)

Sucks being me... LOL but only during these situations... otherwise it s
rocking the cradle.

I wonder what is next to die ?

My monitor ? pls not my monitor... if my 1000 euro bux monitor dies I am
going to jump of the building but not really ofcourse... everything dies
sometime... but it's painfull expensive to die ! ;)

Big fucking shit. Now I have to go back to my pentoum 3... me very glad I
still have it...

It has saved me three times before and now it will save me again... Holyshit
!

Shit shit shit shit shit shit shit I hate being on that thing it's so damn
slow... FUCK.

I can forget about youtube video's for a while... especially the hd's one :(

Oh well.

Skybuck signing off and facing another death scenerio for now.

YES TOTAL INSTALLATION/FILE SYSTEM DEATH STARING ME IN THE FACE RIGHT NOW.

WITH NO SYSTEM BACKUP AVAILABLE !!! OHOHOH
IT'S TO BIG TO BACKUP ON DVD'S WHICH ARE CRAP ANYWAY.

I am out of my mind typing this long message... but maybe it not so bad...
it will be my last one from this PC for a while ! :(((((

Bye,
BYEEEEEEEEEEEEEEEEEE
Skybuck ! ;) =D


CellShocked

unread,
Oct 30, 2009, 5:11:21 AM10/30/09
to
On Fri, 30 Oct 2009 09:10:19 +0100, "Skybuck Flying"
<Blood...@hotmail.com> wrote:

>
>I did one last check:


Have you ever considered that the file might be corrupt BEFORE the burn
session? Have you checked the file itself?

Also, are you burning an oversized session?

Corrupted file system cache?

Dude, you are so stupid as it related to computers.

You cannot guess what things mean or how they work.

You cannot go through life only looking at the pictures and reading the
captions.
You need to LEARN about computers, and not from your own hand, by a
competent professional.

If you already claim to have done so, the instructor was and is an
incompetent ditz!


Also, your incessant cros-posting extends BEYOND being retarded. You
need professional mental health care!

Dave Platt

unread,
Oct 30, 2009, 2:31:57 PM10/30/09
to
In article <e44b4$4aea9f68$d53372a9$71...@cache4.tilbu1.nb.home.nl>,
Skybuck Flying <Blood...@hotmail.com> wrote:

>Unless other people have the same offset/position as damaged then it's
>probably just a problem with one of my hd-disks...

Or your RAM or motherboard or CPU.

A single-bit error in your DRAM (either when reading or writing) could
result in this sort of corruption.

Get yourself a MEMTEST86+ boot image from http://www.memtest.org/ (it
can go on a floppy or a bootable CD-ROM or a bootable USB stick).
Fire it up. Let it run memory tests for a day or so. See if any
memory errors are detected.

If you, you may have bad memory... or a glitchy motherboard... or
simply an incompatibility between otherwise-good memory and an
otherwise-good motherboard (e.g. there are some motherboards which can't
safely use "dual channel" memory mode if you load up all of the DDR
SDRAM slots... there's too much capacitance).

Or, possibly you've overclocked your system (or manually narrowed the
memory timings) beyond what the memory or board can handle.

>Big shit though... this means I will have to stop using my "Dream PC" which
>can now be rightfully called "Nightmare PC" until I get new harddisks...
>this also means the Antec 1200 case could be risky... especially when
>cleaning dustfilters while hd's are on... this could also mean placing tower
>on table is bad because of bumps against table or so... which might kill
>hd's ?! BIG SHIT... can't place PC on ground because of dust.

Yeah, do *not* bang or pound on the computer when the disks are
spinning, and don't tilt the chassis to another angle either. All of
these can be hard on a spinning hard drive.

Just turn off the computer before performing preventive maintenance,
OK?

Oh... and there's one thing you should really *NOT* do. You should
not use a world-wide netnews distribution system as if it was your own
personal blog. If you want to blog (or just free-associate about
your latest incident of toothbrushing and broken shoelaces), use a
real blogging service, or Twitter, or something like that, OK?

A guy I worked with some years ago had a sign posted on his office
door: "Logorrhoea exclusion area. Violators will be subject to
pleonasty."

--
Dave Platt <dpl...@radagast.org> AE6EO
Friends of Jade Warrior home page: http://www.radagast.org/jade-warrior
I do _not_ wish to receive unsolicited commercial email, and I will
boycott any company which has the gall to send me such ads!

Skybuck

unread,
Oct 30, 2009, 10:03:40 PM10/30/09
to
First I want to say, thanks for thinking with me/helping me
out ! ;) :)

On Oct 30, 7:31 pm, dpl...@radagast.org (Dave Platt) wrote:
> In article <e44b4$4aea9f68$d53372a9$7...@cache4.tilbu1.nb.home.nl>,


>
> SkybuckFlying <BloodySh...@hotmail.com> wrote:
> >Unless other people have the same offset/position as damaged then it's
> >probably just a problem with one of my hd-disks...
>
> Or your RAM or motherboard or CPU.
>
> A single-bit error in your DRAM (either when reading or writing) could
> result in this sort ofcorruption.

I thought about this a little bit and I thought it was plausible... a
single bit error in memory could have caused the file to get
corrupted... then once written to disk it would ofcourse stay
corrupted... fooling me into believing the harddisk might be
corrupt ;) <- worst case scenerio.

The idea of having just memory corruption is less bad than hd
corruption so I decided to test this theory... especially since I was
fooled last time believing the power supply might be bad or so... also
this could save me from going through a whole lot of trouble... though
making a backup of my system drive don't sound so bad to me
either ! ;) :) Maybe I am still gonna do that just in case ! ;) :)
This one was scary :)

> Get yourself a MEMTEST86+ boot image fromhttp://www.memtest.org/(it
> can go on a floppy or a bootable CD-ROM or a bootable USB stick).
> Fire it up.  Let it run memory tests for a day or so.  See if any
> memory errors are detected.

Fortunately I happen to have this handy disk in my toolset ! ;) :)

So I popped it into my computer... first my computer didn't wanna boot
from the floppy which was kinda odd... I activated the boot menu but
the boot menu fucked up and it went into windows... I was like shit I
don't want this but ok...I was also nervous that maybe the floppy
drive was wrongly connected or didn't work or something so I tested it
with a msdos disk and windows could read it so the floppy drive was
fine...

So after telling windows to restart the floppy disk finally booted...
and memtest began to load... I was like jipppee !

Only a few seconds after running memtest it already reported a bit
error in memory !

Currently it says:

Memtest86+ v1.65

Athlon 64 X2 2006 Mhz
L1 Cache: 128K 16443MB/s
L2 Cache: 512K 3918MB/s
Memory: 4095M 2063MB/s

Walltime Cached RsvdMem MemMap Cache ECC Test Pass Errors ECC errors
0:16:55 4095M 1380K e820-Std on off std 0
159 0

Tst Pass Failing Address Good Bad Err-
Bits Count
1 0 0003712b68c - 881.6 MB 3712b68c 3712b48c 00000200 159

So it seems there is bad memory in the system... seems like 2 bits
bad ? So just two bad bits can cause a hell lot of a mess ! ) :)

Now the big question for me is:

1. Why did one of the memory chips go bad ? Is it still a reminensence
of my "plastic experiment" where plastic tape fell on it... <- it's
possible.

2. Or did the memory chip die from heat from the heatpipes from the
big cpu cooler ?!? <- Plausible. This could mean trouble for the
future as well.

or

3. Did the memory chip just die because of general system heat... ?!?

or

4. Is it bad quality from Corsair ? I don't think so but ok.

Fortunately Corsair was nice and smart enough to sent me two new
memory chips when another one was bad not so long ago. That's why I
still have 4 GB of ram I guess... and I guess I also have a spare
memory chip somewhere not sure ?!? ;)

Maybe I could even sent this one back and still get warranty
lol ?!? ;) I don't know maybe I still have warranty on it I don't
know...

Usually I only use 2 GB of rams... so I have at least 3 spare memory
chips if I am not mistaken.

Not the only problem is in figuring out which memory chip went bad...
I think I can manage that ! ;)

After I get rid of the bad memory chip I can do a copy test again...
and see if it works out this test...

Me would be pretty glad if only this is the problem ;) :)

So big thanks to you Dave Platt ! ;) :

I owe you one ! =D

> If you, you may have bad memory... or a glitchy motherboard... or
> simply an incompatibility between otherwise-good memory and an
> otherwise-good motherboard (e.g. there are some motherboards which can't
> safely use "dual channel" memory mode if you load up all of the DDR
> SDRAM slots... there's too much capacitance).
>
> Or, possibly you've overclocked your system (or manually narrowed the
> memory timings) beyond what the memory or board can handle.

Nope, no overclocking... unless asus motherboard does that but I don't
think so ;)

>
> >Big shit though... this means I will have to stop using my "Dream PC" which
> >can now be rightfully called "Nightmare PC" until I get new harddisks...
> >this also means the Antec 1200 case could be risky... especially when
> >cleaning dustfilters while hd's are on... this could also mean placing tower
> >on table is bad because of bumps against table or so... which might kill
> >hd's ?! BIG SHIT... can't place PC on ground because of dust.
>
> Yeah, do *not* bang or pound on the computer when the disks are
> spinning, and don't tilt the chassis to another angle either.  All of
> these can be hard on a spinning hard drive.

Yeah but then again... some of these drives end op in jet
fighters ! ;)

>
> Just turn off the computer before performing preventive maintenance,
> OK?

Yeah from now on I will do this just in case... this was some scary
shit...

Hmm interesting it just found another error !

Tst Pass Failing Address Good Bad Err-Bits Count
5 0 0003712b688 - 881.6MB ffffff7f fffffd7f 00000200 1

And another one just popped up ! ;) :)

Tst Pass Failing Address Good Bad Err-Bits Count
6 0 0003712b68c - 881.6MB fffffff7 fffffdf7 00000200 16

Most interesting so it seems the program is doing multiple different
memory tests and is coming across the same bits as being bad
again ! ;)

Good program memtest86 ! ;)

> Oh... and there's one thing you should really *NOT* do.  You should
> not use a world-wide netnews distribution system as if it was your own
> personal blog.  If you want to blog (or just free-associate about
> your latest incident of toothbrushing and broken shoelaces), use a
> real blogging service, or Twitter, or something like that, OK?

But you helped me out and that's what it's all about ! =D

>
> A guy I worked with some years ago had a sign posted on his office
> door:  "Logorrhoea exclusion area.  Violators will be subject to
> pleonasty."

What does that mean ? :)

Ok thanks Pal... it's time for me to go and be happy and figure out
what memory chip it is...

It would be interesting if it was the chip closest to the heat pipe...

Before I touch inside of my PC I make picture of it first...

Gonna document everything to make sure I figure it out ! ;)

Bye,
Skybuck.

Archimedes' Lever

unread,
Oct 30, 2009, 10:42:17 PM10/30/09
to
I cannot believe some of the horseshit responses this has garnered.

Ever stop to think that he may have a dog slow box, and has his burn
software cache setting so WRONG that he causes the problem? He even said
he was on the internet once. That would not matter on MY box, but on a
SkyTard convolution, it very well may.

It is commonly referred to in the optical disc recording realm as
"buffer underrun" or "buffer overrun".

If his RAM had a problem, Windows would catch it, because Windows does
a RAM exercise as it comes up. Overclocked wrong? It fails to boot. Bit
error... it FAILS TO BOOT!


Got it?

What he should do is start SMALL. Take ONE RAR file and do a burn
session. If that fails, his burn software is set up wrong. Likely
because the dope fucked with the settings when he failed the first
session.

He has zero diagnostic capacity because that requires knowledge of the
hardware, and he falls severely short of that mark.

So, HE should NOT be doing ANY of this. ESPECIALLY if his "fix session"
began with making a bunch of software setting changes, instead of making
them ONE AT A TIME.

I would also bet that he NEVER did a "practice burn" where all the data
streams move around to test the burn function, but no burn wastes a disc.

He needs several forms of "help" in his life, not the least of which is
his parents hand across his ass for being such an inconsiderate,
cross-posting, Usenet abusing little bastard.

Top posted because nothing you said makes a fuck.

The hard drive remark is total bullshit too. An old hard drive form
the 80s might have slop in the bearings, but modern hard drives are MADE
to take motion in ALL axis DURING OPERATION.

You're an idiot to think that they are not.


On Fri, 30 Oct 2009 11:31:57 -0700, dpl...@radagast.org (Dave Platt)
wrote:

Archimedes' Lever

unread,
Oct 30, 2009, 11:40:13 PM10/30/09
to
On Fri, 30 Oct 2009 19:03:40 -0700 (PDT), Skybuck
<skybu...@hotmail.com> wrote:

>So it seems there is bad memory in the system... seems like 2 bits
>bad ? So just two bad bits can cause a hell lot of a mess ! ) :)
>
>Now the big question for me is:
>
>1. Why did one of the memory chips go bad ? Is it still a reminensence
>of my "plastic experiment" where plastic tape fell on it... <- it's
>possible.


A: Have you overclocked the damned thing? As little as you know about
them, you need to keep them at stock operating levels. Overclocking a
machine will DEFINITELY result in fouled operation, ESPECIALLY if one
does not know what one is doing, and you do not.

Next: Have you tried re-seating the stick(s)?

Did you buy them used, or were they packaged by their manufacturer?

And finally, find out where your help is coming from, and TRIM your
group list so that you can keep it where it belongs. You do not need to
continue your blatant, inconsiderate cross-posting after you have found
assistance. You can keep it down to the group that the dope that tried
to help you is "from".

I think it is pretty damned funny that only YOU have all these problems
through how many machines?

That is indicative of the fact that you are DICKING AROUND with your
hardware, while at the same time having no clue about how to protect it,
much less successfully dick with it.

In what... twenty five years, I have never had such an issue, and we
had loose memory chips that were MORE prone to failure.

The number of failure you SPEW about in these groups in the last year
and a half are so high that there is no doubt whatsoever that you are
doing things to your hardware that you should NOT be doing.
You most likely zap the piss out of everything, and then wonder why it
fails a month later.

You think what you got was help?

Archimedes' Lever

unread,
Oct 30, 2009, 11:41:40 PM10/30/09
to
On Fri, 30 Oct 2009 19:03:40 -0700 (PDT), Skybuck
<skybu...@hotmail.com> wrote:

>Fortunately Corsair was nice and smart enough to sent me two new
>memory chips when another one was bad not so long ago.


I'd be willing to bet that you are an ESD nightmare.

Despite you thinking that you are protecting your equipment, it is
pretty blatantly obvious that you are not.

Archimedes' Lever

unread,
Oct 30, 2009, 11:43:23 PM10/30/09
to
On Fri, 30 Oct 2009 19:03:40 -0700 (PDT), Skybuck
<skybu...@hotmail.com> wrote:

>Nope, no overclocking... unless asus motherboard does that but I don't
>think so ;)

The default BIOS setting DOES.

You have to manually set it to "manual" and then NO overclocking.

Archimedes' Lever

unread,
Oct 30, 2009, 11:50:29 PM10/30/09
to
On Fri, 30 Oct 2009 19:03:40 -0700 (PDT), Skybuck
<skybu...@hotmail.com> wrote:

>> >Big shit though... this means I will have to stop using my "Dream PC" which
>> >can now be rightfully called "Nightmare PC" until I get new harddisks...
>> >this also means the Antec 1200 case could be risky... especially when
>> >cleaning dustfilters while hd's are on... this could also mean placing tower
>> >on table is bad because of bumps against table or so... which might kill
>> >hd's ?! BIG SHIT... can't place PC on ground because of dust.
>>
>> Yeah, do *not* bang or pound on the computer when the disks are
>> spinning, and don't tilt the chassis to another angle either. �All of
>> these can be hard on a spinning hard drive.
>
>Yeah but then again... some of these drives end op in jet
>fighters ! ;)
>
>>

His hard drive remarks were baseless and pretty stupid.

In fact, it was the military that originally contracted that hard
drives be built and that is why they were practically rugged this whole
time. They are not "rugged", but they are mil spec, mechanically
speaking.

The original drives could not handle as much because they were 5.25"
form factor and had much larger masses being motored around on older
technology bearings. Those drives had way more problems.

Modern drives claim to be able to handle certain shocks *while under
operation*. They can certainly handle multi-axial transitions.

Skybuck Flying

unread,
Nov 2, 2009, 12:58:10 AM11/2/09
to
Yeah it was memory corruption ;) :)

See my reply to you in another thread ;)

At least 2 dvd's were burned correctly without memory errors it seems ;)

Bye,
Skybuck.


0 new messages