setting device to load on startup

[arsunist]

So I've installed the older version of the camera drivers in order to fix a camera issue I'm getting with the 7201 CPU. Right now, I need to manually go into the task manager -> Devices -> start CIF1.DLL every time my phone is restarted, otherwise the camera won't initialize.

Short of cooking the old camera version into the rom, is there a way I can get the camera to load automatically?

[overhaulengines]

did you install this using a cab? what camera cab did you use? did you just flash a new rom? if so, might be your radio

Lupe

[thesire]

did you install this using a cab? what camera cab did you use? did you just flash a new rom? if so, might be your radio

Lupe

radio can't be issue because camera does work; he doesn't want to manually load the file for the camera every time he restarts his kaiser.

I never had this issue of having to start the camera manually. On xda live 3.0 the camera application is taken out but installation via cab makes it work without problem ...
search for "kyphur xda live 3.0"; that should bring up the thread for that rom. In the thread download the file that kyphur has on his 4shared account which includes things he removed from rom. In that zip file there are two different files for camera.

Try that and see what results you yield.

[johnk1973]

Can't you just put CIF1.DLL in to Windows/startup folder?

[arsunist]

Thanks for the replies. I realized I should have been a bit clearer.

Ok, so I went back and looked at what I was loading and the file is called SJ CIF_314.CAB It's not the camera, but a device or driver that the camera uses. If I install this cab, but don't manually load it in the taskmanager, the camera won't initialize.

I'm loading this cab to address an issue my camera has when recording video (has to do with the 7201 CPU). You can read the details of this solution here:
http://forum.xda-developers.com/showthread.php?t=387057

Basically, because of my CPU, any of the roms cooked with the TYTNII PhotoQuality.cab fix seems to cause recording problems on my video camera. So to fix this, i need to install the SJ CIF_314.CAB.

So there is no issue with the camera after this device driver is loaded. But I need to load it manually each time my phone is reset.

When I go into task manager to find the device in the devices list, it is listed as $device\CIF1(CIF1:) and it is unloaded. I just have to highlight and start it to get my camera working each time. In the registry it is linked to the file CIF.DLL

I'm basically asking if there is a way to get this device to load automatically like most of the other devices in the devices list. Like maybe changing or adding something in the registry?

[arsunist]

so anyone know how to do this?

[Gellenole]

anyone have a resolution for this? I want to see this resolved as well heh

[mart-xda]

i have the same problem - anyone figured out how to fix this so the driver loads automatically on startup?

[austinsnyc]

what i find strange is (i dont mean anything mean by this) it seems like Junior members are the only one with this issue. these days cooking a rom is simple with the kitchens out there i would just cook the drivers in and be done with it. also seems like that .cab might be messed up a little if its not over writting the "newer" driver no?

also all the wm6.1 roms have camera fix built in before the cooks touch it so its not like we are doing this on purpose sorry :D

[mart-xda]

yes it certainly looks suspicious that this happens only to junior members.

but, i had this problem after i loaded dutty's wm 6.1 rom, messed around for a day looking for the best radio rom (had issues like carrier signal dropping and coming back every 5 seconds, black screen camera and video camera).

i am not yet at the stage that i want to cook my own rom, so this issue is not a result of a junior member's rom, but rather playing with other roms which seem to be highly recognized in this community, and other strange behavior (ie locking up the device - found a fix for that today as well).

having said all that, do you know how to override boot settings so a driver is automatically started after every reset?