Thread: Kitchen OEMs
View Single Post
  #133 (permalink)  
Old 02-23-2007, 07:31 PM
JBabey's Avatar
JBabey
Halfway to VIP Status
Offline
Location: http://www.SoulPirates.NET
 
Join Date: Dec 2006
Posts: 567
Reputation: 27
JBabey is just getting started
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Send a message via ICQ to JBabey Send a message via AIM to JBabey Send a message via MSN to JBabey Send a message via Yahoo to JBabey Send a message via Skype™ to JBabey
Quote:
All of the versions of .Net Ive used (on the ftp) don't seem to work. I believe it's something to do with the order of installation and over writing existing files. My workaround is just install from .cab into the ext_rom. Even though the install says it fails and no space is used in the ext_rom .Net then works.

this is true, if you dig deep enough though youll see that if your going to use one on the FTP (mine is a combined 1 & 2 if i remember) youll need to go into the OS folder & delete folder

38f43c9f-bc38-430e-81d1-a2e6c650f225

This folder holds some half-ass DLL's that will conflict with your CreateOS when trying to use an OEM of .NET (im not sure why they are there, or if they are for the kitchens install of .NET1)

i have not tested dropping all of the NET2 dll's into that folder and see if it will install a working .NET2.... may be worth a shot though,

I ramble... anyways, if your going to OEM .NET then make sure you delete that folder in the OS before create-os (or back it up somewhere)

if you use my package, and delete that file youll have no problems, every OEM i am posting up has been tested to work properly... albeit a billion flashes ><

__________________
~Big.J
Reply With Quote