Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Windows 95 disketts

38 views
Skip to first unread message

Kevin Rose

unread,
Sep 11, 2000, 8:10:02 PM9/11/00
to
Desperately looking to get the Windows 95 Diskettes since my system wont
read the cd-rom. I am hoping that somebody can advise me and point me in
the proper direction of either properly copying my cd-rom onto disk or
acquiring an new set. It is very important I be able to get this. Any
information is greatly appreciated.

Thanks for your assistance and information.


JD Adams

unread,
Sep 11, 2000, 6:02:14 PM9/11/00
to
If all you need are DOS CD drivers, they can be found on the mfg's
website. You could be looking for W95 on floppies for a long, long
time.

-JD

Bob B.

unread,
Sep 11, 2000, 6:58:53 PM9/11/00
to
>Subject: Re: Windows 95 disketts
>From: JD Adams JDA...@Softcom.Net

Just saw some for sale on ebay.


Bob B.
Please Reply to the Newsgroup.
People are more important then their opinions.

Brian

unread,
Sep 12, 2000, 6:05:49 AM9/12/00
to
The following is an extract from a message posted to this group previously
and should enable you to produce your own floppies from the windows cd :-

"here's a method I saved from the microsoft.public.win95.general.discussion
newsgroup:
----------------------------------------------------------------------------
------
How to create a floppy installation of Win95b (OSR2) using OEM cd-rom.

There have been a few times when I needed to install Windows 95 from floppy
because a system didn't have a cd-rom. Not common since all new systems ship
with cd-roms, but sometimes you run into an older system that doesn't have a
cd-rom built-in, or you have a notebook and external cd-roms are too
expensive. In my case, I bought a Compaq Prolinea 466 on eBay and it didn't
have a cd-rom. I could have gone out and bought the cheapest one I could
find, but this got me thinking about how to create my own installation
diskettes from the cd-rom that I already had. I knew that you can't create a
win95 install from the original release of win95 because the cab files were
~2MB in size. Too large to fit on a single disk, even if it was formatted to
DMF (Distribution Media Format) size of 1.68MB. The Win95b version didn't
suffer this problem because the cab files were just under 1.68MB so the only
problem was formatting a diskette to DMF and finding out what files were
needed on diskette 1, 2, 3 etc.

The first disk needs to be formatted to 1.44MB. This is because a system
without win95 cannot read DMF diskettes. Once win95 is on it, it can read
and write to DMF (although it still cannot format one). The EXTRACT.EXE
utility on the first floppy lets the win95 installer read and write DMF
disks. That's why the installer can read disk 2, 3... during installation.

Anyway, after a bit of tinkering (and cheating by seeing how others have
done it), I came to the following set of files for disk 1. They all come on
the cd-rom in the \Win95 directory. Simply format a disk to 1.44MB, give it
a volume label of "DISK1" and copy these files from the \win95 directory on
the CD-ROM. If you find yourself having to create win95 disks often then you
could write a batch file to automate it.

PRECOPY1.CAB
DOSSETUP.BIN
EXTRACT.EXE
MINI.CAB
DELTEMP.COM
SCANDISK.PIF
SAVE32.COM
SCANDISK.EXE
README.TXT
SETUP.TXT
SETUP.EXE
SCANPROG.EXE
WB16OFF.EXE
SMARTDRV.EXE
XMSMMGR.EXE
WINSETUP.BIN


Next, get your hands on a utility to create DMF disks. A good one is
MaxiDisk available from www.herne.com. You're going to need 27 DMF-formatted
floppies, so make sure to have more than that available. Most HD disks will
have no problems formatting to DMF, but if you use really cheap disks then
you may run into lots of errors. Set whatever utility you're using to verify
the format. Don't forget to set the volume label as "DISK2". Copy the
following files from \win95 directory of the cd-rom to disk 2.

PRECOPY2.CAB
WIN95_02.CAB


Next, just copy the remaining cab files to the other DMF diskettes.
WIN95_03.CAB goes on disk 3, WIN95_04.CAB on disk 4, etc. Don't forget the
volume labels on these either.

You're done. Now you have a set of Win95 OSR2 install floppies. What's nice
about being able to create your own set of install disks is that if someone
burns a copy with their name/company on it, you can undo the damage by
creating a new disk. By the way, the registration info is saved on disk 2.
So if someone goofs up your install disks by branding them, just recreate
disk2. You will need to reformat the disk, since the user info is not saved
in the files. Its saved on a sector in the floppy, so you will need to
reformat the disk to DMF and recopy the cab files from cd-rom again.
----------------------------------------------------------------------------
-----"

hope this helps,

Brian

Kevin Rose <knm...@bellsouth.net> wrote in message
news:LSbv5.2811$5M.2...@news3.mia...

life...@xxvol.com

unread,
Sep 17, 2000, 3:00:00 AM9/17/00
to
JD Adams <JDA...@Softcom.Net> said:

Question. Does the same thing go for a mouse? My brother has a DOS
machine, and we're trying to put Wind95 on it, starting directly from
the CD. The mouse is fine until the installation process gets to the
"setting up hardware" part of it. At that time the mouse goes dead.

The mouse is Logitech. I've tried going through Control Panel. I've
tried both Logitech and generic mouse drivers. Regardless, I find the
mouse dead.

What's going on here?

