New BuildOS - Report Bugs Here - Page 59

x99percent · #**581** (**permalink**) 09-06-2008, 11:55 PM

Quote:

Originally Posted by gguruusa

? buildos doesn't create ppcgeeks_oem.rar. Give the exact error message, and what you were doing when you got it.

The error he's describing is:

Quote:

kitchens\PPCGeeks_OEM.rar

File create error

[OK]

**gguruusa** · #**582** (**permalink**) 09-07-2008, 04:01 AM

Caused by a conflct between 2 oems. You'll have to hunt for which ones through trial and error. start with any camera choice you have made.

x99percent · #**583** (**permalink**) 09-07-2008, 12:31 PM

Quote:

Originally Posted by gguruusa

Caused by a conflct between 2 oems. You'll have to hunt for which ones through trial and error. start with any camera choice you have made.

Samsung D3D drivers...

**Trident** · #**584** (**permalink**) 09-09-2008, 10:51 AM

I reported this problem in the 20273 Kitchen thread, but the exact same thing is happening when I try to open any project. I have tried with both the stock kitchen on each project and some of my modified projects. I'm going to try uninstalling and reinstalling Build OS and going from there-
Any help appreciated. This is what I happens:

I got a barrage of Microsoft .NET Framwork error messages.
"Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quite, the application will close immediately.

Attempted to read or write protected memory. This is often an indication that other memory is corrupt"
Details
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at System.Windows.Forms.UnsafeNativeMethods.CallWindo wProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at System.Windows.Forms.NativeWindow.DefWndProc(Messa ge& m)
at System.Windows.Forms.Control.DefWndProc(Message& m)
at System.Windows.Forms.Control.WmEraseBkgnd(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ListView.WndProc(Message& m)
at EventListView.EventListView.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
PPC-BuildOS
Assembly Version: 9.5.0.0
Win32 Version: 9.05.2.7
CodeBase: file:///C:/Program%20Files/PPCkitchen.org/BuildOS/BuildOS/PPC-BuildOS.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
EventListView
Assembly Version: 1.0.3037.22458
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files/PPCkitchen.org/BuildOS/BuildOS/EventListView.DLL
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Web.Services
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Web.Services/2.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll
----------------------------------------
muuunfub
Assembly Version: 9.5.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Deployment
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Deployment/2.0.0.0__b03f5f7f11d50a3a/System.Deployment.dll
----------------------------------------
UnRARNET
Assembly Version: 1.0.3039.20609
Win32 Version: 1.0.3039.20609
CodeBase: file:///C:/Program%20Files/PPCkitchen.org/BuildOS/BuildOS/UnRARNET.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
-------------

Pressed Continue a bunch of times, but just kept on getting the message.
Pressed Quit and it all ended.

**Trident** · #**585** (**permalink**) 09-09-2008, 12:04 PM

Uninstalled and reinstalled BuildOS.
I modified the 20273 RAR file- but now when I run BuildOS I get as far as making my selections from the project [I had to modify the project by changing the name of the kitchen file to the new file that I created; I just added the three files discussed above and renamed it].
When BuildOS starts to run, almost immediately I get an error message:

ROM folder does not exists.
ROM\XIP\

I looked in every folder I could find and I did find those folders, but I've apparently done something wrong.
I'll keep playing with it... but if someone has seen this before or can give me a nudge in the right direction...
Thanks.

**gguruusa** · #**586** (**permalink**) 09-11-2008, 01:04 AM

Quote:

Originally Posted by Trident

I reported this problem in the 20273 Kitchen thread, but the exact same thing is happening when I try to open any project. I have tried with both the stock kitchen on each project and some of my modified projects. I'm going to try uninstalling and reinstalling Build OS and going from there-
Any help appreciated. This is what I happens:

I got a barrage of Microsoft .NET Framwork error messages.
"Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quite, the application will close immediately.

Attempted to read or write protected memory. This is often an indication that other memory is corrupt"

Caused by installing IE8. Don't know why. To work around, remove the BackgroundImage=line from kitchen_config.txt in the .rar

**gguruusa** · #**587** (**permalink**) 09-11-2008, 01:05 AM

Quote:

Originally Posted by Trident

Uninstalled and reinstalled BuildOS.
I modified the 20273 RAR file- but now when I run BuildOS I get as far as making my selections from the project [I had to modify the project by changing the name of the kitchen file to the new file that I created; I just added the three files discussed above and renamed it].
When BuildOS starts to run, almost immediately I get an error message:

ROM folder does not exists.
ROM\XIP\

I looked in every folder I could find and I did find those folders, but I've apparently done something wrong.
I'll keep playing with it... but if someone has seen this before or can give me a nudge in the right direction...
Thanks.

Uh, your renaming is where you went wrong. More than likely, you didn't match the name in your selections.txt with the new name.

psiphi · #**588** (**permalink**) 09-11-2008, 05:46 PM

Quote:

Originally Posted by x99percent

Samsung D3D drivers...

Confirmed, I get the same error when including the Samsung D3D drivers...

userfriendly8a · #**589** (**permalink**) 09-11-2008, 11:08 PM

I received the following error message when launching the buildOS.exe after using the updater.
__________________________________________________ ________
PPC-BuildOS.exe - Application Error
---------------------------
The application failed to initialize properly (0xc0000135). Click on OK to terminate the application.
---------------------------
OK
__________________________________________________ _____________
I am wondering why this is occuring. Thanks for any input anyone may have.

**gguruusa** · #**590** (**permalink**) 09-12-2008, 08:49 AM

Quote:

Originally Posted by userfriendly8a

I received the following error message when launching the buildOS.exe after using the updater.
The application failed to initialize properly (0xc0000135). Click on OK to terminate the application.
__________________________________________________ _____________
I am wondering why this is occuring. Thanks for any input anyone may have.

becuase:

a) you didn't read
b) you didn't search
c) you don't have .Net 2.0 SP1 or later installed
d) the installer didn't install it for you (ok, I'll claim that one)

As long as you are here, if you want to find me in chat BEFORE you install .Net, you can help me test new installers to see if they'll correctly warn of not having an appropriate version of .Net installed