![]() |
|
|
|
#1
|
|||
|
|||
|
just a hunch...
make sure you've unloaded the previous instance of ramdisk.sys before starting up the new one. windows may be preventing the loading of another ramdisk.sys because one is already in place. |
|
#2
|
|||
|
|||
|
Yes, i stop the service, after i load it in winhex and i change a char and save it, i restart the service and the service doesnt start anymore...
![]() Stop again the service, undo in winhex and save it, i restart the service and it works! I've try it with differents xp machines... DaGoN Last edited by DaGoN; 06-24-2004 at 04:12. |
|
#3
|
|||
|
|||
|
fixed checksum already?
|
|
#4
|
|||
|
|||
|
Quote:
I havent found nothing about it. Thx, DaGoN |
|
#5
|
|||
|
|||
|
Hi,
Use LordPE to recalculate the CheckSum. |
|
#6
|
|||
|
|||
|
LordPe reduce the file size and optimize it but the result is always the same: It doesnt work.
Lordpe result: Validate Pe image... done. Try it, its strange, seem that there is a check from the system before driver start. ![]() my test bc * bpx IoAllocateDriverObjectExtension start service softice break bpx @esp (bpx on caller) bd 00 x sofice break here: Quote:
bc * bpx IoAllocateDriverObjectExtension i restart the service softice doesnt break anymore DaGoN |
|
#7
|
|||
|
|||
|
Hi,
You are using Rebuild PE. I'm said to you to recalculate the Checksum. Open LordPE hit "PE Editor", choose the sys file, locate the checksum and you will see a "?" on the right hand side just hit it and then hit "Save". ALiAli |
![]() |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Driver patching / filter driver | aldente | General Discussion | 4 | 03-21-2006 04:43 |