Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
96 & NT 4.00
Message
De
25/10/1998 12:12:10
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Titre:
Divers
Thread ID:
00148965
Message ID:
00150319
Vues:
18
>Dear Ed Rauh
>I think u have mistaken what i meant,
>By uninstalling softwares, i meant all the software which is dependent on win95 as our aim is to shift the booting to win95 and that also through uninstalling through control panel ,add remove program.
>(in no way i gave an idea to remove application directory)
>When the dual booting is controlled by win NT, U can uninstall win95 through win95 setup which i feel no doubt the best method.This method automatically transfer the complete control to winNT and hence the dual booting problem can be solved.

It's completely unnecessary; the registries are not shared between Win95 and WinNT. Removing the Win95 directory structure and the directories containing Win95-only referenced applications is sufficient; if a resource is common to both Win95 and WinNT, it will appear in both the Win95 Windows or Windows\System path AND the WinNT or WinNT\System32 path; the paths are not common, or the shared component will be in an application directory. So removal of the Win95 directory structure and the BOOT.INI entry is more than sufficient.

Uninstalling an app used in common by both NT and 95 through the Control Panel is asking for a disaster to happen, becasue the shared component reference counts kept in the separate registries are not in sync, and as a result, a shared component in a common app directory needed by the instance under NT may be deleted improperly by the Win95 uninstall. If the app is not common to both Win95 and WinNT, there's no need to uninstall on the Win95 side; jsut make it go away, since the registry references that might exist will not matter once the system is NT-only. This uninstall behavior is one reason that most apps require that you install to separate application directories under Win95 and WinNT, sharing data directories if the application data is the same regardless of which operating system is running.

Dual boot with common applications is a major problem, and one reason I've moved away from trying to make one system run in multiple environments for production, or serious development. It's hard enough to keep one operating system's component versions properly updated - for example, if you update an ActiveX control, and need to use it in both environments, you must make certain to register it in both environments. Registering it in one but not the other ensures that one of the two will be unstable at best, and broken in the vast majority of cases.

>
>I think we are looking to the same problem with different angles.
>Your way can solve the problem, but still i feel uninstallation is better than removing/deliting win95 directory.

If it works for you, great - there are too many instances where I know it doesn't.

>
>By the way what is PITA (No idea).

Pain In The Artichoke (or some body part, as appropriate.)

>pls feedback.
>Aashish
>
>
>>>Well friend, u have the same setup as i have,
>>>try out running win95 setup and then uninstall all the components.
>>>but before this uninstall all the software u loaded in win95.
>>>i hope this should and should work.
>>>
>>
>>(1) There's no need to uninstall anything, since the registries are not shared between NT and 95. Simply removing the Win95 directories are sufficient, since there's no file dependency. It's a bad idea to remove all the application directories, since if any of the apps are installed under both NT and 95, removing the common directories will affect the NT registry.
>>
>>It's necessary to remove the BOOT.INI reference to the Win95 boot record to make the boot manager menu not show Win95 - the reference remains even if Win95 does not, since it isn't controlled by the Win95 install.
>>
>>If dual boot is not managed by NT, there's a significantly more complex procedure involved, since it's necessary to load the NT boot sector and loader and create the correct BOOT.INI entries for NT's boot manager if they aren't there. Doing this involves a partial run of the WinNT installer, at least to restore the NT boot and loader files once Win95 is removed; it's not a big problem, but it is moderatley involved and a bit of a PITA. The boot sector written by NT has significantly different behavior than the boot sectors used by DOS and/or Win95 (and Win98's is different from both of these as well.)
>>
>>BTW, I don't have 95 installed anywhere here in any case; I do have one system set up with both Win98 and NT, using NT's loader to control the boot process. The process I described above, removing the BOOT.INI entry and the Win95 directories does work when NT controls the boot process.
>>
>>>try out
>>>aashish
>>>
>>>>>Hello All,
>>>>>Does anyone know how to uninstall Windows 95 from a dual boot NT/W95 setup leaving NT intact, I basically have Windows 95 and NT 4 loaded onto the same hard disk and would like to remove 95 leaving NT operational ( also removing the dual boot menu )
>>>>
>>>>If NT is providing the boot management, simply delete the Win95 directories, and edit BOOT.INI to not reference the Win95 boot. If some other boot manager is being used (ie you're hosting dual boot NT from the WIn95 boot manager, not something I thought was doable, or in any case desirable) you're on your own.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform