Mail Archives: djgpp/1997/11/01/23:20:20
Darrel Hankerson wrote:
>
> Startup time = time from pressing Enter to a change on screen. It
> takes several seconds, and is same on repeated runs. There are no
> network disks (although machine is tcp/ip connected).
>
> The machine is a 486-66 16meg which has been used for Linux for some
> time, but only recently for testing Win-95. No special hardware other
> than a Kingston ethernet board. IDE CDROM, no SCSI, S3-801 video at
> 640x480x256.
>
> less works fine on Win-3.1 (on a different machine), and from the
> Linux dosemu environment (with DOS 5) on the Win-95 machine.
>
> I thought perhaps this was a known bug. I'll look for another
> Win-95 machine for testing. Thanks for your note.
I use less all day long on Windows 95 and Windows 3.1 machines and the
response has always been instantaneous.
To try to solve your problem, I would list out ALL the tasks your
computer has to perform between the time you pressed ENTER and the time
the screen change occurs:
1. Parse the command line - Did you issue "less *" in a directory with
20 million files?
2. Find the executable - Do you have CD-ROM directories in front of your
DJGPP directory in your PATH? Especially CD-ROM directories on the
outer rim of the CD.
3. Get EXE information - Did you compress your drive in any way?
4. Load the program - How much free memory do you have before you
started less? Does Windows 95 need to swap some huge executables out
(like a Microsoft Exchange)?
5. DJGPP startup - Shouldn't be any problems here.
6. Getting at the file to view - How fragmented is your hard disk?
--
Weiqi Gao
weiqigao AT a DOT crl DOT com
- Raw text -