New BuildOS - Report Bugs Here

[gguruusa]

Originally Posted by Verix

Is anyone else having trouble downloading the latest updates?

What kind of trouble? Try downloading one at a time.

[maxm]

I'm trying to run BuildOS on Vista. I need to manually copy the ROM file (nk.nbf) to the New BootLoader_RUU folder from the RUU folder (I set it Standard) to load the ROM. In the new BuildOS, where is the resulting the nk.nbf file? It's not in the usual place (RUU folder).

Thanks
maxm

Update: Found it - the new BuildOS puts it in C:\Users\xxx\AppData\Roaming\hIq Inc\PPC-BuildOS\9.05.2.7Temp\RUU

[gguruusa]

Originally Posted by maxm

I'm trying to run BuildOS on Vista. I need to manually copy the ROM file (nk.nbf) to the New BootLoader_RUU folder from the RUU folder (I set it Standard) to load the ROM. In the new BuildOS, where is the resulting the nk.nbf file? It's not in the usual place (RUU folder).

Thanks
maxm

Update: Found it - the new BuildOS puts it in C:\Users\xxx\AppData\Roaming\hIq Inc\PPC-BuildOS\9.05.2.7Temp\RUU

If you build your rom correctly (choose your bootloader version in the REV dropdown on the toolbar), the correct ruu should have started up for you. No need to copy anything anywhere.

[SBR_L3GION]

Originally Posted by maxm

I'm trying to run BuildOS on Vista. I need to manually copy the ROM file (nk.nbf) to the New BootLoader_RUU folder from the RUU folder (I set it Standard) to load the ROM. In the new BuildOS, where is the resulting the nk.nbf file? It's not in the usual place (RUU folder).

Thanks
maxm

Update: Found it - the new BuildOS puts it in C:\Users\xxx\AppData\Roaming\hIq Inc\PPC-BuildOS\9.05.2.7Temp\RUU

if you go in to programs and find the ppckitchen folder open the folder right click on the build os then look in the options it gives you it should see run as administrator then click on it and everything should run perfectly.

[maxm]

Originally Posted by gguruusa

If you build your rom correctly (choose your bootloader version in the REV dropdown on the toolbar), the correct ruu should have started up for you. No need to copy anything anywhere.

Thanks gguruusa. I've missed completely the Rev drop down.

maxm

[gguruusa]

Originally Posted by SBR_L3GION

if you go in to programs and find the ppckitchen folder open the folder right click on the build os then look in the options it gives you it should see run as administrator then click on it and everything should run perfectly.

This release shouldn't require that.

[Verix]

Originally Posted by gguruusa

What kind of trouble? Try downloading one at a time.

I uninstalled it, and reinstalled, and it worked fine.

[cleblanc92]

I am trying out the new BuildOS from an update today.
.9.05 (4/17/200.

I expected this would allow me to run off my primary work PC as hoped but still no luck. I see that the app is trying to hit "70.191.252.236:3000" but the program response with
"Server Unavailable."
"Unable to connect to the remote server"
then
"Login had expired"

...now I am SURE this will work fine from my home PC but the point is that I want to try and build w/out having to disconnect from the work network. Any thoughts or am a doomed to use this only from a home PC when I get the chance?

[gguruusa]

Originally Posted by cleblanc92

I am trying out the new BuildOS from an update today.
.9.05 (4/17/200.

I expected this would allow me to run off my primary work PC as hoped but still no luck. I see that the app is trying to hit "70.191.252.236:3000" but the program response with
"Server Unavailable."
"Unable to connect to the remote server"
then
"Login had expired"

...now I am SURE this will work fine from my home PC but the point is that I want to try and build w/out having to disconnect from the work network. Any thoughts or am a doomed to use this only from a home PC when I get the chance?

First, make sure you have a current .Net version installed. .Net2.0SP1 should do it, but to be certain, try .Net3.5. .Net2.0 will NOT work. To track the problem any further will probably require a special debugging build.

[cleblanc92]

Originally Posted by gguruusa

First, make sure you have a current .Net version installed. .Net2.0SP1 should do it, but to be certain, try .Net3.5. .Net2.0 will NOT work. To track the problem any further will probably require a special debugging build.

I currently have 1.1, 1.1 HotFix, 2.0 SP1, and 3.0 SP1. I will toss 3.5 to the pile and let ya know. Thanks for the suggestion!!