Archived from groups: microsoft.public.win98.gen_discussion (More info?)
During bootup, the wrong autoexec file is read. Why?
During bootup, the wrong autoexec file is read. Why?
-
AMD dishes out more Zen 5 details — compact core is 25% smaller than the normal core, new SoC and chip architecture with dual CCXs
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
G
Guest
Guest
Archived from groups: microsoft.public.win98.gen_discussion (More info?)
The only autoexec file that should run is Autoexec.bat. What makes you
think that some other autoexec. is running?
--
Gary S. Terhune
MS MVP Shell/User
http://www.grystmill.com/articles/cleanboot.htm
http://www.grystmill.com/articles/security.htm
"b11_" <b11@discussions.microsoft.com> wrote in message
news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
> During bootup, the wrong autoexec file is read. Why?
The only autoexec file that should run is Autoexec.bat. What makes you
think that some other autoexec. is running?
--
Gary S. Terhune
MS MVP Shell/User
http://www.grystmill.com/articles/cleanboot.htm
http://www.grystmill.com/articles/security.htm
"b11_" <b11@discussions.microsoft.com> wrote in message
news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
> During bootup, the wrong autoexec file is read. Why?
G
Guest
Guest
Archived from groups: microsoft.public.win98.gen_discussion (More info?)
I don't believe the autoexec.bat file is read during a safe mode boot.
--
Regards
Ron Badour, MS MVP for W98
Tips: http://home.satx.rr.com/badour
Knowledge Base Info:
http://support.microsoft.com/default.aspx?pr=kbinfo
"b11_" <b11@discussions.microsoft.com> wrote in message
news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
> During bootup, the wrong autoexec file is read. Why?
I don't believe the autoexec.bat file is read during a safe mode boot.
--
Regards
Ron Badour, MS MVP for W98
Tips: http://home.satx.rr.com/badour
Knowledge Base Info:
http://support.microsoft.com/default.aspx?pr=kbinfo
"b11_" <b11@discussions.microsoft.com> wrote in message
news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
> During bootup, the wrong autoexec file is read. Why?
G
Guest
Guest
Archived from groups: microsoft.public.win98.gen_discussion (More info?)
"b11_" <b11@discussions.microsoft.com> wrote in message
news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
> During bootup, the wrong autoexec file is read. Why?
1. During bootup, the system reads the first AUTOEXEC
file encountered in the filepath. This is usually
c:\windows\autoexec.bat
2. Standard Win98 requires no AUTOEXEC file.
Try booting without it and without CONFIG.SYS
(rename both) and see if that solves your problem.
--
Don Phillipson
Carlsbad Springs
(Ottawa, Canada)
"b11_" <b11@discussions.microsoft.com> wrote in message
news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
> During bootup, the wrong autoexec file is read. Why?
1. During bootup, the system reads the first AUTOEXEC
file encountered in the filepath. This is usually
c:\windows\autoexec.bat
2. Standard Win98 requires no AUTOEXEC file.
Try booting without it and without CONFIG.SYS
(rename both) and see if that solves your problem.
--
Don Phillipson
Carlsbad Springs
(Ottawa, Canada)
G
Guest
Guest
Archived from groups: microsoft.public.win98.gen_discussion (More info?)
During a _normal_ boot, I accidentally discovered that a different autoexec
file( a backup autoexec I think) was being read.
____________________________________________________________________
"Don Phillipson" wrote:
> "b11_" <b11@discussions.microsoft.com> wrote in message
> news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
>
> > During bootup, the wrong autoexec file is read. Why?
>
> 1. During bootup, the system reads the first AUTOEXEC
> file encountered in the filepath. This is usually
> c:\windows\autoexec.bat
>
> 2. Standard Win98 requires no AUTOEXEC file.
> Try booting without it and without CONFIG.SYS
> (rename both) and see if that solves your problem.
>
> --
> Don Phillipson
> Carlsbad Springs
> (Ottawa, Canada)
>
>
>
During a _normal_ boot, I accidentally discovered that a different autoexec
file( a backup autoexec I think) was being read.
____________________________________________________________________
"Don Phillipson" wrote:
> "b11_" <b11@discussions.microsoft.com> wrote in message
> news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
>
> > During bootup, the wrong autoexec file is read. Why?
>
> 1. During bootup, the system reads the first AUTOEXEC
> file encountered in the filepath. This is usually
> c:\windows\autoexec.bat
>
> 2. Standard Win98 requires no AUTOEXEC file.
> Try booting without it and without CONFIG.SYS
> (rename both) and see if that solves your problem.
>
> --
> Don Phillipson
> Carlsbad Springs
> (Ottawa, Canada)
>
>
>
G
Guest
Guest
Archived from groups: microsoft.public.win98.gen_discussion (More info?)
More detail on how you discovered this would be helpful, what you saw,
etc.
A list of all "autoexec" files on your machine would also help.
--
Gary S. Terhune
MS MVP Shell/User
http://www.grystmill.com/articles/cleanboot.htm
http://www.grystmill.com/articles/security.htm
"b11_" <b11@discussions.microsoft.com> wrote in message
news:64F7628B-016A-479B-8BEE-852D77DEB113@microsoft.com...
> During a _normal_ boot, I accidentally discovered that a different
> autoexec
> file( a backup autoexec I think) was being read.
> ____________________________________________________________________
> "Don Phillipson" wrote:
>
>> "b11_" <b11@discussions.microsoft.com> wrote in message
>> news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
>>
>> > During bootup, the wrong autoexec file is read. Why?
>>
>> 1. During bootup, the system reads the first AUTOEXEC
>> file encountered in the filepath. This is usually
>> c:\windows\autoexec.bat
>>
>> 2. Standard Win98 requires no AUTOEXEC file.
>> Try booting without it and without CONFIG.SYS
>> (rename both) and see if that solves your problem.
>>
>> --
>> Don Phillipson
>> Carlsbad Springs
>> (Ottawa, Canada)
>>
>>
>>
More detail on how you discovered this would be helpful, what you saw,
etc.
A list of all "autoexec" files on your machine would also help.
--
Gary S. Terhune
MS MVP Shell/User
http://www.grystmill.com/articles/cleanboot.htm
http://www.grystmill.com/articles/security.htm
"b11_" <b11@discussions.microsoft.com> wrote in message
news:64F7628B-016A-479B-8BEE-852D77DEB113@microsoft.com...
> During a _normal_ boot, I accidentally discovered that a different
> autoexec
> file( a backup autoexec I think) was being read.
> ____________________________________________________________________
> "Don Phillipson" wrote:
>
>> "b11_" <b11@discussions.microsoft.com> wrote in message
>> news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
>>
>> > During bootup, the wrong autoexec file is read. Why?
>>
>> 1. During bootup, the system reads the first AUTOEXEC
>> file encountered in the filepath. This is usually
>> c:\windows\autoexec.bat
>>
>> 2. Standard Win98 requires no AUTOEXEC file.
>> Try booting without it and without CONFIG.SYS
>> (rename both) and see if that solves your problem.
>>
>> --
>> Don Phillipson
>> Carlsbad Springs
>> (Ottawa, Canada)
>>
>>
>>
G
Guest
Guest
Archived from groups: microsoft.public.win98.gen_discussion (More info?)
You need to supply a lot more detailed information regarding exactly what "autoexec"
files you have and which is being read. Additionally, all files have a file
extension...text files use .txt, Word documents use .doc, and so forth. A batch
file uses the .bat extension. Click Start> Settings> Folder Options> View tab, set
the Hidden Files setting to "Show All Files", and uncheck the box for "Hide file
extensions for known files types", then click OK. This will allow you to see, and
report back, with what file extensions these "autoexec" files have.
See here:
http://home.mindspring.com/~glee29/images/f-opt98.jpg
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/goodpost.htm
"b11_" <b11@discussions.microsoft.com> wrote in message
news:64F7628B-016A-479B-8BEE-852D77DEB113@microsoft.com...
> During a _normal_ boot, I accidentally discovered that a different autoexec
> file( a backup autoexec I think) was being read.
> ____________________________________________________________________
> "Don Phillipson" wrote:
>
> > "b11_" <b11@discussions.microsoft.com> wrote in message
> > news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
> >
> > > During bootup, the wrong autoexec file is read. Why?
> >
> > 1. During bootup, the system reads the first AUTOEXEC
> > file encountered in the filepath. This is usually
> > c:\windows\autoexec.bat
> >
> > 2. Standard Win98 requires no AUTOEXEC file.
> > Try booting without it and without CONFIG.SYS
> > (rename both) and see if that solves your problem.
> >
> > --
> > Don Phillipson
> > Carlsbad Springs
> > (Ottawa, Canada)
> >
> >
> >
You need to supply a lot more detailed information regarding exactly what "autoexec"
files you have and which is being read. Additionally, all files have a file
extension...text files use .txt, Word documents use .doc, and so forth. A batch
file uses the .bat extension. Click Start> Settings> Folder Options> View tab, set
the Hidden Files setting to "Show All Files", and uncheck the box for "Hide file
extensions for known files types", then click OK. This will allow you to see, and
report back, with what file extensions these "autoexec" files have.
See here:
http://home.mindspring.com/~glee29/images/f-opt98.jpg
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.org/goodpost.htm
"b11_" <b11@discussions.microsoft.com> wrote in message
news:64F7628B-016A-479B-8BEE-852D77DEB113@microsoft.com...
> During a _normal_ boot, I accidentally discovered that a different autoexec
> file( a backup autoexec I think) was being read.
> ____________________________________________________________________
> "Don Phillipson" wrote:
>
> > "b11_" <b11@discussions.microsoft.com> wrote in message
> > news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
> >
> > > During bootup, the wrong autoexec file is read. Why?
> >
> > 1. During bootup, the system reads the first AUTOEXEC
> > file encountered in the filepath. This is usually
> > c:\windows\autoexec.bat
> >
> > 2. Standard Win98 requires no AUTOEXEC file.
> > Try booting without it and without CONFIG.SYS
> > (rename both) and see if that solves your problem.
> >
> > --
> > Don Phillipson
> > Carlsbad Springs
> > (Ottawa, Canada)
> >
> >
> >
G
Guest
Guest
Archived from groups: microsoft.public.win98.gen_discussion (More info?)
"b11_" <b11@discussions.microsoft.com> wrote in message news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
> During bootup, the wrong autoexec file is read. Why?
Please repost with more information, including why you think a
different file is being processed.
Ben
"b11_" <b11@discussions.microsoft.com> wrote in message news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
> During bootup, the wrong autoexec file is read. Why?
Please repost with more information, including why you think a
different file is being processed.
Ben
G
Guest
Guest
Archived from groups: microsoft.public.win98.gen_discussion (More info?)
During bootup, the autoexec.tsh file is read, not the Autoexec.bat.
______________________________________
"Ben Myers" wrote:
> "b11_" <b11@discussions.microsoft.com> wrote in message news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
> > During bootup, the wrong autoexec file is read. Why?
>
> Please repost with more information, including why you think a
> different file is being processed.
>
> Ben
>
>
During bootup, the autoexec.tsh file is read, not the Autoexec.bat.
______________________________________
"Ben Myers" wrote:
> "b11_" <b11@discussions.microsoft.com> wrote in message news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
> > During bootup, the wrong autoexec file is read. Why?
>
> Please repost with more information, including why you think a
> different file is being processed.
>
> Ben
>
>
G
Guest
Guest
Archived from groups: microsoft.public.win98.gen_discussion (More info?)
Autoexec.bat is renamed to Autoexec.tsh by Windows when you uncheck
Autoexec.bat in "START, Run, MSConfig, General tab". In that case, there
is no Autoexec.bat to run at boot-- & neither will Autoexec.tsh be run.
That was the purpose of renaming it.
When it is checked again, the .tsh will become a .bat again after a
reboot. I think, though, every individual line inside Autoexec.bat that
may have been unchecked in Autoexec.bat will be checked now. So, watch
that!
--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR
pcrrcp@netzero.net
"b11_" <b11@discussions.microsoft.com> wrote in message
news:FADB56EF-EE38-4C48-B338-93D375E3F3F6@microsoft.com...
| During bootup, the autoexec.tsh file is read, not the Autoexec.bat.
| ______________________________________
| "Ben Myers" wrote:
|
| > "b11_" <b11@discussions.microsoft.com> wrote in message
news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
| > > During bootup, the wrong autoexec file is read. Why?
| >
| > Please repost with more information, including why you think a
| > different file is being processed.
| >
| > Ben
| >
| >
Autoexec.bat is renamed to Autoexec.tsh by Windows when you uncheck
Autoexec.bat in "START, Run, MSConfig, General tab". In that case, there
is no Autoexec.bat to run at boot-- & neither will Autoexec.tsh be run.
That was the purpose of renaming it.
When it is checked again, the .tsh will become a .bat again after a
reboot. I think, though, every individual line inside Autoexec.bat that
may have been unchecked in Autoexec.bat will be checked now. So, watch
that!
--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR
pcrrcp@netzero.net
"b11_" <b11@discussions.microsoft.com> wrote in message
news:FADB56EF-EE38-4C48-B338-93D375E3F3F6@microsoft.com...
| During bootup, the autoexec.tsh file is read, not the Autoexec.bat.
| ______________________________________
| "Ben Myers" wrote:
|
| > "b11_" <b11@discussions.microsoft.com> wrote in message
news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
| > > During bootup, the wrong autoexec file is read. Why?
| >
| > Please repost with more information, including why you think a
| > different file is being processed.
| >
| > Ben
| >
| >
G
Guest
Guest
Archived from groups: microsoft.public.win98.gen_discussion (More info?)
Correction: When you uncheck Autoexec.bat in MSCONFIG, Autoexec.bat is
renamed to Autoexec.tsh, but a *new* Autoexec.bat is created containing
nothing but comments that explain about Autoexec.tsh being the backup. There
*is* an Autoexec.bat, but it's toothless.
--
Gary S. Terhune
MS-MVP Shell/User
"PCR" <pcrrcp@netzero.net> wrote in message
news:O9GJyUcqFHA.3480@tk2msftngp13.phx.gbl...
> Autoexec.bat is renamed to Autoexec.tsh by Windows when you uncheck
> Autoexec.bat in "START, Run, MSConfig, General tab". In that case, there
> is no Autoexec.bat to run at boot-- & neither will Autoexec.tsh be run.
> That was the purpose of renaming it.
>
> When it is checked again, the .tsh will become a .bat again after a
> reboot. I think, though, every individual line inside Autoexec.bat that
> may have been unchecked in Autoexec.bat will be checked now. So, watch
> that!
>
>
> --
> Thanks or Good Luck,
> There may be humor in this post, and,
> Naturally, you will not sue,
> should things get worse after this,
> PCR
> pcrrcp@netzero.net
> "b11_" <b11@discussions.microsoft.com> wrote in message
> news:FADB56EF-EE38-4C48-B338-93D375E3F3F6@microsoft.com...
> | During bootup, the autoexec.tsh file is read, not the Autoexec.bat.
> | ______________________________________
> | "Ben Myers" wrote:
> |
> | > "b11_" <b11@discussions.microsoft.com> wrote in message
> news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
> | > > During bootup, the wrong autoexec file is read. Why?
> | >
> | > Please repost with more information, including why you think a
> | > different file is being processed.
> | >
> | > Ben
> | >
> | >
>
>
Correction: When you uncheck Autoexec.bat in MSCONFIG, Autoexec.bat is
renamed to Autoexec.tsh, but a *new* Autoexec.bat is created containing
nothing but comments that explain about Autoexec.tsh being the backup. There
*is* an Autoexec.bat, but it's toothless.
--
Gary S. Terhune
MS-MVP Shell/User
"PCR" <pcrrcp@netzero.net> wrote in message
news:O9GJyUcqFHA.3480@tk2msftngp13.phx.gbl...
> Autoexec.bat is renamed to Autoexec.tsh by Windows when you uncheck
> Autoexec.bat in "START, Run, MSConfig, General tab". In that case, there
> is no Autoexec.bat to run at boot-- & neither will Autoexec.tsh be run.
> That was the purpose of renaming it.
>
> When it is checked again, the .tsh will become a .bat again after a
> reboot. I think, though, every individual line inside Autoexec.bat that
> may have been unchecked in Autoexec.bat will be checked now. So, watch
> that!
>
>
> --
> Thanks or Good Luck,
> There may be humor in this post, and,
> Naturally, you will not sue,
> should things get worse after this,
> PCR
> pcrrcp@netzero.net
> "b11_" <b11@discussions.microsoft.com> wrote in message
> news:FADB56EF-EE38-4C48-B338-93D375E3F3F6@microsoft.com...
> | During bootup, the autoexec.tsh file is read, not the Autoexec.bat.
> | ______________________________________
> | "Ben Myers" wrote:
> |
> | > "b11_" <b11@discussions.microsoft.com> wrote in message
> news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
> | > > During bootup, the wrong autoexec file is read. Why?
> | >
> | > Please repost with more information, including why you think a
> | > different file is being processed.
> | >
> | > Ben
> | >
> | >
>
>
G
Guest
Guest
Archived from groups: microsoft.public.win98.gen_discussion (More info?)
Autoexec.tsh is a backup file created by msconfig when the
autoexec.bat file is disabled. If you use msconfig to modify
autoexec.bat, I suggest you leave this file in place. If not,
it can be renamed or deleted.
Ben
"b11_" <b11@discussions.microsoft.com> wrote in message news:FADB56EF-EE38-4C48-B338-93D375E3F3F6@microsoft.com...
> During bootup, the autoexec.tsh file is read, not the Autoexec.bat.
> ______________________________________
> "Ben Myers" wrote:
>
> > "b11_" <b11@discussions.microsoft.com> wrote in message news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
> > > During bootup, the wrong autoexec file is read. Why?
> >
> > Please repost with more information, including why you think a
> > different file is being processed.
> >
> > Ben
> >
> >
Autoexec.tsh is a backup file created by msconfig when the
autoexec.bat file is disabled. If you use msconfig to modify
autoexec.bat, I suggest you leave this file in place. If not,
it can be renamed or deleted.
Ben
"b11_" <b11@discussions.microsoft.com> wrote in message news:FADB56EF-EE38-4C48-B338-93D375E3F3F6@microsoft.com...
> During bootup, the autoexec.tsh file is read, not the Autoexec.bat.
> ______________________________________
> "Ben Myers" wrote:
>
> > "b11_" <b11@discussions.microsoft.com> wrote in message news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
> > > During bootup, the wrong autoexec file is read. Why?
> >
> > Please repost with more information, including why you think a
> > different file is being processed.
> >
> > Ben
> >
> >
G
Guest
Guest
Archived from groups: microsoft.public.win98.gen_discussion (More info?)
Thanks. Yes, perhaps I did see that once for one of the files. Yes, it's
a reminder of what one has done. I will remember this on the day I make
a Master Post about it! Thanks.
--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR
pcrrcp@netzero.net
"Gary S. Terhune" <grystnews@mvps.org> wrote in message
news:%23XqzOncqFHA.3064@TK2MSFTNGP15.phx.gbl...
| Correction: When you uncheck Autoexec.bat in MSCONFIG, Autoexec.bat is
| renamed to Autoexec.tsh, but a *new* Autoexec.bat is created
containing
| nothing but comments that explain about Autoexec.tsh being the backup.
There
| *is* an Autoexec.bat, but it's toothless.
|
| --
| Gary S. Terhune
| MS-MVP Shell/User
|
| "PCR" <pcrrcp@netzero.net> wrote in message
| news:O9GJyUcqFHA.3480@tk2msftngp13.phx.gbl...
| > Autoexec.bat is renamed to Autoexec.tsh by Windows when you uncheck
| > Autoexec.bat in "START, Run, MSConfig, General tab". In that case,
there
| > is no Autoexec.bat to run at boot-- & neither will Autoexec.tsh be
run.
| > That was the purpose of renaming it.
| >
| > When it is checked again, the .tsh will become a .bat again after a
| > reboot. I think, though, every individual line inside Autoexec.bat
that
| > may have been unchecked in Autoexec.bat will be checked now. So,
watch
| > that!
| >
| >
| > --
| > Thanks or Good Luck,
| > There may be humor in this post, and,
| > Naturally, you will not sue,
| > should things get worse after this,
| > PCR
| > pcrrcp@netzero.net
| > "b11_" <b11@discussions.microsoft.com> wrote in message
| > news:FADB56EF-EE38-4C48-B338-93D375E3F3F6@microsoft.com...
| > | During bootup, the autoexec.tsh file is read, not the
Autoexec.bat.
| > | ______________________________________
| > | "Ben Myers" wrote:
| > |
| > | > "b11_" <b11@discussions.microsoft.com> wrote in message
| > news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
| > | > > During bootup, the wrong autoexec file is read. Why?
| > | >
| > | > Please repost with more information, including why you think a
| > | > different file is being processed.
| > | >
| > | > Ben
| > | >
| > | >
| >
| >
|
|
Thanks. Yes, perhaps I did see that once for one of the files. Yes, it's
a reminder of what one has done. I will remember this on the day I make
a Master Post about it! Thanks.
--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR
pcrrcp@netzero.net
"Gary S. Terhune" <grystnews@mvps.org> wrote in message
news:%23XqzOncqFHA.3064@TK2MSFTNGP15.phx.gbl...
| Correction: When you uncheck Autoexec.bat in MSCONFIG, Autoexec.bat is
| renamed to Autoexec.tsh, but a *new* Autoexec.bat is created
containing
| nothing but comments that explain about Autoexec.tsh being the backup.
There
| *is* an Autoexec.bat, but it's toothless.
|
| --
| Gary S. Terhune
| MS-MVP Shell/User
|
| "PCR" <pcrrcp@netzero.net> wrote in message
| news:O9GJyUcqFHA.3480@tk2msftngp13.phx.gbl...
| > Autoexec.bat is renamed to Autoexec.tsh by Windows when you uncheck
| > Autoexec.bat in "START, Run, MSConfig, General tab". In that case,
there
| > is no Autoexec.bat to run at boot-- & neither will Autoexec.tsh be
run.
| > That was the purpose of renaming it.
| >
| > When it is checked again, the .tsh will become a .bat again after a
| > reboot. I think, though, every individual line inside Autoexec.bat
that
| > may have been unchecked in Autoexec.bat will be checked now. So,
watch
| > that!
| >
| >
| > --
| > Thanks or Good Luck,
| > There may be humor in this post, and,
| > Naturally, you will not sue,
| > should things get worse after this,
| > PCR
| > pcrrcp@netzero.net
| > "b11_" <b11@discussions.microsoft.com> wrote in message
| > news:FADB56EF-EE38-4C48-B338-93D375E3F3F6@microsoft.com...
| > | During bootup, the autoexec.tsh file is read, not the
Autoexec.bat.
| > | ______________________________________
| > | "Ben Myers" wrote:
| > |
| > | > "b11_" <b11@discussions.microsoft.com> wrote in message
| > news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
| > | > > During bootup, the wrong autoexec file is read. Why?
| > | >
| > | > Please repost with more information, including why you think a
| > | > different file is being processed.
| > | >
| > | > Ben
| > | >
| > | >
| >
| >
|
|
G
Guest
Guest
Archived from groups: microsoft.public.win98.gen_discussion (More info?)
Oh....joy...
--
Gary S. Terhune
MS-MVP Shell/User
"PCR" <pcrrcp@netzero.net> wrote in message
news:uo6GhucqFHA.1272@TK2MSFTNGP11.phx.gbl...
> Thanks. Yes, perhaps I did see that once for one of the files. Yes, it's
> a reminder of what one has done. I will remember this on the day I make
> a Master Post about it! Thanks.
>
>
> --
> Thanks or Good Luck,
> There may be humor in this post, and,
> Naturally, you will not sue,
> should things get worse after this,
> PCR
> pcrrcp@netzero.net
> "Gary S. Terhune" <grystnews@mvps.org> wrote in message
> news:%23XqzOncqFHA.3064@TK2MSFTNGP15.phx.gbl...
> | Correction: When you uncheck Autoexec.bat in MSCONFIG, Autoexec.bat is
> | renamed to Autoexec.tsh, but a *new* Autoexec.bat is created
> containing
> | nothing but comments that explain about Autoexec.tsh being the backup.
> There
> | *is* an Autoexec.bat, but it's toothless.
> |
> | --
> | Gary S. Terhune
> | MS-MVP Shell/User
> |
> | "PCR" <pcrrcp@netzero.net> wrote in message
> | news:O9GJyUcqFHA.3480@tk2msftngp13.phx.gbl...
> | > Autoexec.bat is renamed to Autoexec.tsh by Windows when you uncheck
> | > Autoexec.bat in "START, Run, MSConfig, General tab". In that case,
> there
> | > is no Autoexec.bat to run at boot-- & neither will Autoexec.tsh be
> run.
> | > That was the purpose of renaming it.
> | >
> | > When it is checked again, the .tsh will become a .bat again after a
> | > reboot. I think, though, every individual line inside Autoexec.bat
> that
> | > may have been unchecked in Autoexec.bat will be checked now. So,
> watch
> | > that!
> | >
> | >
> | > --
> | > Thanks or Good Luck,
> | > There may be humor in this post, and,
> | > Naturally, you will not sue,
> | > should things get worse after this,
> | > PCR
> | > pcrrcp@netzero.net
> | > "b11_" <b11@discussions.microsoft.com> wrote in message
> | > news:FADB56EF-EE38-4C48-B338-93D375E3F3F6@microsoft.com...
> | > | During bootup, the autoexec.tsh file is read, not the
> Autoexec.bat.
> | > | ______________________________________
> | > | "Ben Myers" wrote:
> | > |
> | > | > "b11_" <b11@discussions.microsoft.com> wrote in message
> | > news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
> | > | > > During bootup, the wrong autoexec file is read. Why?
> | > | >
> | > | > Please repost with more information, including why you think a
> | > | > different file is being processed.
> | > | >
> | > | > Ben
> | > | >
> | > | >
> | >
> | >
> |
> |
>
>
Oh....joy...
--
Gary S. Terhune
MS-MVP Shell/User
"PCR" <pcrrcp@netzero.net> wrote in message
news:uo6GhucqFHA.1272@TK2MSFTNGP11.phx.gbl...
> Thanks. Yes, perhaps I did see that once for one of the files. Yes, it's
> a reminder of what one has done. I will remember this on the day I make
> a Master Post about it! Thanks.
>
>
> --
> Thanks or Good Luck,
> There may be humor in this post, and,
> Naturally, you will not sue,
> should things get worse after this,
> PCR
> pcrrcp@netzero.net
> "Gary S. Terhune" <grystnews@mvps.org> wrote in message
> news:%23XqzOncqFHA.3064@TK2MSFTNGP15.phx.gbl...
> | Correction: When you uncheck Autoexec.bat in MSCONFIG, Autoexec.bat is
> | renamed to Autoexec.tsh, but a *new* Autoexec.bat is created
> containing
> | nothing but comments that explain about Autoexec.tsh being the backup.
> There
> | *is* an Autoexec.bat, but it's toothless.
> |
> | --
> | Gary S. Terhune
> | MS-MVP Shell/User
> |
> | "PCR" <pcrrcp@netzero.net> wrote in message
> | news:O9GJyUcqFHA.3480@tk2msftngp13.phx.gbl...
> | > Autoexec.bat is renamed to Autoexec.tsh by Windows when you uncheck
> | > Autoexec.bat in "START, Run, MSConfig, General tab". In that case,
> there
> | > is no Autoexec.bat to run at boot-- & neither will Autoexec.tsh be
> run.
> | > That was the purpose of renaming it.
> | >
> | > When it is checked again, the .tsh will become a .bat again after a
> | > reboot. I think, though, every individual line inside Autoexec.bat
> that
> | > may have been unchecked in Autoexec.bat will be checked now. So,
> watch
> | > that!
> | >
> | >
> | > --
> | > Thanks or Good Luck,
> | > There may be humor in this post, and,
> | > Naturally, you will not sue,
> | > should things get worse after this,
> | > PCR
> | > pcrrcp@netzero.net
> | > "b11_" <b11@discussions.microsoft.com> wrote in message
> | > news:FADB56EF-EE38-4C48-B338-93D375E3F3F6@microsoft.com...
> | > | During bootup, the autoexec.tsh file is read, not the
> Autoexec.bat.
> | > | ______________________________________
> | > | "Ben Myers" wrote:
> | > |
> | > | > "b11_" <b11@discussions.microsoft.com> wrote in message
> | > news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
> | > | > > During bootup, the wrong autoexec file is read. Why?
> | > | >
> | > | > Please repost with more information, including why you think a
> | > | > different file is being processed.
> | > | >
> | > | > Ben
> | > | >
> | > | >
> | >
> | >
> |
> |
>
>
G
Guest
Guest
Archived from groups: microsoft.public.win98.gen_discussion (More info?)
Anyhow, it may not be safe to remain in this thread! b11_ seems to have
huge problems, judging from other threads he's begun! OK, bye!
--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR
pcrrcp@netzero.net
"Gary S. Terhune" <grystnews@mvps.org> wrote in message
news:%23G2lhbdqFHA.3788@TK2MSFTNGP12.phx.gbl...
| Oh....joy...
|
| --
| Gary S. Terhune
| MS-MVP Shell/User
|
| "PCR" <pcrrcp@netzero.net> wrote in message
| news:uo6GhucqFHA.1272@TK2MSFTNGP11.phx.gbl...
| > Thanks. Yes, perhaps I did see that once for one of the files. Yes,
it's
| > a reminder of what one has done. I will remember this on the day I
make
| > a Master Post about it! Thanks.
| >
| >
| > --
| > Thanks or Good Luck,
| > There may be humor in this post, and,
| > Naturally, you will not sue,
| > should things get worse after this,
| > PCR
| > pcrrcp@netzero.net
| > "Gary S. Terhune" <grystnews@mvps.org> wrote in message
| > news:%23XqzOncqFHA.3064@TK2MSFTNGP15.phx.gbl...
| > | Correction: When you uncheck Autoexec.bat in MSCONFIG,
Autoexec.bat is
| > | renamed to Autoexec.tsh, but a *new* Autoexec.bat is created
| > containing
| > | nothing but comments that explain about Autoexec.tsh being the
backup.
| > There
| > | *is* an Autoexec.bat, but it's toothless.
| > |
| > | --
| > | Gary S. Terhune
| > | MS-MVP Shell/User
| > |
| > | "PCR" <pcrrcp@netzero.net> wrote in message
| > | news:O9GJyUcqFHA.3480@tk2msftngp13.phx.gbl...
| > | > Autoexec.bat is renamed to Autoexec.tsh by Windows when you
uncheck
| > | > Autoexec.bat in "START, Run, MSConfig, General tab". In that
case,
| > there
| > | > is no Autoexec.bat to run at boot-- & neither will Autoexec.tsh
be
| > run.
| > | > That was the purpose of renaming it.
| > | >
| > | > When it is checked again, the .tsh will become a .bat again
after a
| > | > reboot. I think, though, every individual line inside
Autoexec.bat
| > that
| > | > may have been unchecked in Autoexec.bat will be checked now. So,
| > watch
| > | > that!
| > | >
| > | >
| > | > --
| > | > Thanks or Good Luck,
| > | > There may be humor in this post, and,
| > | > Naturally, you will not sue,
| > | > should things get worse after this,
| > | > PCR
| > | > pcrrcp@netzero.net
| > | > "b11_" <b11@discussions.microsoft.com> wrote in message
| > | > news:FADB56EF-EE38-4C48-B338-93D375E3F3F6@microsoft.com...
| > | > | During bootup, the autoexec.tsh file is read, not the
| > Autoexec.bat.
| > | > | ______________________________________
| > | > | "Ben Myers" wrote:
| > | > |
| > | > | > "b11_" <b11@discussions.microsoft.com> wrote in message
| > | > news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
| > | > | > > During bootup, the wrong autoexec file is read. Why?
| > | > | >
| > | > | > Please repost with more information, including why you think
a
| > | > | > different file is being processed.
| > | > | >
| > | > | > Ben
| > | > | >
| > | > | >
| > | >
| > | >
| > |
| > |
| >
| >
|
|
Anyhow, it may not be safe to remain in this thread! b11_ seems to have
huge problems, judging from other threads he's begun! OK, bye!
--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR
pcrrcp@netzero.net
"Gary S. Terhune" <grystnews@mvps.org> wrote in message
news:%23G2lhbdqFHA.3788@TK2MSFTNGP12.phx.gbl...
| Oh....joy...
|
| --
| Gary S. Terhune
| MS-MVP Shell/User
|
| "PCR" <pcrrcp@netzero.net> wrote in message
| news:uo6GhucqFHA.1272@TK2MSFTNGP11.phx.gbl...
| > Thanks. Yes, perhaps I did see that once for one of the files. Yes,
it's
| > a reminder of what one has done. I will remember this on the day I
make
| > a Master Post about it! Thanks.
| >
| >
| > --
| > Thanks or Good Luck,
| > There may be humor in this post, and,
| > Naturally, you will not sue,
| > should things get worse after this,
| > PCR
| > pcrrcp@netzero.net
| > "Gary S. Terhune" <grystnews@mvps.org> wrote in message
| > news:%23XqzOncqFHA.3064@TK2MSFTNGP15.phx.gbl...
| > | Correction: When you uncheck Autoexec.bat in MSCONFIG,
Autoexec.bat is
| > | renamed to Autoexec.tsh, but a *new* Autoexec.bat is created
| > containing
| > | nothing but comments that explain about Autoexec.tsh being the
backup.
| > There
| > | *is* an Autoexec.bat, but it's toothless.
| > |
| > | --
| > | Gary S. Terhune
| > | MS-MVP Shell/User
| > |
| > | "PCR" <pcrrcp@netzero.net> wrote in message
| > | news:O9GJyUcqFHA.3480@tk2msftngp13.phx.gbl...
| > | > Autoexec.bat is renamed to Autoexec.tsh by Windows when you
uncheck
| > | > Autoexec.bat in "START, Run, MSConfig, General tab". In that
case,
| > there
| > | > is no Autoexec.bat to run at boot-- & neither will Autoexec.tsh
be
| > run.
| > | > That was the purpose of renaming it.
| > | >
| > | > When it is checked again, the .tsh will become a .bat again
after a
| > | > reboot. I think, though, every individual line inside
Autoexec.bat
| > that
| > | > may have been unchecked in Autoexec.bat will be checked now. So,
| > watch
| > | > that!
| > | >
| > | >
| > | > --
| > | > Thanks or Good Luck,
| > | > There may be humor in this post, and,
| > | > Naturally, you will not sue,
| > | > should things get worse after this,
| > | > PCR
| > | > pcrrcp@netzero.net
| > | > "b11_" <b11@discussions.microsoft.com> wrote in message
| > | > news:FADB56EF-EE38-4C48-B338-93D375E3F3F6@microsoft.com...
| > | > | During bootup, the autoexec.tsh file is read, not the
| > Autoexec.bat.
| > | > | ______________________________________
| > | > | "Ben Myers" wrote:
| > | > |
| > | > | > "b11_" <b11@discussions.microsoft.com> wrote in message
| > | > news:7A184CDE-66FD-40AB-A41F-1A87C44D23F0@microsoft.com...
| > | > | > > During bootup, the wrong autoexec file is read. Why?
| > | > | >
| > | > | > Please repost with more information, including why you think
a
| > | > | > different file is being processed.
| > | > | >
| > | > | > Ben
| > | > | >
| > | > | >
| > | >
| > | >
| > |
| > |
| >
| >
|
|
G
Guest
Guest
Archived from groups: microsoft.public.win98.gen_discussion (More info?)
Yeah, I gave up on trying to figure that one out. I can't get a true picture
of what's going on.
--
Gary S. Terhune
MS-MVP Shell/User
"PCR" <pcrrcp@netzero.net> wrote in message
news:OasszhlqFHA.3444@TK2MSFTNGP12.phx.gbl...
> Anyhow, it may not be safe to remain in this thread! b11_ seems to have
> huge problems, judging from other threads he's begun! OK, bye!
>
>
> --
Yeah, I gave up on trying to figure that one out. I can't get a true picture
of what's going on.
--
Gary S. Terhune
MS-MVP Shell/User
"PCR" <pcrrcp@netzero.net> wrote in message
news:OasszhlqFHA.3444@TK2MSFTNGP12.phx.gbl...
> Anyhow, it may not be safe to remain in this thread! b11_ seems to have
> huge problems, judging from other threads he's begun! OK, bye!
>
>
> --
G
Guest
Guest
Archived from groups: microsoft.public.win98.gen_discussion (More info?)
I think he's trying to multiboot with BIOS settings, but I know little
of it. He's sees the right partition try to boot but ends up in the
wrong one. Better clear out of this thread & all of the others! Run!
--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR
pcrrcp@netzero.net
"Gary S. Terhune" <grystnews@mvps.org> wrote in message
news:%239fvkolqFHA.3540@TK2MSFTNGP14.phx.gbl...
| Yeah, I gave up on trying to figure that one out. I can't get a true
picture
| of what's going on.
|
| --
| Gary S. Terhune
| MS-MVP Shell/User
|
| "PCR" <pcrrcp@netzero.net> wrote in message
| news:OasszhlqFHA.3444@TK2MSFTNGP12.phx.gbl...
| > Anyhow, it may not be safe to remain in this thread! b11_ seems to
have
| > huge problems, judging from other threads he's begun! OK, bye!
| >
| >
| > --
|
|
I think he's trying to multiboot with BIOS settings, but I know little
of it. He's sees the right partition try to boot but ends up in the
wrong one. Better clear out of this thread & all of the others! Run!
--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR
pcrrcp@netzero.net
"Gary S. Terhune" <grystnews@mvps.org> wrote in message
news:%239fvkolqFHA.3540@TK2MSFTNGP14.phx.gbl...
| Yeah, I gave up on trying to figure that one out. I can't get a true
picture
| of what's going on.
|
| --
| Gary S. Terhune
| MS-MVP Shell/User
|
| "PCR" <pcrrcp@netzero.net> wrote in message
| news:OasszhlqFHA.3444@TK2MSFTNGP12.phx.gbl...
| > Anyhow, it may not be safe to remain in this thread! b11_ seems to
have
| > huge problems, judging from other threads he's begun! OK, bye!
| >
| >
| > --
|
|
G
Guest
Guest
Archived from groups: microsoft.public.win98.gen_discussion (More info?)
I said that the correct drive(physical drive 3) runs then physical drive 1
runs.
What would cause the drive I selected to boot(physical drive 3) to run then
physical drive 1 to run which results in a messed-up bootup?
_____________________________________________________
"PCR" wrote:
> I think he's trying to multiboot with BIOS settings, but I know little
> of it. He's sees the right partition try to boot but ends up in the
> wrong one. Better clear out of this thread & all of the others! Run!
>
>
> --
> Thanks or Good Luck,
> There may be humor in this post, and,
> Naturally, you will not sue,
> should things get worse after this,
> PCR
> pcrrcp@netzero.net
> "Gary S. Terhune" <grystnews@mvps.org> wrote in message
> news:%239fvkolqFHA.3540@TK2MSFTNGP14.phx.gbl...
> | Yeah, I gave up on trying to figure that one out. I can't get a true
> picture
> | of what's going on.
> |
> | --
> | Gary S. Terhune
> | MS-MVP Shell/User
> |
> | "PCR" <pcrrcp@netzero.net> wrote in message
> | news:OasszhlqFHA.3444@TK2MSFTNGP12.phx.gbl...
> | > Anyhow, it may not be safe to remain in this thread! b11_ seems to
> have
> | > huge problems, judging from other threads he's begun! OK, bye!
> | >
> | >
> | > --
> |
> |
>
>
>
I said that the correct drive(physical drive 3) runs then physical drive 1
runs.
What would cause the drive I selected to boot(physical drive 3) to run then
physical drive 1 to run which results in a messed-up bootup?
_____________________________________________________
"PCR" wrote:
> I think he's trying to multiboot with BIOS settings, but I know little
> of it. He's sees the right partition try to boot but ends up in the
> wrong one. Better clear out of this thread & all of the others! Run!
>
>
> --
> Thanks or Good Luck,
> There may be humor in this post, and,
> Naturally, you will not sue,
> should things get worse after this,
> PCR
> pcrrcp@netzero.net
> "Gary S. Terhune" <grystnews@mvps.org> wrote in message
> news:%239fvkolqFHA.3540@TK2MSFTNGP14.phx.gbl...
> | Yeah, I gave up on trying to figure that one out. I can't get a true
> picture
> | of what's going on.
> |
> | --
> | Gary S. Terhune
> | MS-MVP Shell/User
> |
> | "PCR" <pcrrcp@netzero.net> wrote in message
> | news:OasszhlqFHA.3444@TK2MSFTNGP12.phx.gbl...
> | > Anyhow, it may not be safe to remain in this thread! b11_ seems to
> have
> | > huge problems, judging from other threads he's begun! OK, bye!
> | >
> | >
> | > --
> |
> |
>
>
>
G
Guest
Guest
Archived from groups: microsoft.public.win98.gen_discussion (More info?)
Physical drive 3 may not be bootable. I suggest you remove it and replace
it with a known good bootable drive and see if the computer boots from it.
Ben
"b11_" <b11@discussions.microsoft.com> wrote in message news:6325E6E9-27DF-41D1-924E-E83DBC0BB706@microsoft.com...
> I said that the correct drive(physical drive 3) runs then physical drive 1
> runs.
>
> What would cause the drive I selected to boot(physical drive 3) to run then
> physical drive 1 to run which results in a messed-up bootup?
> _____________________________________________________
>
> "PCR" wrote:
>
> > I think he's trying to multiboot with BIOS settings, but I know little
> > of it. He's sees the right partition try to boot but ends up in the
> > wrong one. Better clear out of this thread & all of the others! Run!
> >
> >
> > --
> > Thanks or Good Luck,
> > There may be humor in this post, and,
> > Naturally, you will not sue,
> > should things get worse after this,
> > PCR
> > pcrrcp@netzero.net
> > "Gary S. Terhune" <grystnews@mvps.org> wrote in message
> > news:%239fvkolqFHA.3540@TK2MSFTNGP14.phx.gbl...
> > | Yeah, I gave up on trying to figure that one out. I can't get a true
> > picture
> > | of what's going on.
> > |
> > | --
> > | Gary S. Terhune
> > | MS-MVP Shell/User
> > |
> > | "PCR" <pcrrcp@netzero.net> wrote in message
> > | news:OasszhlqFHA.3444@TK2MSFTNGP12.phx.gbl...
> > | > Anyhow, it may not be safe to remain in this thread! b11_ seems to
> > have
> > | > huge problems, judging from other threads he's begun! OK, bye!
> > | >
> > | >
> > | > --
> > |
> > |
> >
> >
> >
Physical drive 3 may not be bootable. I suggest you remove it and replace
it with a known good bootable drive and see if the computer boots from it.
Ben
"b11_" <b11@discussions.microsoft.com> wrote in message news:6325E6E9-27DF-41D1-924E-E83DBC0BB706@microsoft.com...
> I said that the correct drive(physical drive 3) runs then physical drive 1
> runs.
>
> What would cause the drive I selected to boot(physical drive 3) to run then
> physical drive 1 to run which results in a messed-up bootup?
> _____________________________________________________
>
> "PCR" wrote:
>
> > I think he's trying to multiboot with BIOS settings, but I know little
> > of it. He's sees the right partition try to boot but ends up in the
> > wrong one. Better clear out of this thread & all of the others! Run!
> >
> >
> > --
> > Thanks or Good Luck,
> > There may be humor in this post, and,
> > Naturally, you will not sue,
> > should things get worse after this,
> > PCR
> > pcrrcp@netzero.net
> > "Gary S. Terhune" <grystnews@mvps.org> wrote in message
> > news:%239fvkolqFHA.3540@TK2MSFTNGP14.phx.gbl...
> > | Yeah, I gave up on trying to figure that one out. I can't get a true
> > picture
> > | of what's going on.
> > |
> > | --
> > | Gary S. Terhune
> > | MS-MVP Shell/User
> > |
> > | "PCR" <pcrrcp@netzero.net> wrote in message
> > | news:OasszhlqFHA.3444@TK2MSFTNGP12.phx.gbl...
> > | > Anyhow, it may not be safe to remain in this thread! b11_ seems to
> > have
> > | > huge problems, judging from other threads he's begun! OK, bye!
> > | >
> > | >
> > | > --
> > |
> > |
> >
> >
> >
G
Guest
Guest
Archived from groups: microsoft.public.win98.gen_discussion (More info?)
It could be certain important system files are kept on drive 1 & must
run although you boot drive 3, but I'm sorry I really have no experience
with multi-booting. Good luck with it, b11_.
--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR
pcrrcp@netzero.net
"b11_" <b11@discussions.microsoft.com> wrote in message
news:6325E6E9-27DF-41D1-924E-E83DBC0BB706@microsoft.com...
| I said that the correct drive(physical drive 3) runs then physical
drive 1
| runs.
|
| What would cause the drive I selected to boot(physical drive 3) to run
then
| physical drive 1 to run which results in a messed-up bootup?
| _____________________________________________________
|
| "PCR" wrote:
|
| > I think he's trying to multiboot with BIOS settings, but I know
little
| > of it. He's sees the right partition try to boot but ends up in the
| > wrong one. Better clear out of this thread & all of the others! Run!
| >
| >
| > --
| > Thanks or Good Luck,
| > There may be humor in this post, and,
| > Naturally, you will not sue,
| > should things get worse after this,
| > PCR
| > pcrrcp@netzero.net
| > "Gary S. Terhune" <grystnews@mvps.org> wrote in message
| > news:%239fvkolqFHA.3540@TK2MSFTNGP14.phx.gbl...
| > | Yeah, I gave up on trying to figure that one out. I can't get a
true
| > picture
| > | of what's going on.
| > |
| > | --
| > | Gary S. Terhune
| > | MS-MVP Shell/User
| > |
| > | "PCR" <pcrrcp@netzero.net> wrote in message
| > | news:OasszhlqFHA.3444@TK2MSFTNGP12.phx.gbl...
| > | > Anyhow, it may not be safe to remain in this thread! b11_ seems
to
| > have
| > | > huge problems, judging from other threads he's begun! OK, bye!
| > | >
| > | >
| > | > --
| > |
| > |
| >
| >
| >
It could be certain important system files are kept on drive 1 & must
run although you boot drive 3, but I'm sorry I really have no experience
with multi-booting. Good luck with it, b11_.
--
Thanks or Good Luck,
There may be humor in this post, and,
Naturally, you will not sue,
should things get worse after this,
PCR
pcrrcp@netzero.net
"b11_" <b11@discussions.microsoft.com> wrote in message
news:6325E6E9-27DF-41D1-924E-E83DBC0BB706@microsoft.com...
| I said that the correct drive(physical drive 3) runs then physical
drive 1
| runs.
|
| What would cause the drive I selected to boot(physical drive 3) to run
then
| physical drive 1 to run which results in a messed-up bootup?
| _____________________________________________________
|
| "PCR" wrote:
|
| > I think he's trying to multiboot with BIOS settings, but I know
little
| > of it. He's sees the right partition try to boot but ends up in the
| > wrong one. Better clear out of this thread & all of the others! Run!
| >
| >
| > --
| > Thanks or Good Luck,
| > There may be humor in this post, and,
| > Naturally, you will not sue,
| > should things get worse after this,
| > PCR
| > pcrrcp@netzero.net
| > "Gary S. Terhune" <grystnews@mvps.org> wrote in message
| > news:%239fvkolqFHA.3540@TK2MSFTNGP14.phx.gbl...
| > | Yeah, I gave up on trying to figure that one out. I can't get a
true
| > picture
| > | of what's going on.
| > |
| > | --
| > | Gary S. Terhune
| > | MS-MVP Shell/User
| > |
| > | "PCR" <pcrrcp@netzero.net> wrote in message
| > | news:OasszhlqFHA.3444@TK2MSFTNGP12.phx.gbl...
| > | > Anyhow, it may not be safe to remain in this thread! b11_ seems
to
| > have
| > | > huge problems, judging from other threads he's begun! OK, bye!
| > | >
| > | >
| > | > --
| > |
| > |
| >
| >
| >
Tom's Hardware is part of Future plc, an international media group and leading digital publisher. Visit our corporate site.
© Future Publishing Limited Quay House, The Ambury, Bath BA1 1UA. All rights reserved. England and Wales company registration number 2008885.
Facebook
Twitter
Instagram