Post by: Xbox-Scene on March 02, 2010, 04:11:00 PM
Run Jungle Flasher Win7 x64 With Perm Disabled Driver Signing No More F8 Posted by XanTium | March 2 18:11 EST | News Category: Xbox360 |
| From team-xecuter.com: Quote As you may (or may not) know, the new 64bit compatible Jungle Flasher requires you to disable the Windows 7 driver signing policy by hitting F8 every time you boot up as the 64 bit PortIO driver isn't digitally signed. Full Story: team-xecuter.com |
Post by: skyliner99 on March 02, 2010, 04:16:00 PM
Post by: Its_me_again on March 02, 2010, 04:23:00 PM
Post by: telo{+} on March 02, 2010, 04:25:00 PM
QUOTE(Its_me_again @ Mar 3 2010, 12:23 AM) 
I don't have to press F8 at bootup since the day JungleFlasher supports Win 7 x64, I just signed PortIO with DSEO.
No No. Far too easy. Do what the "experts" tell you to do.
I mean, patching ntoskrnl.exe & winload.exe.... What could go wrong!? (IMG:style_emoticons/default/sad.gif)
Post by: Silv on March 02, 2010, 04:27:00 PM
You can obtain it or find out more about it here:
http://www.ngohq.com/home.php?page=dseo
EDIT: Its_me_again with first mention of it, so there you have it!
This post has been edited by Silv: Mar 3 2010, 12:28 AM
Post by: alwaysonjohn on March 02, 2010, 04:37:00 PM
Post by: jester on March 02, 2010, 05:59:00 PM
Should add this to the main post:
http://fyyre.ivory-tower.de/projects/bootloader.txt
QUOTE(telo{+} @ Mar 2 2010, 06:25 PM)
No No. Far too easy. Do what the "experts" tell you to do.
I mean, patching ntoskrnl.exe & winload.exe.... What could go wrong!? (IMG:style_emoticons/default/sad.gif)
QUOTE(Silv @ Mar 2 2010, 06:27 PM)
Seems a little ridiculous to me.. I'd rather use Driger Signature Enforcement Overrider which is a simple boot flag, rather than modifying core OS files such as NTOSKRNL and WINLOAD, which could get updated by MS with a patch...
You can obtain it or find out more about it here:
http://www.ngohq.com/home.php?page=dseo
EDIT: Its_me_again with first mention of it, so there you have it!
If you read into it, you would see it simply makes copies of these files.
QUOTE
save modified ntoskrnl.exe with a different name (i.e. ntkrnlmp.exe)
Save as winload.exe as osloader.exe (or whatever..)
Save as winload.exe as osloader.exe (or whatever..)
Post by: nickcas on March 02, 2010, 08:03:00 PM
Good way to make use of his patch though.
Post by: m82a1 on March 02, 2010, 08:29:00 PM
This post has been edited by m82a1: Mar 3 2010, 04:30 AM
Post by: Paperstack.1 on March 02, 2010, 08:35:00 PM
QUOTE(alwaysonjohn @ Mar 2 2010, 05:37 PM)
Only downfall is leaving windows 7 in test mode is annoying due to the watermark.
There's an option to download a watermark remover in there for both x86 & x64 (IMG:style_emoticons/default/wink.gif)
The real drawback to it is when you use DSEO, the watermark comes back after a while plus for some reason my PC randomly brings it out of Test Mode. (IMG:style_emoticons/default/blink.gif)
I'll give this a try now. Hopefully it will keep my PC in test mode (IMG:style_emoticons/default/smile.gif)
EDIT: Just applied this patch and it seems to be working ok with unsigned drivers, but now the boot screen is the Vista bar scroll and not the Windows 7 screen, plus it takes a bit longer for my PC to show the login screen.
This post has been edited by Paperstack.1: Mar 3 2010, 04:44 AM
Post by: EvanVanVan on March 03, 2010, 05:51:00 AM
Post by: ccfman2004 on March 03, 2010, 07:56:00 AM
Also, I can't find the "osloader.exe" when I use 2.exe.
Post by: xboxmods2977 on March 03, 2010, 03:02:00 PM
I have not experienced any of the above mentioned symptoms with it, (reappearing watermark, random test mode failures) altho sometimes I have to open/close/re-open PG2 a few times to get it to start the GUI.
I am however interested in this other method if it fixes the problem I have with PG2. Anyone know?
This post has been edited by xboxmods2977: Mar 3 2010, 11:03 PM
Post by: ccfman2004 on March 03, 2010, 06:50:00 PM
QUOTE(ccfman2004 @ Mar 3 2010, 03:56 PM)
Does this work for Multi-Core systems since it uses a different loader?
Also, I can't find the "osloader.exe" when I use 2.exe.
I found the problem. Apparently your account username cannot have any spaces in it. Once I created an account with one word, it worked fine. This is good to know for any user having issues with 2.exe not finding the osload.exe file.
Post by: jimbo70 on March 04, 2010, 05:34:00 PM
QUOTE(xboxmods2977 @ Mar 3 2010, 05:02 PM)
I am however interested in this other method if it fixes the problem I have with PG2. Anyone know?
Try Peerblock, basically same as peer guardian except it works flawlessly under Win7 64bit. I've been using it ever since they got signed driver for it.