autoexec.bat og config.sys

Har du prøvet \"edit config.sys\" i kommandoprompten?

dual boot ligger i Linux så vidt jeg ved på en partion for sig selv, det gør det også under OS/2, det er en lille partion på 1-2 mB

Nop... Har lige selv testet, og det virker ikke

prøv via dos-promten at skrive \"edit autoexec.bat\"
eller \"edit config.sys\"
der kan du komme ind i filerne og se hvad der nu engang er af spændene ting :)

hvis du vil af med den linux starter op når du tænder computeren skal du ude i dos\'en skrive \"fdisk mbr\"

håber du kan bruge dette til noget.

Har også prøvet edit i kommandoprompten og har ligesom runberg fundet ud af det ikke virker.

brixz --- Hvad er det lige præcis \"fdisk mbr\" gør??? Jeg er ikke interesseret i at formatere mit c-drev da windows jo er installeret her.

Se http://www.cc.ic.ac.uk/helpdesk/apriori/15.1950.html

/Rob

Teksten lyder:

How to Remove LiLo on an NT Machine
DocId:15.1950
DocLastModDate:14 Dec 2000 11:22
DocShortDesc:How to Remove LiLo on an NT Machine
DocLongDesc:
Problem: How to Remove LiLo on an NT Machine

User has set up a PC as a dual bootable system with Linux and NT.
Windows NT was set up as the default operating system.

At some stage the Linux partition has been deleted, but the Lilo
boot process still worked well. The filespace was incorporated into
the NT file space.

Now the machine won\'t boot. It just display LI and then stops.
What can be done.

Response: Recreate the Master boot record.

When a PC starts up, the Bios will first do some tasks, like count
how much memory is available, and usually now allow you so do some
configuration. It will then try to \"boot\" from some disk.

This involves reading the Master boot record, which contains the disk
address where a boot code can be found. At this stage the PC is in
8086 mode, and the address is exspected to be in terms of head, cylinder,
sector, and length (in sectors). The PC executes the information found
at that place on the disk. (N.B. this is what some boot viruses exploit
to get run at boot time.) This boot code will look then for config.sys,
msdos.sys, io.sys etc. When you install lilo, this boot code understands
a Linux file system and looks for a kernel.

By incorporating the disk space into the NT file space, there is no
longer a file system that keeps this space inviolate, and at some stage
the boot code is rewritten and will no longer work. Thus the machine will
not boot.

You should proceed as follows:

  o  boot the system from an MS-DOS 6.0 or similar floppy disk

  o  execute an \"fdisk /mbr\" command

Early versions of DOS would point the master boot record to load
a fixed area of the disk, and newer versions still follow that and
keep some boot code in that place, even though it is no longer the
actual system you see finally running on the machine.

  o  boot again from the hard disk, it will probably get into NT

  o  run the disk administrator and re-write the disk label (it asks
      you when it starts up)

  o  hope for the best


/Rob

Denne her er nok bedre:

http://support.microsoft.com/support/kb/articles/Q171/6/11.ASP


    All Products  |  Support  |  Search  |  microsoft.com Home   
 

  Support Home  |  Find a Solution  |  Request Support  |  Custom Support  | 

All Products  |  Support  |  Search  |  Microsoft.com Guide  Home  |  Find a Solution  |  Request Support  |  Custom Support

--------------------------------------------------------------------------------
Downloads
MS Product Catalog
Microsoft Accessibility

--------------------------------------------------------------------------------
Servers
Developer Tools
Office
Windows
MSN

--------------------------------------------------------------------------------
Knowledge Base
Product Support Options
Service Partner Referrals

--------------------------------------------------------------------------------
Search Microsoft.com
MSN Web Search

--------------------------------------------------------------------------------
Microsoft.com Home
MSN Home

--------------------------------------------------------------------------------
Contact Us
Events
Newsletters
Profile Center
Training & Certification
Free E-mail Account

--------------------------------------------------------------------------------
Support Home
microsoft.com

--------------------------------------------------------------------------------
Search Knowledge Base
Search Wizard
FAQs by Product
Find Software Downloads
Newsgroups

--------------------------------------------------------------------------------
Get Help From Microsoft
Check Status of Your Pending Question
Call Microsoft Support
Removing the Linux LILO Boot Manager
Formal product support for Microsoft Windows XP will be available from Microsoft beginning October 25, 2001. Until then, you can consult with your counterparts, peers, and Microsoft Most Valuable Professionals (MVPs) by using our online newsgroups. Access to the Microsoft newsgroups is available from the following Microsoft Web site:
http://communities.microsoft.com/newsgroups/default.asp

--------------------------------------------------------------------------------
The information in this article applies to:

Microsoft Windows XP Home Edition
Microsoft Windows XP Professional
Microsoft Windows 2000 Professional
Microsoft Windows 2000 Server
Microsoft Windows 2000 Advanced Server
Microsoft Windows 2000 Datacenter Server
Microsoft Windows NT Workstation versions 3.5, 3.51, 4.0
Microsoft Windows NT Server versions 3.50, 3.51, 4.0

--------------------------------------------------------------------------------


SUMMARY
This article describes how to remove the LILO boot manager from the Master Boot Record (MBR).



MORE INFORMATION
When Linux is installed on your computer, it allows a dual boot by loading a boot manager called LILO directly into the MBR. To remove LILO, perform the following steps:

If Linux is Still Installed
Run LILO with either the -u or -U switch. The device name has to be the second parameter.
For example, if LILO is installed to the MBR of the master drive on the primary IDE controller, the command would be:


lilo -u /dev/hda

Where dev is the device directory, hd indicates an IDE hard drive, and a indicates the master on the primary IDE channel.


To use with a SCSI drive, run lilo -u /dev/sda where sd indicates a SCSI drive and a indicates the first drive in the chain.


If there are multiple partitions on the drive, indicate the partition number for LILO to uninstall by adding a number corresponding to the partition number on the drive, starting the count at 1 (not 0). For example,


lilo -u /dev/sda1

removes LILO from the first SCSI drive, first partition.

NOTE: The sda indicator has nothing to do with the SCSI ID number.
If Linux is Not Installed
NOTE: The following procedure is not supported by Microsoft and is done strictly at the discretion of the user. Microsoft assumes no liability for lost or corrupted data. This procedure should be done only as a last resort.

IMPORTANT: fdisk /mbr removes the disk signature from the MBR. If this drive is a member of a Windows fault tolerance set, it will no longer be recognized as a member of that set.
Use the Windows Resource Kit Disksave.exe utility to back up the MBR and boot sector.


Boot to MS-DOS and type the following:


fdisk /mbr
Restart your computer.


The computer should start normally. If the computer does not start normally, boot to an MS-DOS boot disk and run Disksave again to restore the MBR and boot sector. You may also need to run Fdisk to specify the new active partition to boot.

The only difference between the two switches is that -u checks the time stamp on the current MBR and the backed-up one, whereas -U does not check the time stamp at all.

The third-party products discussed here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products\' performance or reliability.


/Rob

øhh den renser ja hmm lad hellere være med at gøre det og brug den kun som sidste udvej. det var bare den jeg brugte da jeg ville af med linux

fdisk /mbr virker fint, den skal bare fyres af når du har bootet på en boot disk, den laver en \"orginal\" microsoft boot record, og det gør så at maskinen booter i windows uden at komme op med lilo først.

-- popeye_2k