Archived from groups: microsoft.public.win98.gen_discussion (More info?)

How can I disable the Win98 swap file?

It causes some of my processing to occur out of sequence
and I would like to prevent that from happening.

This is relating to my own programming.

Thanks for any help.

Jack

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

System Properties, Performance tab. There's a button there.

But you'd better be *real* sure you have plenty of RAM to handle
whatever comes down the pike.

You're doing your own programming and you don't know how to disable the
Swap file? Perhaps you should be looking for more training in ways to
manage your code so that the swap file ceases to become an issue? Just a
thought...

--
Gary S. Terhune
MS MVP Shell/User
http://www.grystmill.com/articles/cleanboot.htm
http://www.grystmill.com/articles/security.htm

"J. Yazel" <jyazel@ds.net> wrote in message
news:4amr311dppfsfub0nu1cpi9lbe90isftdl@4ax.com...
>
> How can I disable the Win98 swap file?
>
> It causes some of my processing to occur out of sequence
> and I would like to prevent that from happening.
>
> This is relating to my own programming.
>
> Thanks for any help.
>
> Jack
>

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

Control Panel, System, Performance, Virtual Memory tab (etc).
Generally NOT a good idea.

J. Yazel wrote:
> How can I disable the Win98 swap file?
>
> It causes some of my processing to occur out of sequence
> and I would like to prevent that from happening.
>
> This is relating to my own programming.
>
> Thanks for any help.
>
> Jack

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

Gary S. Terhune wrote:
> System Properties, Performance tab. There's a button there.
>
> But you'd better be *real* sure you have plenty of RAM to handle
> whatever comes down the pike.
>
> You're doing your own programming and you don't know how to disable the
> Swap file?

LOL. That's a good catch! Yeah, now this sounds a bit fishy to me.

> Perhaps you should be looking for more training in ways to
> manage your code so that the swap file ceases to become an issue? Just a
> thought...
>
> --
> Gary S. Terhune
> MS MVP Shell/User
> http://www.grystmill.com/articles/cleanboot.htm
> http://www.grystmill.com/articles/security.htm
>
> "J. Yazel" <jyazel@ds.net> wrote in message
> news:4amr311dppfsfub0nu1cpi9lbe90isftdl@4ax.com...
>>
>> How can I disable the Win98 swap file?
>>
>> It causes some of my processing to occur out of sequence
>> and I would like to prevent that from happening.
>>
>> This is relating to my own programming.
>>
>> Thanks for any help.
>>
>> Jack

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

In addition to Gary's response, be aware that some programs expect to see a
swap file (even though they might not use it) and will not run properly
without it.

--
Regards

Ron Badour, MS MVP Windows 98
Tips: http://home.satx.rr.com/badour
Knowledge Base Info:
http://support.microsoft.com/default.aspx?pr=kbinfo

"J. Yazel" <jyazel@ds.net> wrote in message
news:4amr311dppfsfub0nu1cpi9lbe90isftdl@4ax.com...
>
> How can I disable the Win98 swap file?
>
> It causes some of my processing to occur out of sequence
> and I would like to prevent that from happening.
>
> This is relating to my own programming.
>
> Thanks for any help.
>
> Jack
>

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

On Sun, 20 Mar 2005 12:48:26 -0800, "Gary S. Terhune" <grystnews@mvps.org>
wrote:

>System Properties, Performance tab. There's a button there.
>
>But you'd better be *real* sure you have plenty of RAM to handle
>whatever comes down the pike.
>
>You're doing your own programming and you don't know how to disable the
>Swap file? Perhaps you should be looking for more training in ways to
>manage your code so that the swap file ceases to become an issue? Just a
>thought...
=================================

Thanks for the answer. However, I didn't clearly state what I need.

First, the program I am referring to is not a Windows program, but an
assembler (MASM) program. It is a mass copy program that I use very
frequently between machines. I wrote my own because I have from time to
time various versions of Windows and DOS and most backup programs
don't cover this. In addition, most backup programs don't compare the
source and target files after the copy. I'm a nut case when it comes to
making sure that a copy is in fact, valid.

The program, however, must be able to run in a Windows DOS window
to prevent loss of the long file names.

More importantly, I don't want to disable the swap file permanently. Ninety-
five percent of the time it will be enabled. It will be disabled only when I
am running this program (or something similar).

