Related
how to dump the newest 19839 ROM？
i found i can't dump it。can anybody tell me？
thanks
search my friend and it will do you wonders....
http://forum.xda-developers.com/showthread.php?t=379559
in this thread it should show you what you need...
no,this is not the way which can dump the 19839 rom your friend UDk made,and besides they just keep it as a secret and ignore every PM which were sent by the person who would be happy to know the truth.and someone just criticize that the other cookers who just start a "Cooker War" and on the other hand he just make some undumpable Rom as the prove of his selfishness.What a ridiculous phenomena....
You can use this http://forum.xda-developers.com/showthread.php?t=384251 tools to dump all polaris ROM's there is only one thing and that is that the cooker removes DSM/RGU files and packages.sof from his ROM and this makes it not possible to use it.
NikMel said:
You can use this http://forum.xda-developers.com/showthread.php?t=384251 tools to dump all polaris ROM's there is only one thing and that is that the cooker removes DSM/RGU files and packages.sof from his ROM and this makes it not possible to use it.
Click to expand...
Click to collapse
thanks,but the rom is only removes dsm and rgu.if u dump it ,u will find the rom is do something by the owner.
so i want to know it.
All roms can be dumped.
Using kitchen tools or Htc Rom Image Editor
http://forum.xda-developers.com/showpost.php?p=2028331&postcount=1
Use dsms & rgus from an older build into your dump directory ....
swtos said:
All roms can be dumped.
Click to expand...
Click to collapse
really do you think what wrote???
ervius said:
really do you think what wrote???
Click to expand...
Click to collapse
what do you mean ?
would it be unreasonable to ask for the dsm and rgu's of matching build to be provided, even in a separate archive? i have no problem with placing them into my dump before packaging, just dont like the idea of dsm/rgu from a different build. i prefer clean, true SYS..
edit: im speaking in general, not specifically for 19839. i just think that alot of authors are spending time reconstructing dumps that would be better spent developing with a known good, easily accessible source.
swtos said:
what do you mean ?
Click to expand...
Click to collapse
nothing.... dump it and rebuild.
dcd1182 said:
would it be unreasonable to ask for the dsm and rgu's of matching build to be provided, even in a separate archive? i have no problem with placing them into my dump before packaging, just dont like the idea of dsm/rgu from a different build. i prefer clean, true SYS..
edit: im speaking in general, not specifically for 19839. i just think that alot of authors are spending time reconstructing dumps that would be better spent developing with a known good, easily accessible source.
Click to expand...
Click to collapse
rgus and sdms are allways the same from build 19716, same!!!
ervius said:
rgus and sdms are allways the same from build 19716, same!!!
Click to expand...
Click to collapse
no, they are not. some SYS rgu's have changed between 19716 and 19199/19202/19209. as the dsm contains the build number info, it goes without saying they are different too.
i really mean no disrespect and i appreciate everything you guys do. ervius, your buildos and other tools are appreciated as well as your ROMs. but my point is that we are putting people to unnecessary trouble. what benefit does anyone gain from this?
dcd1182 said:
no, they are not. some SYS rgu's have changed between 19716 and 19199/19202/19209. as the dsm contains the build number info, it goes without saying they are different too.
i really mean no disrespect and i appreciate everything you guys do. ervius, your buildos and other tools are appreciated as well as your ROMs. but my point is that we are putting people to unnecessary trouble. what benefit does anyone gain from this?
Click to expand...
Click to collapse
yes, dsm contains version, but you solve with my dsm patcher...
and rgu, maybe only 19716 are differents, for me no differences from 19199 and last posted...
I think that microsoft provides us with TRUE SYS 19202 (Mar 24 - April 5 - 2008)....
So, there's no reason to patch dsms... to match a non existing version .....
swtos said:
All roms can be dumped.
Using kitchen tools or Htc Rom Image Editor
http://forum.xda-developers.com/showpost.php?p=2028331&postcount=1
Use dsms & rgus from an older build into your dump directory ....
Click to expand...
Click to collapse
oh,no
swtos,if u dump it?
you should to do it!and if u try ,u will find the rom is different .
does anybody find this?
the dsm youcan use the 19202 or 19209 or 19199,it will ok.
we know the dsm has the information of the ROM,but it's not important.
the important is if u can get the all file from the rom?!
GPRS said:
the dsm youcan use the 19202 or 19209 or 19199,it will ok.
we know the dsm has the information of the ROM,but it's not important.
the important is if u can get the all file from the rom?!
Click to expand...
Click to collapse
no, he cannot, only who protects roms can.....
@ervius
please can you post dsm's & rgu's that worked with your build ??
thanks.
how protected?and how dump?
anbody tell me?help!
yes, I agree with u. swtos's ROM can be dump but can't be rebuilt. I want to know what's the problem of the ROM.
GPRS said:
oh,no
swtos,if u dump it?
you should to do it!and if u try ,u will find the rom is different .
does anybody find this?
Click to expand...
Click to collapse
How do you disable Beta expiration?
Make an "app.reg" with this key:
Code:
[-HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\DeviceBeta]
then put it in an EXT folder.
Works like a charm. Thank you so much!
No problem...you are wellcome
Anyone help?
I have tried a couple of times now to use mortscript to remove the "BETA" tags from the registry. I obviously am doing it wrong - can someone post what the mortscript should be for me please?
this is what I tried just now and still no go...
Code:
If ( RegKeyExists("HKLM","\Software\Microsoft\Shell\Device Beta"))
RegDeleteKey("HKLM","\Software\Microsoft\Shell\Device Beta",TRUE,TRUE)
EndIf
Thanks
DT
d_train said:
I have tried a couple of times now to use mortscript to remove the "BETA" tags from the registry. I obviously am doing it wrong - can someone post what the mortscript should be for me please?
this is what I tried just now and still no go...
Code:
If ( RegKeyExists("HKLM","\Software\Microsoft\Shell\Device Beta"))
RegDeleteKey("HKLM","\Software\Microsoft\Shell\Device Beta",TRUE,TRUE)
EndIf
Thanks
DT
Click to expand...
Click to collapse
I may be wrong but I don't didn't the os like it if the registry is removed. It'll probably add them back.
I'd just put that in a app.reg in the last package to be processed by the kitchen like this:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\DeviceBeta]
"Today"=""
"Expiry"=""
"Reminder"=dword:00000000
wmserver said:
I may be wrong but I don't didn't the os like it if the registry is removed. It'll probably add them back.
I'd just put that in a app.reg in the last package to be processed by the kitchen like this:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\DeviceBeta]
"Today"=""
"Expiry"=""
"Reminder"=dword:00000000
Click to expand...
Click to collapse
I use old my own style kitchen with OEMs.
and simply include it in a .rgu file:
Code:
[-HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\DeviceBeta]
Don't know if works in app.reg in new style kitchens.
babak00000 said:
I use old my own style kitchen with OEMs.
and simply include it in a .rgu file:
Code:
[-HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\DeviceBeta]
Don't know if works in app.reg in new style kitchens.
Click to expand...
Click to collapse
just delete all instances of DeviceBeta from Shell rgu.
MietasSR said:
just delete all instances of DeviceBeta from Shell rgu.
Click to expand...
Click to collapse
I remove this.... but still have a bug for beta... white screen etc..
Nokser said:
I remove this.... but still have a bug for beta... white screen etc..
Click to expand...
Click to collapse
You need to patch shell32.exe. Da_G posted one in his thread. Use that.
For lazy people like me, use the attached pkg and put in your EXT. It will replace SYS reg..
ai6908 said:
You need to patch shell32.exe. Da_G posted one in his thread. Use that.
For lazy people like me, use the attached pkg and put in your EXT. It will replace SYS reg..
Click to expand...
Click to collapse
I still have bugs...
Nokser said:
I remove this.... but still have a bug for beta... white screen etc..
Click to expand...
Click to collapse
And later:
Nokser said:
I still have bugs...
Click to expand...
Click to collapse
White screen has nothing common with beta watermark or shell32 time-bomb
Hi
My ROM has some tweaks and extras that needs a soft reset after initialization wth 1st boot. How can I make a automatic reboot just the 1st time the phone boots up?
If you're using RunCC, edit your *.rgu/app.reg accordingly:
Code:
[HKEY_LOCAL_MACHINE\Software\HTC\RunCC]
"ResetDevice"=dword:00000001
How can I know if I use runCC?
You don't know which packages you're using for your ROM? Funny thing!
animelover said:
You don't know which packages you're using for your ROM? Funny thing!
Click to expand...
Click to collapse
hehe... just using a dump of official rhodium S2, and spiced it up a bit, and deleted things I don't need
Take a look into EXT -> Rhodium -> Your Build -> Rhodium_External_Packages and search for "RunCC"!
animelover said:
Take a look into EXT -> Rhodium -> Your Build -> Rhodium_External_Packages and search for "RunCC"!
Click to expand...
Click to collapse
yeye... there it is Thanks
animelover said:
You don't know which packages you're using for your ROM? Funny thing!
Click to expand...
Click to collapse
Funny indeed. These are the junior cooks we get these days...
No offense here but ...
I think all of great cooks started as "junior"
Even the big NRGZ28
best regards
fwt
hey hey... fair play ppl... glad to have new chefs CC is for that... new chefs and experienced chefs
fwt said:
No offense here but ...
I think all of great cooks started as "junior"
Even the big NRGZ28
best regards
fwt
Click to expand...
Click to collapse
Very true..
Anyways, I love your sig And it's quite funny how true it is!
if i might stick with the topic
2 - xda_uc also offers a reboot after customization - you could add this to your ext
3 - old method: autorun + checkautorun pkg also reboots your rom (dump blackstone or kovsky)
Problem With add2config Packages?
Hey, I had this problem before where all my packages that I cook in with the add2config method (so they can be removed by the user) aren't installing / aren't being set as default...
These are the following packages that I have the problem with:
BG4All Tabs (add2config) - Doesn't appear in the rom at all
A 6.5.5 Theme (add2config) - Isn't default but is in the list of themes
A 6.5.5 Taskbar (add2config) - Doesn't appear in the rom at all
All this was solved when I changed the runcc rgu file: e110406e-9af4-4cdc-932d-255ac9636f4d like everyone says to "ResetDevice"=dword:00000001
But since rebuilding my kitchen im having the same problem, Ive changed the reset device to 00000001 but still none of the add2config packages are working has anyone got any solutions?
Thanks
[★] said:
Hey, I had this problem before where all my packages that I cook in with the add2config method (so they can be removed by the user) aren't installing / aren't being set as default...
These are the following packages that I have the problem with:
BG4All Tabs (add2config) - Doesn't appear in the rom at all
A 6.5.5 Theme (add2config) - Isn't default but is in the list of themes
A 6.5.5 Taskbar (add2config) - Doesn't appear in the rom at all
All this was solved when I changed the runcc rgu file: e110406e-9af4-4cdc-932d-255ac9636f4d like everyone says to "ResetDevice"=dword:00000001
But since rebuilding my kitchen im having the same problem, Ive changed the reset device to 00000001 but still none of the add2config packages are working has anyone got any solutions?
Thanks
Click to expand...
Click to collapse
I'm not sure anyone will be able to answer that without being totally lucky if you don't post your packages or build-log or at least the add2config text files. Anway, maybe you already do this, but if you don't, then start doing this: after cooking, look in the dump and make sure everything is there. Also, look at config.txt to make sure all the add2config's were compiled properly. This will save you the flash-disappointment.
Ok theres my buildlog, my run cc rgu file and one of my add2config files Thanks.
fwt said:
No offense here but ...
I think all of great cooks started as "junior"
Even the big NRGZ28
best regards
fwt
Click to expand...
Click to collapse
Yeah, but I wasn't cooking ROMs for the public until I knew what the hell I was doing... lol
NRGZ28 said:
Yeah, but I wasn't cooking ROMs for the public until I knew what the hell I was doing... lol
Click to expand...
Click to collapse
lol, also I did this way...
Can't remember where I read something like "PPL: Could you make it in this language?" - " "COOK": I don't know how to!"
LOL
[★] said:
Hey, I had this problem before where all my packages that I cook in with the add2config method (so they can be removed by the user) aren't installing / aren't being set as default...
These are the following packages that I have the problem with:
BG4All Tabs (add2config) - Doesn't appear in the rom at all
A 6.5.5 Theme (add2config) - Isn't default but is in the list of themes
A 6.5.5 Taskbar (add2config) - Doesn't appear in the rom at all
All this was solved when I changed the runcc rgu file: e110406e-9af4-4cdc-932d-255ac9636f4d like everyone says to "ResetDevice"=dword:00000001
But since rebuilding my kitchen im having the same problem, Ive changed the reset device to 00000001 but still none of the add2config packages are working has anyone got any solutions?
Thanks
Click to expand...
Click to collapse
[★] said:
Ok theres my buildlog, my run cc rgu file and one of my add2config files Thanks.
Click to expand...
Click to collapse
Bumping my own question
[★] said:
Ok theres my buildlog, my run cc rgu file and one of my add2config files Thanks.
Click to expand...
Click to collapse
The add2config.txt file is in the wrong folder; it needs to go in the \files sub-folder of the EXT. Put it in there, and you're problems should go away.
Edit: although, I'm seeing this in the build-log:
Found: 1 Extra Info on a Package... Populating config.txt with: CAB: \Windows\B4ALL.cab
Click to expand...
Click to collapse
and this:
Processing "B4ALL.cab" as file
Click to expand...
Click to collapse
So, I guess I don't really understand why the .cab isn't installing. I've never used runcc before, so I can't help you on what may be going on with it. I guess it's ok to put the add2config in the main folder, since it looks like it's compiling correctly.
2nd Edit: all the cab is doing is adding a couple of manila files; you should just dump the two files and put them in an EXT and have them over-write the stock manila files. You don't need to run this as a cab, as far as I can tell.
You need to fix this (minor, but might as well do it):
Failed to parse value name HKEY_LOCAL_MACHINE\Security\Shell\StartInfo\start\Tools\Format SD Card.lnk!!!
Click to expand...
Click to collapse
Farmer Ted said:
The add2config.txt file is in the wrong folder; it needs to go in the \files sub-folder of the EXT. Put it in there, and you're problems should go away.
Edit: although, I'm seeing this in the build-log:
and this:
So, I guess I don't really understand why the .cab isn't installing. I've never used runcc before, so I can't help you on what may be going on with it. I guess it's ok to put the add2config in the main folder, since it looks like it's compiling correctly.
2nd Edit: all the cab is doing is adding a couple of manila files; you should just dump the two files and put them in an EXT and have them over-write the stock manila files. You don't need to run this as a cab, as far as I can tell.
You need to fix this (minor, but might as well do it):
Click to expand...
Click to collapse
(disregard my last post on the other thread, I didnt realise you had replied )
Thanks for the response, yeah the add2config file has worked before in the root of the packages, seems something else it buggy :/
Yeah that cab may be so, but that was an old one just as an example, I really need to get it working for this mortscript thing we discussed on the other thread..
Maybe we could discuss more tomorrow ? Perhaps you could have a nosey in my kitchen or something, I know I should work this stuff out myself, but as a chef still in training, its quite difficult to know what to look for, and help from peopel like you is priceless
Thanks
AndrewSh said:
23668 AKU 5307 Windows CE: 5.2 Build 4585 (June 17 2010. 16:05:08)
23668_MSXIPKernel_SYS_QVGA_WQVGA_HVGA_VGA_WVGA_0409.7z (38.98 MB)
http://www.multiupload.com/BRBSUQU4QD
http://multi-up.com/299136
Re-uploaded by Alexx~
Click to expand...
Click to collapse
Wow! Tried it and seems sooooo faster respect to 23667. My I8000 has increased performances as never before. Now SPB MS carousel is really responsive!
I noticed a lot of changes between 23667 and 23668. Any idea?
And, what about Metadata folder. Up to now I never found it inside a package, but now I did.
fubo73 said:
And, what about Metadata folder. Up to now I never found it inside a package, but now I did.
Click to expand...
Click to collapse
Metadata package is the all the registry entries, gathered together into one place.
utak3r said:
Metadata package is the all the registry entries, gathered together into one place.
Click to expand...
Click to collapse
Are you saying it is built during cooking? If not, why I did not find it in packages so often?
utak3r said:
Metadata package is the all the registry entries, gathered together into one place.
Click to expand...
Click to collapse
user and default.hv in metadata are useless because registry should be created from rgu and provxml while cooking.
The important part of metadata are packages.cif and .sof - they define the order and amount of packages cooked into the rom.
That's why I created my own Metadata with necessary packages list and always use it.
AndrewSh said:
user and default.hv in metadata are useless because registry should be created from rgu and provxml while cooking.
The important part of metadata are packages.cif and .sof - they define the order and amount of packages cooked into the rom.
That's why I created my own Metadata with necessary packages list and always use it.
Click to expand...
Click to collapse
can you please tell us how to edit/adjust packages.cif/packages.sof?
HD2Owner, I already posted that some time ago but no-one cares....
Utility by Barin (asusmobile.ru)
AndrewSh said:
HD2Owner, I already posted that some time ago but no-one cares....
Utility by Barin (asusmobile.ru)
Click to expand...
Click to collapse
thanks alot. is there a english version of this tool available?
HD2Owner, English version is a part of Barin's OSBuilder (which I use as a rom kitchen)
The English discussion and public downloadable release is here
Mmmm interesting I heard itbefore an effectively from you Andrew lets make it important here cause neither me use it... Thanks a lot
Just to make it more understandable - screenshots from packages cif and sof editor from OSBuilder tool
Barin is now on vacation and I have no contact with it, but I hope he will forgive me.
I translated pSofCifBuilder to English.
But IMHO, it's a naughtiness, the best choice would be to use OSBuilder.
Good luck
Alexx~ said:
But IMHO, it's a naughtiness, the best choice would be to use OSBuilder.
Good luck
Click to expand...
Click to collapse
Yea I am starting to like that OSBuilder now...
AndrewSh said:
user and default.hv in metadata are useless because registry should be created from rgu and provxml while cooking.
The important part of metadata are packages.cif and .sof - they define the order and amount of packages cooked into the rom.
That's why I created my own Metadata with necessary packages list and always use it.
Click to expand...
Click to collapse
what if we don't modify packages.sof and cif? i've never ever modified them and i dont think that ever caused a problem to me.
!Aman! said:
what if we don't modify packages.sof and cif? i've never ever modified them and i dont think that ever caused a problem to me.
Click to expand...
Click to collapse
I don't think that anyone has until now, and it doesn't seem to have mattered much, has it? Does the operating system even read either of those files? It seems like they're there for book-keeping, but I could certainly be wrong. There's not much point in modifying them with EVK since most EXT's don't have dsm's, and they get thrown out during cooking, anyway.
!Aman! said:
what if we don't modify packages.sof and cif? i've never ever modified them and i dont think that ever caused a problem to me.
Click to expand...
Click to collapse
Farmer Ted said:
I don't think that anyone has until now, and it doesn't seem to have mattered much, has it? Does the operating system even read either of those files? It seems like they're there for book-keeping, but I could certainly be wrong. There's not much point in modifying them with EVK since most EXT's don't have dsm's, and they get thrown out during cooking, anyway.
Click to expand...
Click to collapse
If you use PRB-based kitchen then it doesn't matter. When you use OSBuilder it DOES matter. Don't know whether even older kitchen like Build OS cares or not.
cnzqy1 said:
If you use PRB-based kitchen then it doesn't matter. When you use OSBuilder it DOES matter. Don't know whether even older kitchen like Build OS cares or not.
Click to expand...
Click to collapse
as i said i never ever modified them, that means it doesnt even matter with Build OS. moreover, using "all packages to one" technique strips most of the info from these files without even affecting the ROM.
In this order, which is specified in packages.sof will be building registry. It is not related to PRB, or OSB, or any other kitchen.
Building registry does rgucomp (default.hv, user.hv and boot.hv) on the list of packages (dsm) from packages.sof
It has always been, regardless of whether old or new kitchen. So no other way.
Further deletion of files dsm ("all packages to one", etc.), nothing to do with the building registry.
P.S. There is a myth that OSB is important packages.sof, and at for other kitchens, it is not needed. This is nonsense. In OSB can view and edit packages.sof and packages.cif. That's all the difference.
well, my point is just that registry is added into the hives even if package has not been mentioned in packages.sof, so why bother editing it?
It is important that packets from the SYS and from OEM (which can be attributed to the group OEMDrivers) were formed in the order of packages.sof. The rest you can adjust with the names (dsm or package, depending on the kitchen).
If you think that the roster of SYS formed not so - you are mistaken.
As an example, you might see messages about the problem of "blank page" in IE.
trust me, i've never modified that file. i always use it without editing, from whichever source i get it. i'm not saying it is useless, but in most cases we don't need to edit this file
Hey everybody,
I'm cooking a WM6.5.x ROM for HTC Touch Pro / Fuze / Raphael (you call it how you like it). I'm using WM build 23699. Everything is fine, that's no problem But I have a question related to the kernel. I have not updated the kernel, so I only have slot 0 and 1. But are there much advances on updating my kernel to the 'native' one? And where can I find it? And how should I do it?
Thanks in advance!
MadMatt
The advantage to have a native 6.5 Kernel is that you will have a more smooth rom because you will not need to recmode any module thrn the standard for having a booting rom (Ntconfig.dll).
I dont know if it does exist for your phone but you must search for it in its thread,you need to search for Nk.exe.Once you will find it just replace it with the old one in OEMXIPKernel.
af974 said:
The advantage to have a native 6.5 Kernel is that you will have a more smooth rom because you will not need to recmode any module thrn the standard for having a booting rom (Ntconfig.dll).
I dont know if it does exist for your phone but you must search for it in its thread,you need to search for Nk.exe.Once you will find it just replace it with the old one in OEMXIPKernel.
Click to expand...
Click to collapse
The NK.exe is the only thing you need? And is it possible that it is the same as the one from the HTC Diamond? (as the only difference between those two is the keyboard)
Yes ,only nk.exe you need and i doubt that Nk.exe from another device should works.
_Madmatt said:
The NK.exe is the only thing you need? And is it possible that it is the same as the one from the HTC Diamond? (as the only difference between those two is the keyboard)
Click to expand...
Click to collapse
af974 said:
Yes ,only nk.exe you need and i doubt that Nk.exe from another device should works.
Click to expand...
Click to collapse
Okay, I'll search for the NK.exe. And OsKitchen will automatically detect that it is a newer kernel than?
If you will replace the old kernel then OsKitchen will does all the process automatically.
_Madmatt said:
Okay, I'll search for the NK.exe. And OsKitchen will automatically detect that it is a newer kernel than?
Click to expand...
Click to collapse
Good lord, update the kernel!!! There's one posted in the native kernel thread.
Here's the one I've been using. I think it's the latest. Just swap it into your xip folder and you'll be good to go. And quit recmodding!!!
Farmer Ted said:
Good lord, update the kernel!!! There's one posted in the native kernel thread.
Here's the one I've been using. I think it's the latest. Just swap it into your xip folder and you'll be good to go. And quit recmodding!!!
Click to expand...
Click to collapse
Thanks, will I need to update OEMDrivers too? Because I read that sometimes that is needed too And will I be able to un-RecMod everything after updating the kernel?
Look for one of Da_G's kitchens (23016 was the last full one). It has the oem. But the drivers are all the same. I use drivers from the Orange/20779 final raphael rom. Convert all the drivers to modules.
Farmer Ted said:
Look for one of Da_G's kitchens (23016 was the last full one). It has the oem. But the drivers are all the same. I use drivers from the Orange/20779 final raphael rom. Convert all the drivers to modules.
Click to expand...
Click to collapse
Didn't understand what you are saying here So I need all the OEM packages execpt the OEMDrivers? The OEM packages I have right now are those from the RUU_Raphael_HTC_WWE_5.05.405.1_R_Radio_Signed_Raphael_52.58.25.30_1.11.25.01_Ship.exe
Are that good ones too? Convert all drivers to modules? What do you mean by this? Convert the OEMDrivers in the OEM tab to EXT packages? (Using osKitchen)
Sorry, all you need is the 20779 or 20771 oem. But if you don't want to dump it yourself, get Da_G's kitchen, which is cleaned up a bit. The drivers aren't 6.5-specific. You should convert them all to modules, though.
Farmer Ted said:
Sorry, all you need is the 20779 or 20771 oem. But if you don't want to dump it yourself, get Da_G's kitchen, which is cleaned up a bit. The drivers aren't 6.5-specific. You should convert them all to modules, though.
Click to expand...
Click to collapse
Allright, if the drivers aren't 6.5 specific, then I can just convert my drivers I have now to EXT-packages?
_Madmatt said:
Allright, if the drivers aren't 6.5 specific, then I can just convert my drivers I have now to EXT-packages?
Click to expand...
Click to collapse
Why convert them to EXT's? Just leave them in your OEM Drivers folder. And convert them to modules.
Farmer Ted said:
Why convert them to EXT's? Just leave them in your OEM Drivers folder. And convert them to modules.
Click to expand...
Click to collapse
Okay. and how do I do that in osKitchen? This is my first kernel update
I don't use that kitchen, but if it doesn't have module creation built-in, get reversemod.exe and manually do the conversion by dragging and dropping the files onto the exe. You should do all the oem driver dll's (they get loaded at startup, anyway, and this will save some virtual memory).