| Author |
Message |
Gerod Hall
| | Posted on Tuesday, September 3, 2002 - 11:24 am: | |
What is the absolute easiest way to upgrade a Win95 machine up to a Win98 machine? I have 18 computers I need to upgrade and don't want to spend a whole lot of time on this project, however, I do want it to be done correctly. Any suggestions? |
win
| | Posted on Tuesday, September 3, 2002 - 3:24 pm: | |
ah. are you on a network? and, is all the hardware the same? if so, you can do a basic network install from a file server. requires boot disks, or pxe nic cards. dns server is needed to get the ip address of the files server, so you can create a script from the 98 setup to tell it what to install on what machine. check the resource kit for more info. it's fairly easy just takes time to setup the network and scripts. have your hardware drivers disks for the final tuning. |
Gerod Hall
| | Posted on Wednesday, September 4, 2002 - 8:10 am: | |
I am on a network, but would prefer to install machine by machine. I am still learning the ropes of this network that I inherited and am not certain on any IP addresses. |
win
| | Posted on Thursday, September 5, 2002 - 4:09 am: | |
i thought i posted this last night, but i was tired, so i may not have hit the post button right, i don't see it here. ok......
here's what i'd do, i'd get a boot disk (startup), or a few of them, copy format.com to the disk. then, i'd partition, and format the drives using said boot disk(s). then, i would startup with the cd in the tray, using the floppy, make a directory called "cab" and copy the cab files including scandisk, to the drive in a temp (or permanent) folder such as "cab" using the command: A:copy (your cdrom drive letter):win98\*.* C:cab
like this at the command prompt; A:mkdir C:cab (enter) which will make the directory. then: A:copy E:win98\*.* C:cab (enter)
that will make a directory and copy all the contents of the win98 folder on the cd to the cab folder on c: drive. you can then go down the line doing this and when you have a few done, you can go back and run setup from the cab folder. then go back and forth copying cab files and starting setup, assembly line style til you're done, when you're done with the installs, you can then sit at each machine in turn, and make up the machine names, policies, whatever programs you want to do. so you have to have drivers disks handy. which is why the network is so nice, you can do it all from a few boot disks and a file server. takes less time so you can do something else. you could also have the drivers for the computers on the server, and when you want to go get them, with win98 up, it's easy. you'll probably have to install netbui protocol so the machines can see each other on the net if it doesn't already. make sure your names and files shares are there, lots to do after setup which is why i suggested the scripting and network setup.
ah, you can also burn a copy of the win98 disk for "archive" purposes only (of course you can, 1 only legitimately, unless you got a special deal) and use 2 cds to do it. make it go twice as fast. i'd log all this so you know who's who's when you need to give them permissions to access your files on the server, names for users and passwords, etc. or you'll get lost. heh. and..... give a copy to only your boss so in case anything happens to you, if they need to get in and change something with another guy, they can, and tell him/her, to put the passwords, logs, in a safe, or a very safe place. just in case. |
win
| | Posted on Thursday, September 5, 2002 - 4:16 am: | |
oh, note these instructions are for a clean install, which is the best way to upgrade. but, for just 95 to 98, get the 2 cds, and go from machine to machine, it'll do most of it. other than that, you can do the file server thing, and put the cd on it, then point each machine to go to the file server, and run setup. if you need a confirmation of eligibility, you can take the 95 disk and insert it in the cd tray on each machine in turn, if it asks for it. that's it. and be prepared to run into problems along the way. need to know how to fix them, usually dlls. |
|
