Hello!
First of all, is file extract from 3DO game CDs now illegal and has it been disabled for this reason in 4DO?
If YES then why is there no explicit warning about it?
If NO, then why is that feature not working?
Every time I try extracting a file, I get log entries like these:
12.01.2016 17:01:12 4DO Starting up
12.01.2016 17:01:31 Thread exception: System.IO.FileNotFoundException: Could not load file or assembly 'Ookii.Dialogs, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. Не удается найти указанный файл.
File name: 'Ookii.Dialogs, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'
at FourDO.UI.DiscBrowser.Browser.AskForFolder(String currentFolder)
at FourDO.UI.DiscBrowser.Browser.AskAndExtractToDirectory(IEnumerable`1 items)
at FourDO.UI.DiscBrowser.Browser.ExtractMenuItem_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
I'm using the installed 1.3.2.4 version.
File extract feature not working
Re: File extract feature not working
Okay, let me take a look.
Is it works in previous versions 1.3.2.3, 1.3.2.2?
Is it works in previous versions 1.3.2.3, 1.3.2.2?
Re: File extract feature not working
No. I installed 1.3.2.4 just recently. As the savefiles from previous version weren't seen by the new one, I left the 1.3.2.2 version installed.
Re: File extract feature not working
I see that there is a problem that will be fixed in the next version.
Re: File extract feature not working
Thank you very much!
Who is online
Users browsing this forum: No registered users and 59 guests