Version 6.00 B3 Available...

[dexter]

Beta 3 is now available. The logic for identifying password protected RAR sets is working correctly now. The AutoPAR function is working more reliably now too.

• Added a toolbar to the Files tab
• Newsbin will allow you to enter a password for encrypted RAR's now.
• Fixed issue where selection size was messed up if you select individual expanded items in a post list.
• Fixed issue where Newsbin would present multiple password requests if you password protected maximize from system tray
• Removed language selection from installer until we get translations started.

There are many many other changes that are listed on the Newsbin Beta Page and in the text release notes that are available to you after the installer completes the upgrade.

Two notes:
1) Installer currently does not give the option to launch Newsbin after it runs. I'm working on an issue where launching this way was always running as admin.
2) Don't use the ImageDB, it's broken.

The wiki buglist reflects current known issues and the list of fixed issues. This does not include inter-release issues that are found and addressed on the IRC channel.

The download link is on the Newsbin Beta Page

Update: Installer now resets the GUI. Without it, Newsbin might crash on startup. You'll have to move your windows around and re-assign any customizations. This may be a frequent occurance between betas. We'll look for some workaround if it gets to be too much of a pain.

[orygun]

Tried three times to download b3- super long time for 11 meg file.. did install but crashes on launch. Installed second time, same. Uninstalled (kept important files), installed 3rd time- same crash on launch.

XP sp2 2.66 intel Quad cpu, 3GB ram.

Oh-- so confident was I that I deleted the B2 install.. recall you guys don't keep the older versions around..

[Innuendo]

Crashed on launch for me too. Then Windows 7 came back and said it applied some compatibility settings so it would work. Well, it would launch then, but only in an unlocked state. Had to run Task Manager to kill it.

Beta 3 is a bust.

[Mobius]

Crash on launch after upgrade from previous beta on Windows 7 x64. Opened from shortcut fine after that.

[Quade]

Win7 64 here. Installed both the 64 bit and 32 bits and they ran fine. Then wiped the registry and did the same thing and it ran. Then wiped the data folder and registry and it ran fine.

Does it say anything when it dies?

Alpha testers have been running it for most of 2 days now.

[Mobius]

I didn't capture screenshot. Here's event viewer entry for the crash. Do you want the attached files from the log report?

Faulting application name: Newsbinpro64.exe, version: 6.0.0.0, time stamp: 0x4d62f3fe
Faulting module name: Newsbinpro64.exe, version: 6.0.0.0, time stamp: 0x4d62f3fe
Exception code: 0xc000041d
Fault offset: 0x00000000000d4b63
Faulting process id: 0x10bc
Faulting application start time: 0x01cbd24a3472c203
Faulting application path: C:\Program Files\NewsBin\Newsbinpro64.exe
Faulting module path: C:\Program Files\NewsBin\Newsbinpro64.exe
Report Id: 752c59dc-3e3d-11e0-b20e-005056c00008


Fault bucket 30359551, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Newsbinpro64.exe
P2: 6.0.0.0
P3: 4d62f3fe
P4: Newsbinpro64.exe
P5: 6.0.0.0
P6: 4d62f3fe
P7: c000041d
P8: 00000000000d4b63
P9:
P10:

Attached files:
C:\Users\XYZ\AppData\Local\Temp\WER7168.tmp.WERInternalMetadata.xml
C:\Users\XYZ\AppData\Local\Temp\WER84BA.tmp.appcompat.txt
C:\Users\XYZ\AppData\Local\Temp\WER84F9.tmp.mdmp

These files may be available here:
C:\Users\XYZ\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Newsbinpro64.exe_2a9c46b718aae157b3bca3e2e814c33e7f74d9f8_1681c3ac

Analysis symbol:
Rechecking for solution: 0
Report Id: 752c59dc-3e3d-11e0-b20e-005056c00008
Report Status: 9

[kairk]

Same thing is happening to me Windows XP SP 3 32 bit. I deleted Downloads.db3, Downloaded.db3, PAR.db3, RPB.db3 and AutoPAR2.DB3 and it still crashes on startup.

[Mobius]

When collapsing posts in download frame, there is a redraw problem. Vertical black lines appear and disappear quickly. Did not happen in previous beta.

Is it possible to make the NB Security Window be in focus if we happen to double click the tray icon?

[dexter]

I've recreated on both 32 and 64 bit. Strange it didn't happen on my main machine, this is on my laptop.

If you need to go back to B2, use this link

Update: I've found a workaround. If you delete the "workspace" registry key under HKCU\Software\DJI Interprises\Newsbin50, it'll start working.

[Innuendo]

Confirmed Dex's work-around works. Now all Quade has to do is figure out why.

[orygun]

Rgr, workaround got it going for me. Thank.s

[Andreas]

The 'cursor left' and 'cursor right' keys do not work in the text input field of Internet Search.

[Quade]

Wow. I know why too.

Thanks.

Fixed it.

[magician1962]

Also installed B3 on Win7 63 as an upgrade,works fine

Though one small issue its forgotton how to count 1+TB to download, I think not:)
Update now 1.6TB! actuall is about 6GB

