We're OT now... Re: Shared/moved Font Folder
From: Michael (G-2_at_att.net)
Date: 08/31/04
- Next message: Dave Patrick: "Re: Delete files older than X days old."
- Previous message: Gary G. Little: "Re: File is missing or corrupt ERROR message on startup."
- Next in thread: Ndi: "Re: We're OT now... Re: Shared/moved Font Folder"
- Reply: Ndi: "Re: We're OT now... Re: Shared/moved Font Folder"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 31 Aug 2004 13:13:52 GMT
Jeeze, you're patient!
Ok, this is where I stand.
!!!!!!!!!!!!!!Excuse my top posting...
I took a spare drive, formatted a 200 meg FAT partition as a primary. (I
don't want windows---only DOS) Then I used Drive Copy to move the old
C:(W2k) and D: (stuff) (from old hd0) to the second and third partitions
of a new drive.
When I did a check (from DOS) of that drive with Partition Magic it
advised I change the cluster size of the small Fat partition to 64k(k?)
clusters. (Now it shows as FAT 12?...) (I put ntdetect, ntldr and
boot.ini in that partition)
Anyway, W2k did boot to the "second" partition!
But looped at the logon screen (and looped and looped) odd?!---but it
was a smooth repair/re-install. Long, as usual, but w2k kept my
settings. Of course re-install moved W2k from C: to E:--smart, now all
apps from old drive D: are fine, it left D: alone (even tough I did
"place" C: and D: in their respective partitions w/Drive Copy.)
Re-install even put "empty" io.sys, msdos.sys and autoexex. in that
small FAT 12!? partition. I have no clue why and am not sure *what* type
of partiton that is?!
So, I am up and running. (I edited the boot.ini to find w3k on drive
hd1) as I didn't have the drive in the caddy while I was doing this and
re-insall gave me a new boot.ini. I figured if something bad happened,
hd1 would be out of the picture.
So, all seems to be ok---except I have yet to figure out the best way to
get Dos in the system. My original goal in the first place!
I really don't want to do another re-install---looks like I will...?
1. I don't want win98...only Dos. Is there any way to install Dos
without having to repair/reinstall w2k..it wasn't bad, settings
stayed---I hate pressing my luck!
And I don't have a burner for you CD plan...
Check this out from a proggie called Bootpart:
"To have both MS-Dos 6.22 and Windows 95 in the NT menu (forgot F4 !)
=======================================================================
The standard situation for a computer that multiboots to Windows NT,
Windows 95, or MS-Dos 6.22 is : the user selects a "Windows 95" entry
in NT menu, and, then must press F4 if he wants to boot MS-Dos 6.22.
If you don't have this situation (i.e. : you don't have both Win95 and
MS-Dos 6.22 on your system, but want to have both), see the next section.
Just enter these bootpart command :
BOOTPART DOS622 C:\BOOTSECT.622 "MS-Dos 6.22"
BOOTPART WIN95 C:\BOOTSECT.W95 "Windows 95"
BOOTPART REWRITEROOT:C:
The last line (REWRITEROOT:C:) MUST BE EXECUTED UNDER MSDOS, and moves the
MS-Dos IO.* and MSDOS.* files to the beginning of the root directory.
If you have WinNT & Win95 and you only want to add MS-Dos
=========================================================
Take an MSDos 6.22 floppy, copy the files IO.SYS, MSDOS.SYS, and
COMMAND.COM to C:\ as IO.DOS, MSDOS.DOS, and COMMAND.DOS (warning :
these files can be hidden, but you can ask File Manager or Explorer to
display hidden files). Then go to the section "To have both MS-Dos
6.22 and Windows 95 in the NT menu"
I'm back-------Seems like no re-install is necessary?
Anyway, I am a bit slow about how to actually boot to DOS from the
drive! What file(s) should/need to be in the primary? What should they
"say"?
What is the "pointer" (syntax in boot.ini)?
hDo you buy the above solution from bootpart.
Again thanks---I top posted because I took the leap and accounted for
some of what you mention below. So, everytning worked so far, I seem to
be ready to get DOS goin' but still am clueless about the placement of
dos files, what should be in boot.ini. Ideally I'd like a minimum of
DOS files in that FAT12(?!) partition with a folder for DOS elsewhere
else.
Again many thanks!
>> I'm a bid confused---I don't need a FAT 16 partition for Dos 7? (Of
>> course, it appears so as I look at this laptop (win98se) ---again, all
>> Fat32 with/DOS
There might be a confusing factor on my side, I ate too much. But aside
from that, I remember DOS 7 (W95) can "see" FAT32. You might need OSR2 or
smth. But you will go for 98 SE anyway, right?
>> If you mean booting from a floppy---I do---I have to. Again, I use so
>> many various DOS utilities, it would be nice to have them on the system
>> rather than juggling a bunch of floppies. (One floppy hold enough for
>> boot/cdrom/network support only----then I have to go to other floppies
>> for various tasks)
Right. How about NT boot loader lettting you select OS from partition 1
(FAT 2G). Select Windows 98 (from C:), but not before holding down CTRL.
This will bring up the W98 boot menu (or better yet, go for a config.sys
menu). Select command prompt only and voila, you're in DOS mode.
If you still love the floppy, go for a boot floppy that mounts the CD
in D
or something. Just do a boot floppy and nuke the config.sys to something
like:
dos=high
device=himem.sys
device=oakcdrom.sys /d:mscd001 << this is in your Windows installation
and then put mscdex.exe in your autoexec (I think it brings trouble if in
config.sys). Once there, you have your tools CD that will be in a pure dos
environment. The short-named, LOCK needing DOS. Why 100 floppies?
>> A gig sound awfully large. In this new drive I formatted 20 meg (FAT)
>> which could hold five times the DOS stuff I have...
You would need to store NT loader files, Windows 98 and some space in
order to operate W98 and (I would if I were you) some NT recovery data. Like
registry backups. Yes, on a different partition. FAT. Anybody can repair
FAT, even Norton Utilities 8. Beware of long names though.
Besides, why not have W98 at hand when you multiboot anyway? It's
definately better than the DOS CLI in times of need. Plus games :)
>> (Meaning I don't have to do nuttin?) I simply sys DOS 7 in the same
>> partition w/w2k?) Again---some repair work will need to be done since
>> w2k "must" be the last system loaded?!)
Nooooooooooooooo! :)
Emm, actually, yes, sorta. The fact is that SYS a: c: will get you a
DOS7,
a small W98 boot but IIRC it will nuke the NT Loader. Then you'll need to
repair W2000 (insert cd, repair). But I also remember there was a 9x version
that could handle NT loader and insert itself into the boot.ini, but I can't
remember which. Was it W98SE?
Best bet would be to go for 9x in the first partition and then
install/repair other W2k/XP/NT4 installations. (You only need to repair one
and restore boot.ini). Perhaps this will be a goos point to start from
scratch and have backups at hand for future use. For a W2k lifespan of over
2 years, a start-from-scratch is a nice waypoint.
>> No, the w2k's have resided in their primary partitions for some time.
>> This was an afterthought.
I meant you cant just copy D:\WINNT to E:\winnt and then switch drives,
assuming that D and E will switch and noone will notice. 'Cause they will
not. This only works with 9x. Also, inserting a drive should not bump the
drives forward.
>> I have done much research on at least 6-10 boot loaders and tried a
>> couple. All have at least a couple of drawbacks. One really screwed up
>> my partition table...I would prefer a robust version of boot.ini---but
>> obviously a multi-OS boot manager has to monkey around with the disk
>> more than an MS only solution.
NT boot loader is quite robust. I let MS handle everything. With a
listtle
help it can boot Linux, too. Which adds up to just about all significant OSs
:P
>> I think I'll see what happens with putting DOS 7 and w2k boot file in
>> that 20meg FAT 16 partition---of course my hope is that (since it will
>> move w2k up a drive letter) the w2k install disk will be able to
>> "repair" W2k (that would reside in D:\ instead of C:\).
Again, drives do not shift but in a reinstall. Ok, the drives SHOULD not
shift except for a reinstall. Mine don't.
Upgrading/repairing always kept the drives in place. Full install,
howerver, re-letter the drives.
>> Again, I have found w2k quite forgiving---the "standard" repair is
>> limited, but if one has the time, the setup disk can fix about anything
>> and keep what you started out with. In fact, it does everything
>> possible to stop one from re-installing!
Advanced tools are available, like user migration settings, full system
backup and such that will allow more than the system files to be migrated.
If you back up current user software settings and classes, retain Program
files and backup/restore contents of Docs and Sett\Administrator (need to
push and pop data, otherwise you end up with Administrator.000 or
Administrator.computername and that is as annoying as having 4 minute
uptime), you should be able to restore most of the settings through a fresh
install and have over 90% of your old programs working.
-- Andrei "Ndi" Dobrin Brainbench MVP www.Brainbench.com
- Next message: Dave Patrick: "Re: Delete files older than X days old."
- Previous message: Gary G. Little: "Re: File is missing or corrupt ERROR message on startup."
- Next in thread: Ndi: "Re: We're OT now... Re: Shared/moved Font Folder"
- Reply: Ndi: "Re: We're OT now... Re: Shared/moved Font Folder"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