When I run the program, the disk writes and reads actually work against the
swap file almost the whole time. The program is almost finished when the
"real" disk I/O gets going. Therefore, if any error occurs during the "real"
I/O, the program can't handle it. Typical errors include different bytes in
the source and target files, different file dates, times, size, etc.

I was actually looking for a way to disable the swap file only during the
run of a specific program.

I do appreciate your attempt to help.

Jack

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

It's not the swap file that's causing you a problem. Whether or not the swap
file is involved in a copy operation should be completely invisible to a
properly written program, whether DOS or Windows.

You need to investigate why the messages from the copy or compare process
aren't properly handled by your application. From your description it seems
that you are invoking DOS utilities to do the copy and compare for you.
This can mean that your application is not around to handle the error codes
returned by these processes. I can't think of any other way that your
program could be 'almost finished' before these messages are generated.

If this is the way that the program is written, you need to look at how it
is invoking these processes, and what you can change to ensure that it waits
until the process is completed before either moving on to the next task or
handling the returned error.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"J. Yazel" <jyazel@ds.net> wrote in message
news:12hs31pbnukff1vuulrh8abujs4p1f7qvn@4ax.com...
> snip <
>
> Thanks for the answer. However, I didn't clearly state what I need.
>
> First, the program I am referring to is not a Windows program, but an
> assembler (MASM) program. It is a mass copy program that I use very
> frequently between machines. I wrote my own because I have from time to
> time various versions of Windows and DOS and most backup programs
> don't cover this. In addition, most backup programs don't compare the
> source and target files after the copy. I'm a nut case when it comes to
> making sure that a copy is in fact, valid.
>
> The program, however, must be able to run in a Windows DOS window
> to prevent loss of the long file names.
>
> More importantly, I don't want to disable the swap file permanently.
> Ninety-
> five percent of the time it will be enabled. It will be disabled only when
> I
> am running this program (or something similar).
>
> When I run the program, the disk writes and reads actually work against
> the
> swap file almost the whole time. The program is almost finished when the
> "real" disk I/O gets going. Therefore, if any error occurs during the
> "real"
> I/O, the program can't handle it. Typical errors include different bytes
> in
> the source and target files, different file dates, times, size, etc.
>
> I was actually looking for a way to disable the swap file only during the
> run of a specific program.
>
> I do appreciate your attempt to help.
>
> Jack

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

Jeff Richards wrote:
> It's not the swap file that's causing you a problem. Whether or not the
swap
> file is involved in a copy operation should be completely invisible to a
> properly written program, whether DOS or Windows.

Exactly.

> You need to investigate why the messages from the copy or compare process
> aren't properly handled by your application. From your description it
seems
> that you are invoking DOS utilities to do the copy and compare for you.
> This can mean that your application is not around to handle the error
codes
> returned by these processes. I can't think of any other way that your
> program could be 'almost finished' before these messages are generated.
>
> If this is the way that the program is written, you need to look at how it
> is invoking these processes, and what you can change to ensure that it
waits
> until the process is completed before either moving on to the next task or
> handling the returned error.
> --
> Jeff Richards
> MS MVP (Windows - Shell/User)
> "J. Yazel" <jyazel@ds.net> wrote in message
> news:12hs31pbnukff1vuulrh8abujs4p1f7qvn@4ax.com...
>> snip <
>>
>> Thanks for the answer. However, I didn't clearly state what I need.
>>
>> First, the program I am referring to is not a Windows program, but an
>> assembler (MASM) program. It is a mass copy program that I use very
>> frequently between machines. I wrote my own because I have from time to
>> time various versions of Windows and DOS and most backup programs
>> don't cover this. In addition, most backup programs don't compare the
>> source and target files after the copy. I'm a nut case when it comes to
>> making sure that a copy is in fact, valid.
>>
>> The program, however, must be able to run in a Windows DOS window
>> to prevent loss of the long file names.
>>
>> More importantly, I don't want to disable the swap file permanently.
>> Ninety-
>> five percent of the time it will be enabled. It will be disabled only
when
>> I
>> am running this program (or something similar).
>>
>> When I run the program, the disk writes and reads actually work against
>> the
>> swap file almost the whole time. The program is almost finished when the
>> "real" disk I/O gets going. Therefore, if any error occurs during the
>> "real"
>> I/O, the program can't handle it. Typical errors include different bytes
>> in
>> the source and target files, different file dates, times, size, etc.
>>
>> I was actually looking for a way to disable the swap file only during the
>> run of a specific program.
>>
>> I do appreciate your attempt to help.
>>
>> Jack

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

