![]() |
|
|
|
#1
|
|||
|
|||
|
I've just checked, and you will find
"Compuware.Softice.4.3.1.Lite_uploaded_by_deadalien" in the /pub/[Cracking]/[NuMega]/ folder. Bad searching, Bad. Regards,
__________________
JMI |
|
#2
|
|||
|
|||
|
Hi,
I;m not a "Softice version" fanatic for "Lite" releases Can anyone tell me which Softice versions correspond to Driver Studio 3.0, 3.1 and the new 3.2?Thanks. |
|
#3
|
|||
|
|||
|
Isnt that switch related to non execute memory protection (included in AMD64) that XP-SP2 makes use of it?
I just played with boot.ini and put the /PAE option. Its true, SICE resets my computer...without /PAE works great ![]() Good observation, maybe Compuware didnt make that PAE test
|
|
#4
|
|||
|
|||
|
hxxp://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2mempr.mspx
It turns on to allow for the use of DEP if you have a processor that supports the function. Quote:
PAE still active |
|
#5
|
|||
|
|||
|
Kennus, can you show me your boot.ini
|
|
#6
|
|||
|
|||
|
Code:
[boot loader] timeout=15 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /noguiboot /NoExecute=AlwaysOff /noPae multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Windows XP Professional x64 Edition" /fastdetect /noguiboot Go figure why it doesn't turn off
|
|
#7
|
|||
|
|||
|
Maybe you have BIOS settings for this problem. I once worked with a 8x Xeon MP computer with 16 GB RAM installed and its BIOS contained a setting like (I don't remember the exact words): "enable memory hole above 4G". When you enabled it, Windows wasn't able to detect more than 4 GB of RAM. Although I don't know if this had an effect on the PAE settings.
|
|
#8
|
|||
|
|||
|
Kennus, it seams to be all right with your boot.ini
I have no idea :-( I think, it is time to switch to DS3.2 ;-) |
|
#9
|
|||
|
|||
|
Hello,
Has anyone managed to debug with Visual Sofice with DS3.2? I use as target Win64XP with AMD64 but as soon as I start remote debugging , Visual sofitce stays infinitelly retrieving the target information and of course, the target is totally hang. With DS3.1 this problem does not happen (though the problem I have with DS3.1 is context switching everytime that I trace a single instruction). Anyone has managed to use Visual softice with success in this environment? Thanks |
|
#10
|
|||
|
|||
|
Thanks for the idea Kerlingen but that would only be applicable with more then 4 GBs of RAM (and I tried it anyway)
which I don't have (wish I did though!). Finally got ahold of DS 3.2 and it works perfectly
|
|
#11
|
|||
|
|||
|
Hi
I would like to ear some opinions about new version DriverStudio 3.2 I don't have 64bits processor but I have some troubles with DriverStudio 3.1 and older. tia ramon |
|
#12
|
|||
|
|||
|
Then read this thread:
http://www.exetools.com/forum/showthread.php?t=6914 and Search for DS 3.1 to find discussions of issues with DS 3.1 in other threads. Don't ask for a repeat here. Regards,
__________________
JMI |
![]() |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| DriverStudio | Git | General Discussion | 0 | 04-13-2009 18:58 |
| Driverstudio 3.x and amd 64 | runet | General Discussion | 5 | 04-17-2005 00:12 |
| DriverStudio 3.1 & W2K | assembler | General Discussion | 9 | 03-30-2004 13:44 |