DIY eGPU experiences

[User Retired 2]

Ok, everytime i tried to allocate resources, i will boot the bootdisk and select the ViDock Setup(win menu)....then I tried pressing "apply config using startup.bat", after i set up the chainloader, port and compaction but it gives me "Abort,Retry,Fail", is it meant to be like that?
i end up using the "apply config using chainload" option everytime...

I think you are having the same problem I was having with the ICH8M 2510P. Namely, USB 2.0 speed is causing an issue with your USB pendrive writes. This will not be evident when using the Menu-based setup since it runs from ramdisk. The solution then is:

1. See if the bios has a USB 1.1 only mode and enable it if it does.

2. OR use notepad to edit \core\startup.bat. Add the following lines. The ramdisk operation means then will only ever do the initial *read* from the USB drive. All other operations needed will then be done from ramdisk. The 'call waitvid' line is optional.

call ramdisk
call iport x2 5
call waitvid 60 1002:68be
call pci.bat
call grub4dos mbr

I could see how this usb 2.0 write issue could frustrate someone for 3+hrs. I did not have the problem with ICH7M or ICH9M systems so it might be ICH8M-centric??

After rebooting my computer I no longer get the error 12 message. I am once again losing all of my USB ports after about an hour of gaming. It has been suggested that there may be some communication issues going on between the lappy and video card, but I don't know. Also, I have upgraded to Windows 7 since my original post, but still having the same issue, so I guess it's back to the drawing board

I would advise getting the DIY ViDock Setup 1.x working and use it to do as minimal PCI space compaction as you can get away with. Eg: Selective compaction, choose vid_* rather than "ALL". I found that Win7 does it's own PCI Reallocation with side effects like lost mice/usb ports which don't occur if using the Setup 1.x.

[villiankknd]

call pci.bat

so do i type pci.bat or just pci?

thanks alot nando4, i hope this works....my 5750 gave me a grey screen(maybe cos of the overclock) and the restart failed again, .....so i think i am going to fix this, will post if there is any problem after i tried this....

if i remove this "call waitvid 60 1002:68be", does this mean i can restart my computer with vidock plugged in?

[clmerlin]

[QUOTE=nando4
I would advise getting the DIY ViDock Setup 1.x working and use it to do as minimal PCI space compaction as you can get away with. Eg: Selective compaction, choose vid_* rather than "ALL". I found that Win7 does it's own PCI Reallocation with side effects like lost mice/usb ports which don't occur if using the Setup 1.x.[/QUOTE]

Ok so this is where I got lost last time I think, when I go into DOS to the \devcon\i386 and typ in 'devcon resources ACPI\PNP* > \core\devcon.txt i get an error message saying "The system could not find the path specified."

[User Retired 2]

so do i type pci.bat or just pci?

if i remove this "call waitvid 60 1002:68be", does this mean i can restart my computer with vidock plugged in?

'call pci.bat' and 'call pci' do the same thing.

Your DIY ViDock will work with 100% success rate if you pass bios with it switched off. If your bios boots up OK with it switched on, then do another compaction and test again in which case it should work so long as you do a 'ALL' devices compaction.

Ok so this is where I got lost last time I think, when I go into DOS to the \devcon\i386 and typ in 'devcon resources ACPI\PNP* > \core\devcon.txt i get an error message saying "The system could not find the path specified."

Yes. That is what will happen if you haven't copied the files across to the USB drive successfuly. Can do a quick check in Explorer to see if you have these directories on your USB disk: \bin, \core, \devcon, \dos, \help, \setup. If these don't exist then follow the Setup installation instructions carefully, perhaps asking a friend/colleague for assistance if you get stuck.

[clmerlin]

Yes. That is what will happen if you haven't copied the files across to the USB drive successfuly. Can do a quick check in Explorer to see if you have these directories on your USB disk: \bin, \core, \devcon, \dos, \help, \setup. If these don't exist then follow the Setup installation instructions carefully, perhaps asking a friend/colleague for assistance if you get stuck.

Thanks Nando, I figured out what I did wrong. I just copied the DIYVDock folder over rather than the contents only, oops Now I'm going to continue and see if I can get this setup properly. Thank you very much for the help.

[villiankknd]

oh ya one last question...which startup.bat should i edit?

the one in c: or the one in my usb drive?

thanks.

lol i think this is a stupid question, i think should be the one in usb....

should i delete the "REM" words in front of "call"?

[User Retired 2]

lol i think this is a stupid question, i think should be the one in usb....

should i delete the "REM" words in front of "call"?

Edit [USB drive]:\core\startup.bat

Lines started with REM are a remark. The line is ignored. The existing startup.bat will have a number REM lines showing examples of what you may want to use. Delete the REM if you want to use the line.

[villiankknd]

thanks, thats what i thought, ah well failing my programming course was a bad idea lol...

anyways i will try to turn my vidock off and restart it and see what happens...

Update: failed again... I turned off my vidock while restarting was in progress.. then when the asus splash screen comes out and disappear, bootdisk menu appear and I turned on my vidock and select automated startup... and I get the ducking black screen again:...

[jam7000]

Great tutorial, hoping to get this to work on my lenovo T61 laptop. 3GB ram, core2 duo 2.2 ghz. I have a PE4H with an ATI HD5670 1GB hooked up. I have the bootable usb drive working and everything. (I used the instructions on page 64).

and in this screen Imageshack - pciconfig.png i have three "yes"s everything running at 1x (I had to use ignore on the integrated graphics and compactor on all option).

But Using orig. and beta chainloaders my xp freezes during the blue loading bar. (This same thing happens if I try to use the PE4H without the bootable disk.) Any idea what my issue is, or what work around I can try?? If you need more info. please ask, as I really would like to get this working.

[jam7000]

No error messages by the way. Unless I use the beta loader, then I get a blue screen.