[Kjdata]

When you download a image and the thumbs tab are on top, so you can see the thumbs as they are downloading, newsbin freezes and you will have to kill it and restart newsbin.
You can download image files when the download list tab is on top, but if you shift to the thumbs tab while the image files are downloading newsbin freezes instantly.

smile to the world and the world smiles back

[Quade]

Yeah, thanks. Fixed it.

[Moondawgie]

I've recreated on both 32 and 64 bit. Strange it didn't happen on my main machine, this is on my laptop.

If you need to go back to B2, use this link

Update: I've found a workaround. If you delete the "workspace" registry key under HKCU\Software\DJI Interprises\Newsbin50, it'll start working.

I am also experiencing the problem of B3 failing to respond shortly after it's started on my computer. Even after the removal of the "workspace" registry key. I've returned to the use of B2 which does not exhibit such behavior.

Each time Newsbin 6B3 stops responding, the following two entries are posted to the Windows 7 Event Log:

First Entry:

Log Name: Application
Source: Windows Error Reporting
Date: 2/24/2011 10:00:58 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: KingFish-PC
Description:
Fault bucket 1741921411, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: Newsbinpro64.exe
P2: 6.0.0.0
P3: 4d62f3fe
P4: 62f5
P5: 1
P6:
P7:
P8:
P9:
P10:

Attached files:
C:\Users\KingFish\AppData\Local\Temp\WER7F11.tmp.appcompat.txt
C:\Users\KingFish\AppData\Local\Temp\WER822E.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\KingFish\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppHang_Newsbinpro64.exe_cfe1c3dcc73972e4a3248a16ff8873d99612e3e_37f98d73

Analysis symbol:
Rechecking for solution: 0
Report Id: 0442182d-4040-11e0-88ac-0023542084e5
Report Status: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-02-24T18:00:58.000000000Z" />
<EventRecordID>4534</EventRecordID>
<Channel>Application</Channel>
<Computer>KingFish-PC</Computer>
<Security />
</System>
<EventData>
<Data>1741921411</Data>
<Data>5</Data>
<Data>AppHangB1</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>Newsbinpro64.exe</Data>
<Data>6.0.0.0</Data>
<Data>4d62f3fe</Data>
<Data>62f5</Data>
<Data>1</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
C:\Users\KingFish\AppData\Local\Temp\WER7F11.tmp.appcompat.txt
C:\Users\KingFish\AppData\Local\Temp\WER822E.tmp.WERInternalMetadata.xml</Data>
<Data>C:\Users\KingFish\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppHang_Newsbinpro64.exe_cfe1c3dcc73972e4a3248a16ff8873d99612e3e_37f98d73</Data>
<Data>
</Data>
<Data>0</Data>
<Data>0442182d-4040-11e0-88ac-0023542084e5</Data>
<Data>0</Data>
</EventData>
</Event>

Second Entry:

Log Name: Application
Source: Application Hang
Date: 2/24/2011 10:01:01 AM
Event ID: 1002
Task Category: (101)
Level: Error
Keywords: Classic
User: N/A
Computer: KingFish-PC
Description:
The program newsbinpro64.exe version 6.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 584
Start Time: 01cbd44856183eb8
Termination Time: 0
Application Path: C:\Program Files\NewsBin\newsbinpro64.exe
Report Id: 0442182d-4040-11e0-88ac-0023542084e5

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Hang" />
<EventID Qualifiers="0">1002</EventID>
<Level>2</Level>
<Task>101</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2011-02-24T18:01:01.000000000Z" />
<EventRecordID>4535</EventRecordID>
<Channel>Application</Channel>
<Computer>KingFish-PC</Computer>
<Security />
</System>
<EventData>
<Data>newsbinpro64.exe</Data>
<Data>6.0.0.0</Data>
<Data>584</Data>
<Data>01cbd44856183eb8</Data>
<Data>0</Data>
<Data>C:\Program Files\NewsBin\newsbinpro64.exe</Data>
<Data>0442182d-4040-11e0-88ac-0023542084e5</Data>
<Binary>430072006F00730073002D0074006800720065006100640000000000</Binary>
</EventData>
</Event>

Note: The following is displayed in the "Binaries" area at the bottom of the Details section of the second entry:

"Binary data:

In Words

0000: 00720043 0073006F 002D0073 00680074
0008: 00650072 00640061 00000000

In Bytes

0000: 43 00 72 00 6F 00 73 00 C.r.o.s.
0008: 73 00 2D 00 74 00 68 00 s.-.t.h.
0010: 72 00 65 00 61 00 64 00 r.e.a.d.
0018: 00 00 00 00 ...."

C.r.o.s.s-.t.h.r.e.a.d, ?

I don't know if posting so much information is necessary or appropriate. If so, please feel free to politely chastise me. I'm only trying to help.

[dexter]

There are a couple of known issues in B3 that have just been resolved. I am about to post B4 now.

We generally don't get much useful information from the windows event log. Having a detailed procedure to try to recreate the issue ourselves is more useful.