Re: Accessing DOS & BIOS

From: Ernie (1racabli_at_maine.rr.com)
Date: 01/17/05


Date: Mon, 17 Jan 2005 19:54:24 GMT

To all who responded to my "Accessing DOS & BIOS" "Thanks".

To all who responded to my "Accessing DOS & BOS" "Thanks".

Many of you asked my why I needed to access DOS and the BIOS. Fair
question.

When I attempted to use "Drive Image 2002" I get an "Error #3, Not enough
memory" message when trying to copy to disk. I checked with
Symantec/support/powerquest and got a litany of suggestions which included
"DOS and BIOS" and here they are:

"Error 3 Not enough memory"

Situation:
You see the message "Error 3 Not enough memory."

Solution:
Error 3 indicates that the Symantec program does not have enough
conventional memory available to complete an operation. You can determine
how much conventional memory is available by typing chkdsk after booting to
DOS.

In the output, the Bytes Free value should be a number larger than 585 KB.
If it is not, then there is probably not enough conventional memory
available to run your Symantec program.

To resolve the problem make more conventional memory available. To do this,
read the following list of suggestions and the ones that apply to your
computer.

  a.. Upgrade to the latest version of PartitionMagic, Drive Image, or
DriveCopy.
  b.. Defragment your hard disks.
  c.. Make sure that any BIOS-level virus protection is disabled.
  d.. Disable the BIOS-level memory hole setting if you are not using
peripherals that require the setting to be enabled.
  This BIOS setting is often called "Memory Hole" or "Memory Hole at."
Basically, this setting reserves a space in system memory for an ISA adapter
ROM. When this space is reserved in memory, that memory cannot be cached. In
most cases, this setting is unnecessary unless you have a special card that
requires the BIOS to reserve the memory at 15 MB. Peripherals that need to
use this area of memory usually include information regarding this
requirement in their user guides.
  e.. Boot your computer to a DOS disk that does not contain a Config.sys or
Autoexec.bat file, and then run the PowerQuest program.
  f.. Create a minimal DOS boot disk and run the Symantec product from the
command line with the /nss switch.
  Instructions for creating a minimal DOS boot disk are in the Technical
Information section of this document.
  g.. Add more RAM to your computer.
  Flaws in physical memory can also cause this message to occur. Try
changing the RAM out with equivalent physical memory cards.
  Also, if you are using SIMMs instead of DIMMs, make sure that the pairs
are made up of the same brand, size, and type of memory modules.
  h.. Rename the program's .exe file to use a .old extension and then rename
the .ovl file to .exe.
  i.. On some computers, if the BIOS-level settings for shadowing of caching
are enabled, conventional memory resources may not be sufficient to run your
Symantec product.
  To resolve this, temporarily disable shadowing or caching in the BIOS
configuration, and then re-enable it after you are finished running the
program.
  j.. If you are using a FAT32 partition, change the cluster size of the
FAT32 partition from 4 KB to 8 KB.

Technical Information:
To create a minimal DOS boot disk

  1.. Insert a blank floppy disk into the floppy disk drive.
  2.. At a DOS prompt, type the following command.

  format a: /s
  3.. Press Enter.
  4.. Change to drive A.
  5.. At the DOS prompt, type the following command:

  edit config.sys
  6.. Press Enter.
  7.. Add the following lines to the Config.sys file:

  DEVICE=C:\WINDOW\HIMEM.SYS
  DOS=HIGH
  DEVICE=C:\WINDOWS
  8.. Save the file to drive A.
  9.. Exit the editor.
  10.. If your diskette is not compressed, type the following commands,
pressing Enter after each command:

  attrib -r -h -s
  del *.bin

"Malke" <malke@nospoonnotreally.com> wrote in message
news:eqUnIcL$EHA.2580@TK2MSFTNGP15.phx.gbl...
> Ernie wrote:
>
>> How does one access DOS (not MS/DOS) and the BIOS in WinXP?
>
> There is no DOS in XP to access. To get to a command prompt, go to
> Start>Run and type:
>
> cmd [enter]
>
> This will get you the command prompt.
>
> Accessing a computer's BIOS has nothing to do with the operating system.
> You will need to press some key or combination of keys as the computer
> is starting. The specific key to press depends on what BIOS is used
> with your motherboard. Normally when the computer first starts there
> will be a message at the bottom of the screen that says something like,
> "Press DEL to enter Setup" and that will get you into the BIOS. Or look
> in the manual that came with your computer.
>
> What are you trying to do? If you don't know what you're doing (and
> without meaning to be hurtful, it doesn't sound like you do) you can
> seriously mess up your computer by changing BIOS settings.
>
> Malke
> --
> MS MVP - Windows Shell/User
> Elephant Boy Computers
> www.elephantboycomputers.com
> "Don't Panic!"



Relevant Pages

  • Re: Accessing DOS & BIOS
    ... Drive Image 2002 will NOT run under XP. ... > Many of you asked my why I needed to access DOS and the BIOS. ... > memory" message when trying to copy to disk. ...
    (microsoft.public.windowsxp.general)
  • Re: question about system memory space mapping
    ... bios information is copied from mainboard to bios ... > buffer areaand output video signal to monitor. ... of the memory on the video card is placed here instead. ... depending on the version DOS requires between 64KB and 256KB to run. ...
    (comp.lang.asm.x86)
  • Re: Accessing DOS & BIOS
    ... > Many of you asked my why I needed to access DOS and the BIOS. ... > conventional memory available to complete an operation. ... > Instructions for creating a minimal DOS boot disk are in the Technical ... At a DOS prompt, type the following command. ...
    (microsoft.public.windowsxp.general)
  • Re: Boot Disk
    ... loading into upper memory has been around since ME came out. ... > I need to create a DOS boot disk that loads the DOS network redirectors... ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: How to call bios function in WDM Driver??
    ... >> You are not in DOS, where the BIOS is in memory some where in the ... heavens. ...
    (microsoft.public.development.device.drivers)

Quantcast