I think I may have figured out why some people were having trouble running the app after first install. Hopefully, version 0.27 should fix it.
Please visit the beta page to download 0.27.
If you've been having trouble running previous versions, I would really appreciate it if you could download the latest and give it a try. Please let me know if the issue is still happening. Thank you.
I downloaded and installed the new version. It installed in the (x86) program folder even though I am running a 64 bit OS. Install went fine. It asked me to accept license agreement and I did.
I then went to options and told it to import my config file, surfed to it, clicked open...then it crashes. By crash, I mean the program vanishes completely as if I clicked the X in the upper corner. No errors, nothing. Here is the content of the crash.log:
Crash log generated 12/6/2012 1:19:51 AM
Message: Input string was not in a correct format.
Stack: at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at disParity.OldConfig..ctor(String path)
at disParity.Config.ImportOld(String path)
at disParityUI.OptionsDialogViewModel.ImportOldConfiguration(String path)
at disParityUI.OptionsDialog.HandleImportClick(Object sender, RoutedEventArgs args)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.Controls.Button.OnClick()
at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)
at System.Windows.Input.InputManager.ProcessStagingArea()
at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
at System.Windows.Window.ShowHelper(Object booleanBox)
at System.Windows.Window.ShowDialog()
at disParityUI.MainWindow.OptionsExecuted(Object sender, ExecutedRoutedEventArgs e)
at System.Windows.Input.CommandBinding.OnExecuted(Object sender, ExecutedRoutedEventArgs e)
at System.Windows.Input.CommandManager.ExecuteCommandBinding(Object sender, ExecutedRoutedEventArgs e, CommandBinding commandBinding)
at System.Windows.Input.CommandManager.FindCommandBinding(CommandBindingCollection commandBindings, Object sender, RoutedEventArgs e, ICommand command, Boolean execute)
at System.Windows.Input.CommandManager.FindCommandBinding(Object sender, RoutedEventArgs e, ICommand command, Boolean execute)
at System.Windows.Input.CommandManager.OnExecuted(Object sender, ExecutedRoutedEventArgs e)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.Input.RoutedCommand.ExecuteImpl(Object parameter, IInputElement target, Boolean userInitiated)
at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(ICommandSource commandSource, Boolean userInitiated)
at System.Windows.Controls.Button.OnClick()
at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)
at System.Windows.Input.InputManager.ProcessStagingArea()
at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
at System.Windows.Application.RunInternal(Window window)
at System.Windows.Application.Run()
at disParityUI.App.Main()
Can you email me a copy of your old config.txt file so I can debug this? Send it to rolandv@gmail.com. Thank you!
> It installed in the (x86) program folder even though I am running a 64 bit OS.
Yeah, this is an annoying limitation of the simple installer project I can build from Visual Studio. Even though .NET apps can run natively on both 32- and 64-bit OSs, the installer can only be one or the other. I don't want to set the installer platform to be x64, because I'm not sure what effect that will have on a 32-bit OS. I suspect it will refuse to install it.
I could get around this by having two installers, but that's a lot of extra hassle. Note that even though it is installing it to C:\Program Files (x86), it will still run as a 64-bit app.
I suppose I could hard-code the install directory to always be C:\Program Files\, but that might not be the correct path to the program folder on some machines.
old config.txt file sent, but here it is also:
tempram=1500
temp=E:\Temp\Parity Temp Folder
parity=M:\parity
data=N:\
data=O:\
data=P:\
data=Q:\
data=R:\
The original program was placed in C:\disparity
No problem about its location, just made me think it was a 32 bit app, not that it matters much.
Per your reply email, I changed the many data entries to data1, data2, etc. It then imported without any issues. It detected the change I had just made to one of the drives...I must say, the red ! worried me at first. :)
Ran into another issue. When I run the Update All I get an error "Update Failed. Update reference not set to an instance of an object. The drive says 4 new and 5 deleted.
I had the licence agreement windows with this installation, and always got the good version installed before.
Thanx for the columns width ;)
I added a disk and then "crashed" it and was able to restore it without any problem. Not a big one (40GB) but I didn't wanted to have the result next week ;)
> I must say, the red ! worried me at first. :)
Heh, sorry about that. It will show that whenever a delete, move, or edit is detected on a drive. It looks scary because those conditions mean the backup is compromised (i.e. if a drive were to fail at that moment, it might not be possible to do a full recover.)
> Ran into another issue. When I run the Update All I get an error "Update Failed. Update reference not set to an instance of an object. The drive says 4 new and 5 deleted.
Hmm, that's not good. I'm working on an update now that should capture more details about this error, should have it up soon. In the meantime, can you email me the file "disParity.log" which should be in the "logs" folder under the disParity app data folder? There's probably not much in there, but it's worth a shot. Thanks.
the log was empty, I went to send it to you and noticed that. I tried to remove the drive and it gave me an error and would not let me remove it.
I love the new version and really do not mind if you just say that the change is so massive between the two that I need to rebuild my parity. :) But for now, I will just wait in case you need more data for troubleshooting.
The parity data is 100% backwards compatible with the old version, so there should be no reason I can think of to force a rebuild after the upgrade. The error you are getting may or may not have anything to do with the fact that you upgraded from the old version. Either way it indicates a bug in the code and I'd really like to get to the bottom of it!
What is the error message you get when you try to remove the drive?
Also, is there anything special at all about this drive (e.g. removable, etc.) or is it just a plain vanilla hard drive like any other?
It is successfully removing the drive now. Not sure why it did not do it before, possibly I rebooted between the last try and now. I canceled the removal and started an Update All and now it is working.
I think you need to add a pop up telling people to reboot after the install and before they try to use the new software - that is most likely the cause of my previous problems. Everything is working perfectly now (the drive turned yellow and is updating, including the files it removed when I told it to remove the drive).
I will post the final results; it will take a while due to me adding two bluray rips and removing 5 bluray rips from that drive. After that, I have another drive to add, which is holding 1.1 TB of data.
The Update worked. I will begin the Add Disc shortly - I have to move some more files to that drive first.
Any plans on allowing two parity drives?
I'd add a dialog recommending a reboot if I knew why it was necessary. It really shouldn't be. There's nothing about the install process that should require a reboot. Even installing .NET 4.0 shouldn't require a reboot. I'd like to collect some feedback from more beta users first, see if other people are having similar problems or if this was a one-time fluke.
Glad to hear the update finally worked, though!
> Any plans on allowing two parity drives?
It's on the list with a million other things. I could spend the next year doing nothing but working on this program!
I wanted to update that adding the 3 TB drive, half filled, worked perfectly. Took a long time, but I expected that.
You must log in to post.