Hiya

i am having a problem with Softice 4.05 and whenever i bring up the SI Window by "CTRl+D", My OS crashes and i can see where it does that.

Softice gets hold of CONFIGMG_SET_BUS_INFO.

SO i tried to look for configmg.vxd and when i went to Windows Systems, i looked under the System Boards Drivers and found out that configmg.vxd which is a part of VMM32.vxd. Is missing!!!

I know that this is an old problem with Windows98 SE, as along with configmg.vxd other files too get deleted or corrupted.
e.g. ntkern.vxd,vcomm.vxd,vdd.vxd etc.

i did install the required files again from Windows CAB files. But when i CTRL+D again, the same problem arose.
I did unistall Windows and install it back again. But the problem is still there.

Futhermore, i am using SI for about 1 month and there have been no problem with that but recently i installed Windows XP and Driver Studio 2.6. And i had both the OS on the same HardDisk but different Drives.

Does anyone know how to fix this problem.
Do i have to format both my drives.?

Thanx

It appears from your description that your original OS is either a version of NT or Win2000. It would be easier to attempt to help if you were more specific about what OS you are running before you installed XP. I have seen some discussion indicating that when one is running a dual boot system that the Win2K system should be installed last, to avoid some of the essential files from being replaced by the other OS.

I've recently started a switch to Win2K from Win98se and have the "old" OS installed on a separate hard drive and I do remember reading some material from the M$ site discussing which OS systems can be loaded on a dual boot system. Since I don't run XP, I didn't pay too much attention to the discussion of whether they recommend such a combination, but there are definately articles in the M$ Knowledge Base dealing with the compatability of various OS systems on the same machine. I'd recommend you start there first and I''ll also check the articles I downloaded and see if they address this issue.

If you search this board you will also find a great deal of discussion about the perils of attempting to run Sice with WinXP. Some people are having no serious problems with DS 2.6 and many can't get it to work at all, which suggests hardware/driver related problems. We know that Numega hasn't gotten their act together fully with integrating Sice with XP yet.

Regards.

HIya JMI

i had written that i m Using Windows 98 SE and then laterz i installed Win XP.

The problem is that i have been using Softice for anout 1 month and there hasnt been a single problem.First i was using SI 4.05 and then laterz changed to DS 2.5 and than at last i came to DS 2.6. Every version i installed was working perfectly on Windows 98 SE, but i tried it with WInXP and i went ahead and installed DS 2.6. Though it didnt work as it had problems with my VGA Card as i hadnt installed it in XP, though i was just checking it out in XP as i dont use XP much. It was only for Oracle as it doesnt work in WIn 98SE.

If the problem was to be with Dual OS, then i have removed WIn XP though manually.


Thanx for ur reply

Howdy,

I am not sure what your problem is... I am dual booting as well, only have win2k and winXP though so both of them are NTFS... my win2k has sice and XP doesnt.. one thing i am sure of, XP isnt very well supported by sice yet...

It might be some problem with your partition file format, NTFS and FAT32 on the same drive, how you set them up to boot... as in if you have win98 + sice... then you install win XP to boot from the same primary partition again, even though your winNT folder is on another partition... this might mess it up...

If this is the case, before you install winXP, go to BIOS and change the primary partition to the blank partition where you wish to install winXP, so that the installation will not touch your win98 partition at all... then get some boot manager to organise your boot up process... just asuggestion.. i am not sure how you actually dual boot....

Regards,
crUsAdEr

Hiya

i have already posted that i have removed WINXP and im using Windows 98 SE ONLY!!!.

But the problem with SI still remains, it craches at CONFIGMG_SET_BUS_INFO

and when i restart my comp, my configmg.vxd gets deleted along with other vxd's, so i have to copy the vxd's from WIN98 SE CAB files.

Thanx

Hmm,

so you did boot XP on the same partition... guess clean install will have to do then...