Jim L
MR/2 ICE, version 2.2
Remove XX from address to Email
Crooks and kooks will get guns regardless of laws.


Bob B.

unread,
Sep 17, 2000, 8:07:04 PM9/17/00
to
>Subject: Re: Windows 95 disketts
>From: life...@xxvol.com

I forget the switch you need with setup to enable the logitech mouse during
setup. /L something?? Anyway don't worry about it. You can get through setup
easy enough w/out a mouse, then after install set the mouse up.

>Question. Does the same thing go for a mouse? My brother has a DOS
>machine, and we're trying to put Wind95 on it, starting directly from
>the CD. The mouse is fine until the installation process gets to the
>"setting up hardware" part of it. At that time the mouse goes dead.
>
>The mouse is Logitech. I've tried going through Control Panel. I've
>tried both Logitech and generic mouse drivers. Regardless, I find the
>mouse dead.

John K. Picken

unread,
Sep 18, 2000, 3:00:00 AM9/18/00
to

On Sun, 17 Sep 2000 life...@xxvol.com wrote:

> Question. Does the same thing go for a mouse? My brother has a DOS
> machine, and we're trying to put Wind95 on it, starting directly from
> the CD. The mouse is fine until the installation process gets to the
> "setting up hardware" part of it. At that time the mouse goes dead.
>
> The mouse is Logitech. I've tried going through Control Panel. I've
> tried both Logitech and generic mouse drivers. Regardless, I find the
> mouse dead.
>

> What's going on here?
>

If it's a really old Logitech model, try using the Mouse Systems
driver.

jkp

JD Adams

unread,
Sep 18, 2000, 3:00:00 AM9/18/00
to
life...@xxvol.com wrote:
> Question. Does the same thing go for a mouse? My brother has a DOS
> machine, and we're trying to put Wind95 on it, starting directly from
> the CD. The mouse is fine until the installation process gets to the
> "setting up hardware" part of it. At that time the mouse goes dead.
>
> The mouse is Logitech. I've tried going through Control Panel. I've
> tried both Logitech and generic mouse drivers. Regardless, I find the
> mouse dead.
>
> What's going on here?

Nope, the same thing does not apply to mice. Windows has its own mouse
drivers built-in - no need for DOS drivers that wouldn't work within
Windows anyway. If your Logitech mouse isn't working right, the drivers
are wrong, or the mouse doesn't work right to begin with.

My suggestion to you is to try a different mouse. They are not all
created equal. I've run into dozens of people who use El-Cheapo mice
who complain about dead mice, badly tracking mice, etc. I have them
plug in a Microsoft Basic Mouse, and all is well, forever.


Best regards,

-JD


Visit JD's Archive:
http://208.131.40.8/users/jdadams

life...@xxvol.com

unread,
Sep 18, 2000, 3:00:00 AM9/18/00
to
JD Adams <JDA...@Softcom.Net> said:

> If your Logitech mouse isn't working right, the drivers
>are wrong, or the mouse doesn't work right to begin with.

>My suggestion to you is to try a different mouse.

We got it working. On a wild guess I moved the mouse from COM1 to COM2.
It worked. When we changed modems it jumped back to COM1. We put the
first modem back in and now it is still on COM1. I can only assume
plug-n-pray is playing tag with the hardware.

life...@xxvol.com

unread,
Sep 18, 2000, 3:00:00 AM9/18/00
to
bbian...@aol.comcomped (Bob B.) said:

>You can get through setup
>easy enough w/out a mouse, then after install set the mouse up.

Thanks, but I've gone through dozens of attempts to get it going via the
control panel. Nothing. The port keeps changing.

JD Adams

unread,
Sep 18, 2000, 3:00:00 AM9/18/00
to
life...@xxvol.com wrote:
>
> JD Adams <JDA...@Softcom.Net> said:
>
> > If your Logitech mouse isn't working right, the drivers
> >are wrong, or the mouse doesn't work right to begin with.
>
> >My suggestion to you is to try a different mouse.
>
> We got it working. On a wild guess I moved the mouse from COM1 to COM2.
> It worked. When we changed modems it jumped back to COM1. We put the
> first modem back in and now it is still on COM1. I can only assume
> plug-n-pray is playing tag with the hardware.

A-HA! I'm sure Windows is noodling with the IRQ's/IO ports, just for
laughs. (I have my hardware set up so that 8-bit cards and hardware
ports are assigned by the computer at bootup, and Windows can't change
those assignments at runtime, preventing this sort of thing.)

OOPS! Some folks <ahem> around here get censor-happy when I let out
little secrets like that one! Best keep all this tech-talk to a
minimum, lest we confuse the newbies! <g>

Glad to hear you worked a bit of magic with your mouse.

life...@xxvol.com

unread,
Sep 18, 2000, 3:00:00 AM9/18/00
to
JD Adams <JDA...@Softcom.Net> said:

>(I have my hardware set up so that 8-bit cards and hardware ports are
>assigned by the computer at bootup, and Windows can't change those
>assignments at runtime, preventing this sort of thing.)

>OOPS! Some folks <ahem> around here get censor-happy when I let out
>little secrets like that one! Best keep all this tech-talk to a
>minimum, lest we confuse the newbies! <g>

I'm as newbie as anyone. How do you set that up? Hm, maybe a switch in
the BIOS?

0 new messages