quick question re : PortIo, new firmware, and BenQ

Midnight Tboy

Inactive User
Joined
Feb 23, 2008
Messages
851
Reaction score
7
Ola

I'm going to do my bosses xbox tomorrow at work, as his old one red ringed and he's just been given his repair (good tho as the drive was already nigh on dead and had to pot tweak it).

He said the wires in the keyhole are "white" so I suspect it is the BenQ.

The last few machines I modded where Liteons, and in order to do these with my Via sata pci card, I installed the PortIO drivers as recommended.

I'm just wondering however, do I need to reinstall the regular drivers again when doing a benq, or will the PortIO drivers work fine for all drives, as I'm sure I read eons back about some drive types giving problems when using PortIO??

cheers,
T
 
cheers.....just wanted to be sure :D

Being the boss and 'all, and doing it at work this time round, he'll no doubt be looking over my shoulder so wanted to be sure :)

Makes me wish it was a Liteon so it looked a bit more "technical" using the probe :D

Just going to make sure I have the latest JF now
 
cheers mate,

it flashed no bother at work - and no surprises was watched over my shoulder while doing it :D

Now another workmate though is bringing over his 360 tomorrow, and its definately a Hitachi drive (unsure of version til open it tmw).

Would I be right in thinking that its generally recommended to remove PortIO and go back to regular via drivers when doing the Hitachi as less prone to problems?

Ruddy hate Hitachis!!
 
I use PortIO for Hitachi`s too.


Works perfect for me, in fact as i only use my Via card for flashing i never have the Via drivers installed.
 
cheers fellas,

another quickie.....whats the score now then with ModeB?

I in the past with JF before using PortIO on my first Liteon, also used SlaxCD to go to modeB. I now have a Maximus connectivity kit, which as far as I know is meant to auto put the drive to modeB, but I read this in the latest JF guide

Once it inquires, Click send ModeB, you will be presented with the following message, its advised you do as it states as the ModeB button on Connectivity Kit, can cause issues

so what are these issues? The guide basically goes through the motions of WinAPI instead of PortIO too, but presume I should still press the Send Mode B commands? I love the guide and all that but the hitachi section is a little confusing lol :) I take it I'll also still need the 79 unlock cd if it turns out its a 79 too
 
The maximus kits auto modeb is a pita.
 
bugger....

in that case is there any way to disable it? In past I used to just always use the 360 to power the drive. I suppose I could still do that I guess if needs be?

Can I still use the slaxCD then or what is best when using the maximus to get around whatever this modeB/maximus problem is? lol and I thought I'd be giving myself an easier time with these kits!!
 
Try it, only 1-2 of the team had one and it caused issues.
 
The issues lie around modeb.

You could have just the 360 in the time you've been debating ;)
 
I have the maximus and its fine with the hitachi, just use JF to put into mode b m8, works fine
 
drive flased fine anyways

this morning I decided to remove PortIO drivers to be on safe side.

I then used the maximus to power etc, drive was showing in windows but port info etc was blank on JF.

I then reverted to 360 power and slaxCD but it was still showing blank. In the top right column the drive was listed however

So not matching the way the guide is, and had rebooted a few times to try to get the port window in left to show the gdr info

Drive was responding etc anyway so tried to read the keys - all fine, so went ahead and flashed no problem.......so I suspect that the maximus had also put it to modeb no bother too (just I was threw off by the JF app not giving the info on left column (where the send modeb command is)
 
You removed PortIO drivers and wonder why it didnt appear on the port.

Are you serious?

Removing PortIO would not have gave you any benefit at all, as you used WinAPI
 
well I do like to go a long way around doing things :)

I removed portIO seeing as I'd heard of problems with it and hitachis so thought better safe than sorry.

And in the guide, page 44 (which uses Winapi instead of PortIO), those Port Properties info are populated in the pictures which suggests that it should have given that info for me in winapi too. It was the fact that it gave no info at all in port properties while using PortIO the first try (while still using maximus), that made me decide to try removing PortIO...but then with WinAPI it still gave same result of empty properties on left side......so in nutshell neither method worked to give that info :)

On a tangent the last Hitachi I did ages back with an earlier version of JF (and before I put PortIO on for first time) did definately populate those fields

oh lol...and I'd guessed at time too that to use WinAPI I'd have to uninstall PortIO anyways.....thinking that had to have correct via drivers installed again instead
 
Back
Top