You might want to try to "upgrade" your win98, as in install win98 again on top of the current win98 version right now, hopefully it fixes up the system files and everything, but sometimes it doesnt (or most of the time actually:<... if it doesnt work guess you will have to clean install everything cos my guess is that remnant of winXP sys file still lie ard in ur HD...

Hiya Crusader

At first when the procedure of installing WIn XP, my Motherboard gave me a warning signal that a program is trying to "WRITE TO BOOT" and that file was of WIN XP and was named as WINNT somethin like that but sure did contain NT part.
And i granted the permission as without it it would let WIN XP install.

And when the problem arose, i did install Win98 SE over my previous one but that didnt help either. Then i went and removed Win XP manually. And that didnt also help. So furthermore i went and FORMATTE both my drives which contained WIN 98SE and the one which use to contain Win XP.

And reinstalled WIN 98 SE from scratch. BUt then when that didnt help either. I think the file which was written to the BOOT sector is causing the problem.


When the last time i Brought up SI, it crashed at this address.


CONFIG_SET_BUS_INFO
0028:FF02E37A MOV EAX,[FF033628]
0028:FF02E37F CMP EAX,[FF033088]
0028:FF02E380 JBE FF02E38F

and the line that gets highlighted is the CMP eax,[bla bla] one.

And i know that

CONFIGMG.VXD (configuration manager for the motherboard)


Thanx

Ajnabi:

I still recommend that you check out the M$ Knowledge Base for articles on a dual boot system.

You will find several articles at:

hxxp://search.microsoft.com/default.asp?IntCat=0&Boolean=ALL&Nq=new&qu=dual+boot&ig=1&siteid=us/products/windows/windows2000.

There you will find articles such as:

How to Multiple Boot Windows XP, Windows 2000, Windows NT, Windows 95, Windows 98, Windows Me, and MS-DOS (Q217210)

and

HOW TO: Create a Multiple-Boot System in Windows XP (Q306559)

The second discusses a dual boot with Win98se and WinXP and explains, as you found, how WinXP overwrites the boot sector and has to be installed last to function properly. This article does suggest that when you reinstalled Win98se you should have fixed the boot sector problem, but you also stated that you did not "uninstall" WinXP, but "removed it." This could also be contributing to your problem. Win2K has an automatic repair function added which will restore damaged files without letting you know about the activity. Since WinXP is based upon the same kernel, perhaps it is "repairing" itself at boot and replacing files otherwise needed for your Win98se boot. Just a thought.
Did you install a NTFS partion for the WinXP partition, and if so, did you also re-format the Win98se partition for NTFS?

Also, I was not able to find a version of DS 2.6 for which I could get a working Icedump on Win98se, so I went back to 4.05, where it works fine. Unless you are a developer, it should work fine for most of what we do in RCE.

You may, in deed, need to reformat your hard disk and reinstall everything to get your motherboard to work again with Win98se and SI. Although you mentioned that you did format, you may have not done a complete format from a DOS boot disk and you might try reinstalling the system files to your boot sector on the start-up disk from your Win98se start-up disk.

Regards.

You could also try copying back mbr with
fdisk /mbr

Or best, use WinHex to see what ur boot sector looks like :>>....

Howdy,

If your running fat32 you need to delete the partitions
first, then format, then re-partition.
Dont ask me why, I dont feel like explaining it.

You can easily do this with fdisk.

Peace, Woodmann

HIya thanx ya all for replyin

Though i tried out copyin the Batch Files in this Manner. And it sure did help. As when i Press CTRL+D, my computer doesnt crash anymore but though in place of SI Window i just see plain BLACK Screen. I havent tweaked the settings of SI. And ill let u on when im done with it.
Here's the trick which works and i hope this will help other too.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Some of the steps only tell you what needs to be done and not how to do it. If you don't know how to do it, then I suggest that you should re-consider attempting this procedure. In this archive are samples of what the 2 batch files you are going to create should look like. As written they may not be appropriate for you system, so please follow the steps below to create batch files for your system, and use the samples only as a guide to what your completed batch files should look like. The entire procedure can be run from within the Win9X GUI, there is no need to start in Real Mode DOS as is the case with the earlier version of this procedure. Note that in my examples in some of the steps, I only show 3 entries for file lists that will be much larger (probably 40 or more lines). Also for these batch files you will be creating case does not matter.

1.First you must know what files are in your current vmm32.vxd file. You can get a list from the registry at HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Control \ VMM32Files. Since the list is rather long, and because this procedure involves creating a batch file using this list of file names, the easiest thing to do is export this key to VMM32.REG

2.Open VMM32.REG in any editor that you want. An editor with Search and Replace (abbreviated as S&R in this procedure) capability is best (thus NotePad will not do, but WordPad will). The steps in this procedure are written to take advantage of S&R. The editor you use must allow you to save the results to an ascii text file.

3.Delete the first few lines so that you are left with a list that looks something like the following:

"biosxlat.vxd"=hex:00

"combuff.vxd"=hex:00

"configmg.vxd"=hex:00

4.Save what you have so far as WININIT.INI which we use later in this procedure.

5.Now continuing editing VMM32.REG and using S&R enter "=hex:00 (Note the leading quote mark in this text) as the search string and leave the replace text blank and then do a Replace All. You should now have a list that looks something like:

"biosxlat.vxd

"combuff.vxd

"configmg.vxd

6.Now replace all occurrences of " (a single quote mark) with one of the following text strings:

extract /a /y H:\win95\win95_02.cab (for Win95 users)

or

extract /a /y H:\win98\base4.cab (for Win98 users)

Note: In the above commands you have to change H:\win95 or H:\win98 to the actual path that your Win9X cab files can be found at whether it be a CD directory or some HD directory. Also note that there needs to be a SPACE at the end of the replace string. When you have completed this step your file needs to look similar to:

extract /a /y H:\win98\base4.cab biosxlat.vxd

extract /a /y H:\win98\ base4.cab combuff.vxd

extract /a /y H:\win98\ base4.cab configmg.vxd

7.Now ADD the following 5 lines to the TOP of the file:

@echo off c:

cd \windows\system

extract /a /y H:\win98\ base4.cab vmm32.vxd

cd \windows\system\vmm32

The C: in the second line must be changed if you have Win9X installed on a different drive. Also if \Windows in not your base Win9X directory, you need to change the two CD commands accordingly. These commands are necessary to ensure that the files get extracted from the cab files to the appropriate locations on your HD.

8.Now ADD lines similar to what's below to the END of the file. The purpose of these lines is just to give you some sort of an on-screen message when GETVXD.BAT finishes so that you will know it, and also know that it is OK to close the Dos Window that will be left open:

cls

echo extraction of files is complete, it's ok to close the dos window now.

9.Now compare your list of file of files to be extracted to those files that currently exist in your \Windows\system\vmm32 directory. If any files in your list already exist in this directory chances are that they are newer versions than what is on your CD. It is up to you to determine this. If you determine that the version of a file in your \Windows\system\vmm32 directory is newer than what is in your cab files, then Delete that entry from the list because we don't want to overwrite a newer version already existing in the directory with an older one that will be extracted from your cab files.

10.Save your work as GETVXD.BAT

11.Load the WININIT.INI saved in step 4 into your editor.

12.Using S&R enter "=hex:00 (Note the leading quote mark in this text) as the search text and for the replacement text enter =c:\windows\system\vmm32.vxd (adjust the drive\path if necessary) and then perform a Replace All. You should now have a list that looks something like:

"biosxlat.vxd=c:\windows\system\vmm32.vxd

"combuff.vxd=c:\windows\system\vmm32.vxd

"configmg.vxd=c:\windows\system\vmm32.vxd

13.Using S&R enter " (a single quote mark) as the search text and c:\windows\system\vmm32\[/B](Adjust drive\path if necessary) as the replacement text and perform a Replace All. You should now have a list that looks something like:

c:\windows\system\vmm32\biosxlat.vxd=c:\windows\system\vmm32.vxd

c:\windows\system\vmm32\combuff.vxd=c:\windows\system\vmm32.vxd

c:\windows\system\vmm32\configmg.vxd=c:\windows\system\vmm32.vxd

14.At the TOP of the file add a section header of [SetupOptions] and under it Combine=1, Under this add another section header of [CombineVxDs]. Your file should now be similar to:

[SetupOptions]

Combine=1

[CombineVxDs]

c:\windows\system\vmm32\biosxlat.vxd=c:\windows\system\vmm32.vxd

c:\windows\system\vmm32\combuff.vxd=c:\windows\system\vmm32.vxd

c:\windows\system\vmm32\configmg.vxd=c:\windows\system\vmm32.vxd

15.Once you have your file looking like the above example save it keeping the name WININIT.INI

16.Move WININIT.INI and GETVXD.BAT from wherever you saved them with your editor to your \Windows directory

17.Although not required for the rest of the procedure to work, I strongly suggest that you backup any files that already exist in your \Windows\system\vmm32 directory as well as your current vmm32.vxd file and your current registry. How you backup these files is up to you.

18.In the Start > Run dialog enter GETVXD and click on OK to start the batch file which should log you on to the HD that contains Win9X, change to the appropriate directories and extract all file to these directories, automatically overwriting any files that exist with the same filename. Depending on your system speed this batch file may take a while to execute due to the simple way it was written which caused only one file to be extracted from the cabs at a time. I don't think you will be using this batch file often enough to worry about combining filenames on an extract command line to save a little time by extracting multiple files at a time.

19.Restart Win9X and during the startup process, WININIT.INI will be processed. While wininit.ini is being processed you will get a Please wait while Setup updates... message on your screen, as the new vmm32.vxd file is created from the individual files in the \Windows\system\vmm32 directory. During the process, all files combined into vmm32.vxd will be deleted from the \Windows\system\vmm32 directory leaving only those that do not belong in vmm32.vxd (were not listed in your wininit.ini file) which should have been there before starting this procedure.

That's it, you should have re-built your vmm32.vxd file. If everything is working, BACKUP your new vmm32.vxd file now, so if anything happens to it you don't have to repeat this procedure.

I hope this helps others which have problems relating to VXD's

Hiya WoodMann

I wanted to give a last try before reformatting my Partitions and drives.

And i guess it worked but then ill still have to see.
And if everythin works out well then ill let u guys know.

And for the part, i have FAT32 on WIn98SE and it was the same for WinXP too untill i "removed" it.

Though what im tryin to state here is that every other program in my Comp just works fine with no Glitches whatsoever, but my comp only crashes when SI is Invoked.
But now it doesnt but i have to get rid of the Black Screen and im very tired with all the formatting and copying. I had to make a Backup of all my files in orde to format.

HIya

i had posted a way to copy all the needed VXD's by the OS. And it really did work.
Now my SI does not crash or hang. Its work perfectly.

Though i havent tried DS 2.6, not for atleast.

Guess i didnt need had to reformat and repartition my drive afterall.

Anywaz i think if anyone comes across this sort of Problem with SI, my previous post might be of help.

WoodMann can u make this post a Sticky one.

Thanx

HIya

i have found out the problem which causes the hangups when using DS 2.6.

Its with Microsoft's Wireless Intellimouse aas im using it.
When i just plugged it out, Si didnt crash as it used to .

Ajnabi:

I believe that there is a wireless mouse setting in the setup for D.S. 2.6 for using a cordless mouse and I seem to remember that it specifically has a setting for the M$ cordless intellimouse.. Works fine with my logitech cordless. Check the set-up features and you may be able to activate this feature without reinstalling D.S. 2.6. Or you have it working and could just leave it alone.

Regards.

JMI

i did actually choose the option for PS/2 or USB and i also checked on Enhanced Mouse.

It does detect it, theres no doubt coz when i disabled it at first, it gave a Message that theres a mouse detected with Enchanced features.

But when i keep the settings, SI crashes. Though if i disable the mouse in Settings.
Everythin Works.