Ticket #98 (closed defect: invalid)

Opened 4 years ago

Last modified 3 years ago

Nvda is slow at starting up.

Reported by: kenny11 Owned by: kenny11
Priority: major Milestone: 2009.1
Component: Core Version: development
Keywords: Cc:
Operating system: Blocked by:
Blocking:

Description

When nvda starts i get a error sound before it starts up.

Attachments

nvda.log Download (42 bytes) - added by kenny11 4 years ago.
Contains the error information.

Change History

comment:1 Changed 4 years ago by jteh

Please provide more information.

  • Define "slow". How long does it take to start?
  • What are your computer's specs?
  • Are you starting from an installed copy, a USB key or a CD?
  • If you are running a snapshot, what version?
  • Please include the error from your log file or attach the file to this ticket. To access the log file:
    1. Once NVDA starts, press NVDA+n.
    2. Select Tools -> View log.
    3. Either copy and paste the error or select File -> Save As and save the log to a file.

comment:2 Changed 4 years ago by jteh

  • Keywords When nvda starts i get an error before it starts talking here is the log file attached below. removed
  • Priority changed from critical to major

comment:3 Changed 4 years ago by jteh

Reporter notes that NVDA takes 5 seconds to start.

Please comment on this ticket, rather than opening another. I've deleted ticket #99 which you just opened.

Changed 4 years ago by kenny11

Contains the error information.

comment:4 Changed 4 years ago by jteh

This is not an error; it is a warning. Only errors cause the error sound, so you must not have received the error sound in this case. Please see my earlier comment regarding other questions you should answer.

comment:5 Changed 3 years ago by jteh

  • Status changed from new to closed
  • Resolution set to invalid

The "Slow starting core" message is not an error, so it would not have been the cause of an exception (error sound). If speed is the issue, this will depend on many factors. Startup speed does not seem to be an issue for most users and the reporter hasn't followed up on this, so closing as invalid.

Note: See TracTickets for help on using tickets.