--------------- FIDO MESSAGE AREA==> TOPIC: 118 WINDOWS Ref: F3D00004 Date: 02/27/98 From: JOHN FOSTER Time: 07:00am \/To: MATT HOPPER (Read 3 times) Subj: Advice MH>Hi all, MH>I have a problem. MH>I only have the Win95 upgrade CD and want to install it to a new MH>Hard disk. MH>Is there a way of doing this or will i need to find DOS and Win3.1? MH>Thanks in advance, MH>Matt. MH>--- ViaMAIL!/WC4 v1.30 MH> * Origin: ViaMAIL! - Lightning Fast Mailer for Wildcat! (2:2502/1000) Matt, I read this tip in a Window's magazine article. It is supposed to be a fix for the situation you are in. Hope it works. Open Notepad and save a document as WIN.CN_ (_ is a hyphen shifted). Put the WIN.CN_ file on a diskette. When you reach the point in the istallation where Win95 asks you to show it a previous version, put in the diskette with the WIN.CN_ file on it. The installation program will accept it as proof of a previous version. (The document you save can be a blank document as long as it is saved with the filename WIN.CN_) * OLX 2.1 TD * California raisins murdered: Cereal Killer suspected! --- Maximus/2 3.01 * Origin: The I.O. Board - 4GB -X< Anderson, IN >X- V34+ (1:2255/10) --------------- FIDO MESSAGE AREA==> TOPIC: 118 WINDOWS Ref: F3D00005 Date: 03/04/98 From: PAAVO MKEL Time: 05:38pm \/To: JERRY SCHWARTZ (Read 3 times) Subj: Memory architectures > main (L2) memory cache is relatively slow. >If the BIOS on your current machine allows it, you could turn off your L2 cach > temporarily and see for yourself. Yes, I knew that. It does really mean more if there is no cache at l. > There are different cache designs, and different ways of interleaving emory > access (which results in higher throughput). >I can't comment on any particular architecture, but clearly if this weren't an > issue different machines would benchmark out at the same numbers. Are there any benchmarks in the net which would reveal the speed differences? --- BBBS/2 v3.42 ToMmIk-5v * Origin: Deaf Leopard - 06-3207580 V.34/ISDN - 3200759 7*V.34 (2:224/0) --------------- FIDO MESSAGE AREA==> TOPIC: 118 WINDOWS Ref: F3D00006 Date: 03/03/98 From: TOM WARREN Time: 10:52am \/To: FRED SPEIR (Read 3 times) Subj: Re: >DLL file -Thanks for the response, Fred. I found the file on the internet. It is used with a fax program. I had deleted the program and when I was attempting to run another program a error came up stating it couldn't find BFTOOL.DLL. I found out on the internet that the pc I was using at the shop had it's default printer set up as the fax program. Once I changed default printer from the fax to a printer that had a driver installed that took care of the problem. Back to the loose nut on the key board. Anyway thanks again. TW> I am looking for a file called BFTOOL.DLL. FS> To what program does this file belong to? Is there an application FS> you have looking for this file? FS> I have thousands of programs at my disposal, if you can post what FS> program this is from, it would help in the search. FS> FS> TTYL, FS> Fred Speir FS> Logical Positivism FS> fspeir@sunnet.net FS> ICQ: 6768145 FS> ... If there is no God, who pops up the next Kleenex? FS> -!- Blue Wave/DOS v2.30 FS> ! Origin: The Logical Positivism BBS * Lawton, OK * (1:385/44) Tom The Electric Man ... Things are not always as they seem. --- Michiana Mail Center * Origin: CW Technical Support - South Bend, IN - (219) 272-8129 (1:227/129) --------------- FIDO MESSAGE AREA==> TOPIC: 118 WINDOWS Ref: F3D00007 Date: 03/02/98 From: BRUCE WILSON Time: 07:28am \/To: ROBERT FOWLER (Read 3 times) Subj: Re: *.DLL Files Question On 18 Feb 98 12:21pm, Robert Fowler wrote to Bruce Wilson: RF> While you might not have known the potential outcome, you could RF> keep your files from being lost by copying them to a temp RF> folder. Then if an overwrite results in an undesirable outcome, RF> a restoration is not so difficult. That's what I did with the home installation, after I'd learned the hard way what'd happened and its effects at work. The real problem is one's not having a clue what those *.dll files do and the effect of their being changed until something quits working and something gives you a hint the cause might've been a change in a *.dll file. In the case of the printers, I learned precisely which one caused the problem, but I had to take a "shotgun" approach to get the AOL browser working again. --- Via Silver Xpress V4.4P [Reg] * Origin: FOG-Line BBS - 515-964-7937 - 1:290/627 (1:290/627) --------------- FIDO MESSAGE AREA==> TOPIC: 118 WINDOWS Ref: F3D00008 Date: 03/02/98 From: BRUCE WILSON Time: 09:14am \/To: SUSAN AND GEOFF (Read 3 times) Subj: Re: .dll problem On 19 Feb 98 10:32am, Susan and Geoff wrote to All: SaG> We looked at the install file and compared dates/versions of SaG> the .dll files. Oddly some of the overwritten files were SaG> *newer* than the ones that overwrote them! We replaced all of SaG> them. To find out what these .dll files do (sort of) look at SaG> the file information in your file manager under File. Is this good for Windows 3.1 or only for Win 95? (The other half of the problem is not knowing how they're used by individual programs. With list in hand, I tried contacting AOL to learn which of the .dll files that'd been changed might've affected its browser operation, but the tech didn't know. His only suggestion was to do a "clean" install of AOL, which didn't work, presumably because it didn't put the affected .dll file[s] there in the first place.) --- Via Silver Xpress V4.4P [Reg] * Origin: FOG-Line BBS - 515-964-7937 - 1:290/627 (1:290/627) --------------- FIDO MESSAGE AREA==> TOPIC: 118 WINDOWS Ref: F3D00009 Date: 03/02/98 From: BRUCE WILSON Time: 09:19am \/To: CHRISTOPHER GREAVES (Read 3 times) Subj: Re: win3.x on a 386? On 21 Feb 98 08:54pm, Christopher Greaves wrote to All: CG> Is it likely that the hardware at 640K is truly insufficient? Yes. CG> I thought that 286s had only 640K. They also accepted more, as expanded or extended memory. I could, for example, put Win 3.1 on a Toshiba portable with 4 megs of RAM; and the 386 systems at work running Win 3.1 all have 8 megs, at a minimum. --- Via Silver Xpress V4.4P [Reg] * Origin: FOG-Line BBS - 515-964-7937 - 1:290/627 (1:290/627) --------------- FIDO MESSAGE AREA==> TOPIC: 118 WINDOWS Ref: F3D00010 Date: 03/02/98 From: BRUCE WILSON Time: 09:22am \/To: BILL DAWSON (Read 3 times) Subj: Re: win3.x on a 386? On 23 Feb 98 05:51pm, Bill Dawson wrote to Robert Fowler: BD> AFAIK, modern-type SIMM/DIMM memory has never been available in BD> increments less than 1 MB. That tells me that the 386 he has is BD> a pre-SIMM unit, placing it in the era pre-1991 or so. Uh ... There were 256K 30-pin SIMMs before there were 1-meg 30-pin SIMMs. --- Via Silver Xpress V4.4P [Reg] * Origin: FOG-Line BBS - 515-964-7937 - 1:290/627 (1:290/627) --------------- FIDO MESSAGE AREA==> TOPIC: 118 WINDOWS Ref: F3D00011 Date: 03/02/98 From: BRUCE WILSON Time: 09:24am \/To: BUD JAMISON (Read 3 times) Subj: Re: win3.x on a 386? On 24 Feb 98 06:09am, BUD JAMISON wrote to BILL DAWSON: BJ> 30 pin SIMMS were available in 256k versions, but they weren't BJ> common. Yes they were, until they were supplanted by the 1-meg variety (in turn supplanted by the 4-meg variety). --- Via Silver Xpress V4.4P [Reg] * Origin: FOG-Line BBS - 515-964-7937 - 1:290/627 (1:290/627) --------------- FIDO MESSAGE AREA==> TOPIC: 118 WINDOWS Ref: F3D00012 Date: 03/03/98 From: NORMAN WOOD Time: 01:41pm \/To: ** ALL ** (Read 3 times) Subj: NO DOS MOUSE(FROM WIN3.1) A widow neighbor has a computer operating with Win 3.11. She recently had the Logitech "OEM Mouse Ware 95" ver. 7.0 installed. She is thrilled with the pink mouse icon in the Program Manager group; however, now the mouse no longer works in Dos mode. (Works fine in Windows). Her * autoexec.bat * file includes a mouse loading line (C:\Mouse\mouse.exe and Set LMouse=C:\Mouse) and a blue Logitech logo panel flashes when booting;but,there is no mouse driver loaded when she goes into Dos (nothing listed for the mouse when checking memory usage). Any thoughts as to what the problem might be and what should be done to fix it? Thanks. Norm Wood * 1st 2.00 #1862 * Backup religiously -- Pray you don't lose anything! --- DBSMail V2.00g [F633BFFC] * Origin: tnl-online.com -=- san diego, ca -=- (1:202/711) --------------- FIDO MESSAGE AREA==> TOPIC: 118 WINDOWS Ref: F3D00013 Date: 03/03/98 From: STEVEN GRAY Time: 11:19pm \/To: ROSS NAPIER (Read 3 times) Subj: DIY PC. MSDOS to load W95 -=> Quoting Ross Napier to All <=- RN> In order to load windows 95 from the CD on the new system you RN> need to be able to get the pc to recognise the CD rom drive. To RN> do this you first have to install MSDOS, set up the autoexec.bat RN> and config.sys for the correct CDROM drivers and only then can Ross, I've never had occasion to do it, but I should think that all you have to do is put the autoexec.bat and config.sys with CDROM drivers on a DOS bootable floppy. You shouldn't have to do a full DOS installation. Steve ... Predestination was doomed from the start. --- Blue Wave/DOS v2.30 * Origin: LASER! - ORLANDO FL -(407) 647-0031 (1:363/225)