Hi Jim,
Well, I took your suggestion about un-installing and re-installing max,
which I did once already(no success) but this time with a difference.
I think I mentioned early on in this thread that the whole thing started
with a "restore" of program files onto a newly installed OS.
I think that I mentioned, that the restored copy of max didn't show up in
the add/remove programs so I installed a second copy from
the max CD into a different folder and this is when the VDD error message
started showing up.
I had some hesitancy about just deleting the "restored and faulty max
folders" because of the bad experience of deleting the "restored and faulty
norton folders" which has rendered half of norton systemworks inoperative.
No wanting a crippled 3Dmax I resisted the temptation to delete the faulty
max folder until now.
So, I un-installed the one copy of Max through add/remove and just deleted
the other max folders. I then re-installed Max from the CD and it worked ,
the VDD error dialogue box doesn't show up anymore.
I feel kind of sheepish that I had to drag you through all this Regedt32
exploration but hey , I learned something and am fascinated by the depth of
knowledge that you have regarding the windows registry.
Next time is comes around that I have to restore, I probably won't be doing
a restore to "C" drive nor any program file restores but just take the time
to install all the apps one at a time.
Jim, Thanks ever so much for your time, the sharing of your expertise and
dedication to resolving my situation.
Sincerely
Gregory CJ
PS
I will run the folllowing as well.
Also, Gregory - You probably should install 319113, Windows 2000 Application
Compatibility Update (March,2001), here if you haven't already done so:
http://support.microsoft.com/default...en-us%3b319113
"Jim Byrd" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> OK, Gregory - If the key's not there at all, then that's fine - just add
> it. NT backup is fine for that purpose. If you don't have Merge
> (different OS), then just double click on the VirtualDeviceDrivers.reg
> file and the Registry entries should be made.
>
> --
> Regards, Jim Byrd, MS-MVP
> Please respond in original thread in Newsgroup.
>
>
>
>
> In idOKa.26673$Fy6.9550@sccrnsc03, Gregory CJ typed:
> > Hi Jim,
> > You are right about my hesitation in dealing with the registry,
> > but I did follow your instructions, and need some clarificaton,
> > "and do an export of the entire Registry for backup"
> >
> > you are meaning backup the registry through NT backup, right?
> > which I did.
> > Right click on it, then
> >
> >> select Delete, answer Yes where required and OK out.
> >
> > In the folder VirtualDeviceDrivers there is nothing to begin with ( no
> VDD
> > key)
> > and so hence nothing to delete. I should have made that clear the
> last
> > post. Or do you
> > mean deleting the folder VirtualDeviceDrivers, which appears to be
> > undeleteable anyways.
> > I did change the VirtualDeviceDrivers.txt and re-named
> >> VirtualDeviceDrivers.reg
> > When I right click on the VirtualDeviceDrivers.reg I don't get the
> option
> > to
> > Merge. (It is presently sitting on my desktop) That's about as far
> as I
> > got,
> > How can I make this file merge?
> >
> > Your help is much appreciated.
> > Greg
> >
> >
> > "Jim Byrd" <(E-Mail Removed)> wrote in message
> > news:#(E-Mail Removed)...
> >> Hi Gregory - Since you don't seem to be too comfortable dealing with
> the
> >> Registry, I've attached a file to do this for you. Do the following.
> >> Save the attched file as VirtualDeviceDrivers.txt , then
> re-name
> >> it to VirtualDeviceDrivers.reg . Open regedit.exe (or
> >> Regedt32.exe) and do an export of the entire Registry for
> backup.
> >> Now drill down to the VirtualDeviceDrivers key. Right click on it,
> then
> >> select Delete, answer Yes where required and OK out. That key should
> >> now be gone (you may have to hit F5 to refresh the Registry in
> regedit.)
> >> Now right click on the file you just renamed
> >> (VirtualDeviceDrivers.reg) and select Merge. Answer as required
> >> until it says that the info has been added. Now re-boot your
> computer.
> >> Post back here if you have any before doing this if this isn't clear,
> or
> >> afterwards with your results, please.
> >>
> >> --
> >> Regards, Jim Byrd, MS-MVP
> >> Please respond in original thread in Newsgroup.
> >>
> >>
> >>
> >>
> >> In yoKKa.27319$3d.16091@sccrnsc02, Gregory CJ typed:
> >>> Hi Jim,
> >>> I followed the instructions but was unable to create a VDD key
> >>>
> >>> "If the above steps do not work, or if you are unable to create the
> VDD key,
> >>> it may be necessary to also delete and recreate the whole
> >>> VirtualDeviceDrivers registry key"
> >>> sounds like I may have to attempt this next procedure...any help on
> this
> >>> one?
> >>> Thanks
> >>> Greg
> >>>
> >>> "Jim Byrd" <(E-Mail Removed)> wrote in message
> >>> news:(E-Mail Removed)...
> >>>> Hi Gregory - See here and do EXACTLY what it says: Virtual Device
> >>>> Driver Error Message in 16-Bit MS-DOS Subsystem
> >>>> http://support.microsoft.com/default...;EN-US;Q254914
> You
> >>>> MUST have Admin privileges and you MUST use regedt32 .
> >>>>
> >>>>
> >>>> --
> >>>> Regards, Jim Byrd, MS-MVP
> >>>> Please respond in original thread in Newsgroup.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> In doFKa.26202$3d.14788@sccrnsc02, Gregory CJ typed:
> >>>>> I replaced my hard drives and made a fresh install of NT 4 (sp4)
> >>>>> and over that installed an upgrade of win2k.
> >>>>> I restored data from tape to the original locations on C: and E:
> >>>>> drives,(using NT backup)
> >>>>> choosing the option " not to replace existing files if already on
> Hard
> >>>>> Drive."
> >>>>> Now I get a error message when I run the 3d app 3d studio Max.
> that
> >>>>> states,
> >>>>>
> >>>>> " 16 bit\ Windows subsystem...system\current Control
> Set\Control\Vitual
> >>>>> Device Drivers.
> >>>>> VDD Virtual Device Driver format in the registry is invalid...
> choose
> >>>>> "close" to terminate application
> >>>>> or ignore.
> >>>>>
> >>>>> This error message comes up usually once a day upon the initial
> start up
> >>>>> 3D Max.
> >>>>>
> >>>>> Any thoughts on correcting this error would be greatly
> appreciated.
> >>>>>
> >>>>> Thanks
> >>>>> Gregory CJ
>
Similar Threads