So, you're looking for a way to "programmatically" disable Virtual
Memory temporarily. Sorry, that's out of my league.

Backup programs may not suit your needs, but popular "imaging" programs
sound like what you're attempting.

--
Gary S. Terhune
MS MVP Shell/User
http://www.grystmill.com/articles/cleanboot.htm
http://www.grystmill.com/articles/security.htm

"J. Yazel" <jyazel@ds.net> wrote in message
news:12hs31pbnukff1vuulrh8abujs4p1f7qvn@4ax.com...
> On Sun, 20 Mar 2005 12:48:26 -0800, "Gary S. Terhune"
<grystnews@mvps.org>
> wrote:
>
> >System Properties, Performance tab. There's a button there.
> >
> >But you'd better be *real* sure you have plenty of RAM to handle
> >whatever comes down the pike.
> >
> >You're doing your own programming and you don't know how to disable
the
> >Swap file? Perhaps you should be looking for more training in ways to
> >manage your code so that the swap file ceases to become an issue?
Just a
> >thought...
> =================================
>
> Thanks for the answer. However, I didn't clearly state what I need.
>
> First, the program I am referring to is not a Windows program, but an
> assembler (MASM) program. It is a mass copy program that I use very
> frequently between machines. I wrote my own because I have from time
to
> time various versions of Windows and DOS and most backup programs
> don't cover this. In addition, most backup programs don't compare the
> source and target files after the copy. I'm a nut case when it comes
to
> making sure that a copy is in fact, valid.
>
> The program, however, must be able to run in a Windows DOS window
> to prevent loss of the long file names.
>
> More importantly, I don't want to disable the swap file permanently.
Ninety-
> five percent of the time it will be enabled. It will be disabled only
when I
> am running this program (or something similar).
>
> When I run the program, the disk writes and reads actually work
against the
> swap file almost the whole time. The program is almost finished when
the
> "real" disk I/O gets going. Therefore, if any error occurs during the
"real"
> I/O, the program can't handle it. Typical errors include different
bytes in
> the source and target files, different file dates, times, size, etc.
>
> I was actually looking for a way to disable the swap file only during
the
> run of a specific program.
>
> I do appreciate your attempt to help.
>
> Jack
>
>
>

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

Jeff can the swap file in 98SE easily be hacked? TIA

"Jeff Richards" <JRichards@msn.com.au> wrote in message
news:uCPZfCdLFHA.1396@TK2MSFTNGP10.phx.gbl...
: It's not the swap file that's causing you a problem. Whether or not the
swap
: file is involved in a copy operation should be completely invisible to a
: properly written program, whether DOS or Windows.
:
: You need to investigate why the messages from the copy or compare process
: aren't properly handled by your application. From your description it
seems
: that you are invoking DOS utilities to do the copy and compare for you.
: This can mean that your application is not around to handle the error codes
: returned by these processes. I can't think of any other way that your
: program could be 'almost finished' before these messages are generated.
:
: If this is the way that the program is written, you need to look at how it
: is invoking these processes, and what you can change to ensure that it
waits
: until the process is completed before either moving on to the next task or
: handling the returned error.
: --
: Jeff Richards
: MS MVP (Windows - Shell/User)
: "J. Yazel" <jyazel@ds.net> wrote in message
: news:12hs31pbnukff1vuulrh8abujs4p1f7qvn@4ax.com...
: > snip <
: >
: > Thanks for the answer. However, I didn't clearly state what I need.
: >
: > First, the program I am referring to is not a Windows program, but an
: > assembler (MASM) program. It is a mass copy program that I use very
: > frequently between machines. I wrote my own because I have from time to
: > time various versions of Windows and DOS and most backup programs
: > don't cover this. In addition, most backup programs don't compare the
: > source and target files after the copy. I'm a nut case when it comes to
: > making sure that a copy is in fact, valid.
: >
: > The program, however, must be able to run in a Windows DOS window
: > to prevent loss of the long file names.
: >
: > More importantly, I don't want to disable the swap file permanently.
: > Ninety-
: > five percent of the time it will be enabled. It will be disabled only
when
: > I
: > am running this program (or something similar).
: >
: > When I run the program, the disk writes and reads actually work against
: > the
: > swap file almost the whole time. The program is almost finished when the
: > "real" disk I/O gets going. Therefore, if any error occurs during the
: > "real"
: > I/O, the program can't handle it. Typical errors include different bytes
: > in
: > the source and target files, different file dates, times, size, etc.
: >
: > I was actually looking for a way to disable the swap file only during the
: > run of a specific program.
: >
: > I do appreciate your attempt to help.
: >
: > Jack
:
:

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

