Channel scan fails at 22%

[Benarty]

Not sure if posted on the right forum and no suipport.zip included.

 

This might not be a DVBViewer problem so can someone verify that

a channel scan works with 3.6.0.2 ?

 

Platform : satellite so DVB-S, not DVB-C/T/S2

 

DVBViewer starts the scan, finds about 379 channels (22% in my case) but then DVBViewer freezes.

V3.5.0 did not had this problem.

If you can verify this, or scan works till end ...let me know.

[Benarty]

Not sure if posted on the right forum and no suipport.zip included.

 

This might not be a DVBViewer problem so can someone verify that

a channel scan works with 3.6.0.2 ?

 

Platform : satellite so DVB-S, not DVB-C/T/S2

 

DVBViewer starts the scan, finds about 379 channels (22% in my case) but then DVBViewer freezes.

V3.5.0 did not had this problem.

If you can verify this, or scan works till end ...let me know.

 

 

Well, I do a manual scan now on each frequency and that works. If I use auto scan then I have to dump most channels.

[Benarty]

Well, I do a manual scan now on each frequency and that works. If I use auto scan then I have to dump most channels.

 

 

NEWS: bad news: harddrive dead (samsung spinpout hd300LJ)

 

Harddisk died today. I did not recognize the upcoming failures and S.M.A.R.T did not warn either.

Most problems that i've been reporting might be caused by faulty harddisk. Yesterday, suddenly

audio drivers missing... I re-installed them again but after a restart, again, windows auto install's

sound driver.

 

Downloaded harddisk tool of harddisk manufacturer and diagnostic reported no errors.

Stripped down the system to see if it was no other hardware error but no, drive related.

 

First severe failure: could not boot.

I've low level formatted the disk (took several hours) and was able to re-partition and setup windows.

But, after the first windows updates suddenly system halt. No harddisk activity, no keyboard/mouse.

 

Grrr, again, started diagnostic tools from floppy, , tool can not find the harddisk anymore.

 

This drive traveled approx 700 km (ordered via internet) and I expect that the drive had to deal with one or more too large chocks.

 

Unmounted the drive, added to another computer, run the diagnostics again, failure.

 

So, anyway: ignore all my postings about so called DVBViewer errors.

 

 

I'm still gonna replace it with another samsung drive but from local dealer.

Still samsung cause this drive was performing fast enough (for a while) and these are one of the most silent drives. The replacement will be a HD320KJ so same but 16mb cache instead of 8.

 

Damn, need to call microsoft again, 3th time in less then one month.