:< I don't know much about Virtual Memory, either Gary --- how can I learn
more about it. TIA (any good book you suggest I need to read about it)

"Gary S. Terhune" <grystnews@mvps.org> wrote in message
news:uQkV8meLFHA.656@TK2MSFTNGP14.phx.gbl...
: So, you're looking for a way to "programmatically" disable Virtual
: Memory temporarily. Sorry, that's out of my league.
:
: Backup programs may not suit your needs, but popular "imaging" programs
: sound like what you're attempting.
:
: --
: Gary S. Terhune
: MS MVP Shell/User
: http://www.grystmill.com/articles/cleanboot.htm
: http://www.grystmill.com/articles/security.htm
:
: "J. Yazel" <jyazel@ds.net> wrote in message
: news:12hs31pbnukff1vuulrh8abujs4p1f7qvn@4ax.com...
: > On Sun, 20 Mar 2005 12:48:26 -0800, "Gary S. Terhune"
: <grystnews@mvps.org>
: > wrote:
: >
: > >System Properties, Performance tab. There's a button there.
: > >
: > >But you'd better be *real* sure you have plenty of RAM to handle
: > >whatever comes down the pike.
: > >
: > >You're doing your own programming and you don't know how to disable
: the
: > >Swap file? Perhaps you should be looking for more training in ways to
: > >manage your code so that the swap file ceases to become an issue?
: Just a
: > >thought...
: > =================================
: >
: > Thanks for the answer. However, I didn't clearly state what I need.
: >
: > First, the program I am referring to is not a Windows program, but an
: > assembler (MASM) program. It is a mass copy program that I use very
: > frequently between machines. I wrote my own because I have from time
: to
: > time various versions of Windows and DOS and most backup programs
: > don't cover this. In addition, most backup programs don't compare the
: > source and target files after the copy. I'm a nut case when it comes
: to
: > making sure that a copy is in fact, valid.
: >
: > The program, however, must be able to run in a Windows DOS window
: > to prevent loss of the long file names.
: >
: > More importantly, I don't want to disable the swap file permanently.
: Ninety-
: > five percent of the time it will be enabled. It will be disabled only
: when I
: > am running this program (or something similar).
: >
: > When I run the program, the disk writes and reads actually work
: against the
: > swap file almost the whole time. The program is almost finished when
: the
: > "real" disk I/O gets going. Therefore, if any error occurs during the
: "real"
: > I/O, the program can't handle it. Typical errors include different
: bytes in
: > the source and target files, different file dates, times, size, etc.
: >
: > I was actually looking for a way to disable the swap file only during
: the
: > run of a specific program.
: >
: > I do appreciate your attempt to help.
: >
: > Jack
: >
: >
: >
:

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

AFAIK, the .swp file is locked. I may be confusing this with something else
386.swp --- <???> Any help is appreciated on this issue.

"J. Yazel" <jyazel@ds.net> wrote in message
news:4amr311dppfsfub0nu1cpi9lbe90isftdl@4ax.com...
:
: How can I disable the Win98 swap file?
:
: It causes some of my processing to occur out of sequence
: and I would like to prevent that from happening.
:
: This is relating to my own programming.
:
: Thanks for any help.
:
: Jack
:

Archived from groups: microsoft.public.win98.gen_discussion (More info?)

On Mon, 21 Mar 2005 15:44:40 +1100, "Jeff Richards" <JRichards@msn.com.au>
wrote:

>It's not the swap file that's causing you a problem. Whether or not the swap
>file is involved in a copy operation should be completely invisible to a
>properly written program, whether DOS or Windows.
>
>You need to investigate why the messages from the copy or compare process
>aren't properly handled by your application. From your description it seems
>that you are invoking DOS utilities to do the copy and compare for you.
>This can mean that your application is not around to handle the error codes
>returned by these processes. I can't think of any other way that your
>program could be 'almost finished' before these messages are generated.
>
>If this is the way that the program is written, you need to look at how it
>is invoking these processes, and what you can change to ensure that it waits
>until the process is completed before either moving on to the next task or
>handling the returned error.
================

Thanks very much for the response.

Jack