Private Life under Socialism Love Intimacy and

Family Change in a Chinese Village 1949 1999 1st

Edition Yunxiang Yan - Downloadable PDF 2025

https://ebookfinal.com/download/private-life-under-socialism-love-
intimacy-and-family-change-in-a-chinese-village-1949-1999-1st-edition-
yunxiang-yan/

Visit ebookfinal.com today to download the complete set of

ebooks or textbooks
Here are some recommended products that we believe you will be
interested in. You can click the link to download.

Village China Under Socialism and Reform A Micro History

1948 2008 1st Edition Huaiyin Li

https://ebookfinal.com/download/village-china-under-socialism-and-
reform-a-micro-history-1948-2008-1st-edition-huaiyin-li/

The Spectacle of Intimacy A Public Life for the Victorian

Family Karen Chase

https://ebookfinal.com/download/the-spectacle-of-intimacy-a-public-
life-for-the-victorian-family-karen-chase/

Agricultural Change and Peasant Choice in a Thai Village

Michael Moerman

https://ebookfinal.com/download/agricultural-change-and-peasant-
choice-in-a-thai-village-michael-moerman/

The Chinese Worker after Socialism 1st Edition William

Hurst

https://ebookfinal.com/download/the-chinese-worker-after-
socialism-1st-edition-william-hurst/
A New American Family A Love Story 1st Edition Peter
Likins

https://ebookfinal.com/download/a-new-american-family-a-love-
story-1st-edition-peter-likins/

My grandmother s Chinese kitchen 100 family recipes and

life lessons 1st ed Edition Wong

https://ebookfinal.com/download/my-grandmother-s-chinese-
kitchen-100-family-recipes-and-life-lessons-1st-ed-edition-wong/

Growing Couple Intimacy Improving Love Sex and

Relationships William E. Krill

https://ebookfinal.com/download/growing-couple-intimacy-improving-
love-sex-and-relationships-william-e-krill/

Chinese Medicine in East Africa An Intimacy with Strangers

1st Edition Elisabeth Hsu

https://ebookfinal.com/download/chinese-medicine-in-east-africa-an-
intimacy-with-strangers-1st-edition-elisabeth-hsu/

A Mountain Oasis Daily Life in a Village in the Yasin

Valley Pakistan 1st Edition Susan York

https://ebookfinal.com/download/a-mountain-oasis-daily-life-in-a-
village-in-the-yasin-valley-pakistan-1st-edition-susan-york/
Private Life under Socialism Love Intimacy and Family
Change in a Chinese Village 1949 1999 1st Edition
Yunxiang Yan Digital Instant Download
Author(s): Yunxiang Yan
ISBN(s): 9780804744560, 0804744564
Edition: 1
File Details: PDF, 24.07 MB
Year: 2003
Language: english
PRIVATE LIFE UNDER SOCIALISM
YUNXIANG YAN

Private Life under Socialism

Love, Intimacy, and Family Change in a Chinese Village
I949-I999

STANFORD UNIVERSITY PRESS

STANFORD, CALIFORNIA

20O3
Stanford University Press
Library

Stanford University Press

Stanford, California
© 2003 by the Board of Trustees of the
Leland Stanford Junior University.
All rights reserved.
Printed in the United States of America
on acid-free, archival-quality paper.
Library of Congress Cataloging-in-Publication Data
Yan, Yunxiang, 1954-
Private life under socialism : love, intimacy, and family change in a
Chinese village, 1949-1999 / Yunxiang Yan.
p. cm.
Includes bibliographical references and index.
ISBN 0-8047-3309-0 (cloth : alk. paper) — ISBN 0-8047-4456-4 (pbk.
alk. paper)
i. Family—China—Xiajia (Heilongjiang Sheng) 2.
Marriage—China—Xiajia (Heilongjiang Sheng) 3. Intergenerational
relations—China—Xiajia (Heilongjiang Sheng) 4.
Courtship—China—Xiajia (Heilongjiang Sheng) 5. Communism and
family—China—Xiajia (Heilongjiang Sheng) 6. Xiajia (Heilongjiang
Sheng, China)—Social conditions—2oth century. 7. Xiajia (Heilongjiang
Sheng, China)—Social life and customs—2oth century. I. Tide.
HQ684.Z9-X539 2003
306.8*0951 '84—dc21
2002013327
Original Printing 2003
Last figure below indicates year of this printing:
12 ii 10 09 08 07 06 05 04 03
Typeset by Classic Typography in 10/14 Janson
To James L Watson, guru and friend
Contents

List of Figures ix
List of Tables x
Preface xi

Introduction: The Chinese Family and the Study of

Private Life i
1. The Changing Local World: Political Economy,
Public Life, and Social Networks 17
2. Youth Autonomy and Romance in Courtship 42
3. Sex, Intimacy, and the Language of Love 64
4. Gender Dynamics and the Triumph of Conjugal Power 86
5. Domestic Space and the Quest for Privacy 112
6. The Politics of Family Property 140
7. Elderly Support and the Crisis of Filial Piety 162
8. Birth Control and the Making of a New Fertility Culture 190
Conclusion: The Socialist State, the Private Family,
and the Uncivil Individual 217

Character List 237

Notes 243
Bibliography 267
Index 283
Figures

5.1 Floor Plan of a Pre-1980 House 114

5.2 Floor Plan of a 1985 House 118
5.3 Floor Plan of a 1986 House 119
5.4 Floor Plan of a 1997 House 121
Eleven pages of photographs follow page in
Tables

2.1 Spouse Selection among Xiajia Men, 1949-1999 47

2.2 Dominance in Spouse Selection in Xiajia Village, 1949-1999 62
4.1 Family Composition in Xiajia Village, 1980, 1991, and 1998 89
4.2 Family Structure and Economic Stratification in Xiajia
Village, 1980, 1991, and 1998 90
4.3 Decision-Making and Household Chores in Nuclear
Families, 1998-1999 98
6.1 Marriage Financing Provided by the Groom's Family,
1950-1999 151
6.2 Bridewealth Provided by the Groom's Family, 1950-1999 154
7.1 Living Arrangements of Elderly Parents in 1998 164
7.2 Living Arrangements of Middle-Aged Parents in 1998 166
8.1 Fines for Unplanned Births, 1980-1999 195
8.2 Distribution of Births by Parity, 1979-1998 197
8.3 Villagers' Childbearing Status Defined by Last Birth,
April i98o-July 1999 201
Preface

It has been nearly fifteen years since this book was first conceived in the
form of a research proposal. In the academic year 1987-88, I diligently
pored through the existing studies of the Chinese family and kinship, a sub-
field that I had chosen as part of my Ph.D. training in anthropology at Har-
vard University. I was instantly attracted to the interesting and complex issues
I read about, yet at the same time I was puzzled by the absence of a discussion
of individual agency: most scholarly accounts focused on the structural prin-
ciples and collective behavior of the domestic group. That was at odds with
my understanding of family life in the People's Republic of China, where the
family institution has undergone radical and rapid changes since 1949. After
I began to teach, my students expressed the same feeling that something was
missing from the readings I assigned to them. The questions they asked most
frequently were: "Why is the Chinese family so economic, and are people al-
ways so rational?"
There are two possible answers to this puzzle. One answer is that the
Chinese family was indeed an economic organization, with little room for
other aspects of private life such as intimacy, emotionality, and individual
freedom. The other answer is that, in order to emphasize the unique fea-
tures of the Chinese family and compare it with the American/Western fam-
ily, many studies omitted elements of everyday life that were deemed in-
significant or too familiar to readers in the West. As my own research on the
subject developed and progressed, I became convinced that the latter expla-
nation is more likely correct.
Generally speaking, academic studies have presented three models of the
Chinese family. The first is the economic family, proposed mainly by Western

xi
 PREFACE

social scientists, who regard the domestic group primarily as a corporate or-
ganization characterized by a common budget, shared property, and a house-
hold economy with a strict pooling of income. The second may be called the
political family, shown primarily by feminist scholars to have deeply rooted
inequalities and power dynamics; their studies explore the resulting political
dimension of the Chinese family. Studies of the relationship between the
family and the state may also be included in this type. The third is the cul-
tural family; as portrayed mainly by Chinese scholars and cultural elite, these
studies emphasize the overarching and enduring influence of traditional val-
ues, particularly Confucian ethics, on family behavior. The individual re-
mains at the margins in all three models, and the emotional world of flesh-
and-bone people has usually been overlooked.
Yet without individuals and their lived experiences the family would have
not existed and family life would have not been possible. My research shows
that the contemporary Chinese family, while certainly economic, political,
and cultural, is also personal and emotional. Like its counterpart in American
society, Chinese family life is characterized by the moral experiences of indi-
viduals, whose concerns about privacy, intimacy, emotionality, and individual
rights are as important as economic gains. By focusing on the personal and
emotional, I hope this book may provide a new way of understanding private
life in China and balance the previous emphasis on the structure and collec-
tivity of the Chinese family.
In retrospect, I realize how much my longitudinal fieldwork in Xiajia village
benefited from my having spent my youth there in the 19705. As my fieldwork
evolved, I often found myself a stranger in the community where I grew up
because the social landscape, the people, and my relationship with the vil-
lagers had changed so dramatically. Thus I had to relearn what I thought I
already knew. As times changed, so did the mentality of the villagers, many
of whom viewed the same social phenomenon differently or even provided
different narratives of the same event at different times. To capture the dy-
namism in people's behavior and mentality, particularly that of village youth
who are most sensitive to social changes in larger settings, I simply followed
and documented the life course of more than two dozen individuals, a process
that would have been impossible had I not shared my own life experiences
with them in the 19705.
 PREFACE Xlii

I do not intend to portray this rural community as representative of Chi-

nese society as a whole. On the contrary, in this case study I am primarily
concerned with how the villagers lived their private lives under socialism
and how their local history was shaped by social conditions. I also want to
note that the trends of change described in this book, including the privati-
zation of the family, the increasing importance of intimacy and emotional-
ity in family life, the rise of individuality, and the growing crisis of civility,
have long occurred in cities and many parts of rural China, as shown by sev-
eral large-scale national surveys of family change and numerous empirical
studies. This is because all Chinese people have lived with the same social-
ist state since 1949, a state that played a decisive role in transforming Chi-
nese private life. Consequently, the social issues and moral dilemmas that
people in Xiajia village have to deal with are largely the same as those dealt
with by people nationwide. These same issues and dilemmas also exist in
most of the world's societies and thus are relevant to people around the globe.
Nevertheless, because people always respond to changes and challenges from
the outside world in accordance with local conditions and by exercising their
own agency, the specific form and content of their responses vary greatly.
Therefore, it is only through local particularities and historical specificities
that we may deepen our understanding of the general trends of social change
and of the moral experiences of the people. In this sense, I am confident that
the implications of this case study have relevance far beyond the boundaries
of the village.
During my long intellectual journey since 1987 I have accumulated vast
debts to many friends and colleagues and received financial support from a
number of institutions, without whose help it would have been impossible to
complete this book.
The first person I want to thank is James L. (Woody) Watson, my guru and
friend. Woody was the most enthusiastic supporter of the research project
from its inception and was untiring in offering advice and critically reading
several drafts of the manuscript. As an inspiring and encouraging mentor,
Woody has played a decisive role in my intellectual development; as a good
friend, he has been extremely warm, caring, and always available. To Woody I
owe a debt of such great dimensions that a simple acknowledgment is insuffi-
cient; hence the dedication of this book to him.
XlV PREFACE

Similarly, words are inadequate to express my gratitude to Arthur Klein-

man and Joan Kleinman, who have far exceeded their obligations in offering
support and help ever since I became Arthur's student in 1986. They read
several drafts of the manuscript that became this book and offered so many
valuable comments that I lost count. I am above all indebted to Arthur for
his theoretical inspiration. This book represents my own attempt to write an
individual-centered ethnography of moral experience—the kind of anthro-
pological enterprise that Arthur and Joan have long advocated.
I am deeply grateful to the residents of Xiajia village, Heilongjiang prov-
ince, in northeastern China, for receiving me on two occasions. In 1971, at
the age of seventeen, I traveled hundreds of miles from a village in Shan-
dong province to Heilongjiang as a destitute migrant searching for a new
home with enough food. During my wanderings from one place to another
while performing various temporary jobs, the villagers of Xiajia generously
took me in. I thereafter lived in Xiajia as an ordinary farmer until I entered
Peking University for my undergraduate education in 1978. In the spring of
19891 returned to the village as a Ph.D. student from Harvard University to
carry out my first anthropological fieldwork; that visit was followed by a se-
ries of field research trips in 1991, 1993, 1994? J 997> 1998, and 1999. Each
trip began with one or two reunion parties and ended with a long and warm
farewell; in between there were equally memorable times as the villagers
tried their best to fulfill my seemingly endless curiosity about their work,
life, family, and community. Among the villagers, I am especially grateful to
Mr. Hu Yanjun, a friend for more than thirty years, whose knowledge, hu-
mor, and intellect were instrumental in helping me with the specifics of my
fieldwork and who played an important role in my research design. I fre-
quently solicited his opinion on how to deepen and widen my investigations.
I cannot imagine how difficult, if possible at all, my eleven years of longitu-
dinal fieldwork would have been without the help and support of the vil-
lagers and several friends in the local government.
Many friends and colleagues read parts of or the entire manuscript and
generously offered insightful comments. They are my heroes, and I am almost
certain the following is an incomplete list: Cameron Campbell, Myron Cohen,
Deborah Davis, Stephan Feuchtwang, Maris Gillette, Marjorie Goodwin,
Susan Greenhalgh, Stevan Harrell, Douglas Hollan, William Jankowiak, Jun
Jing, William Lavely, James Lee, Bonnie McDougall, Jonathan Parry, Isabelle
 PREFACE

Thireau, Jonathan Unger, Wang Feng, Ruble Watson, and Martin Whyte. I
am also grateful to Joseph Bosco, Karen Brodkin, Choi Chi-cheng, Lothar
von Falkenhausen, Linda Garro, Guo Yuhua, Xiaoxia Gong, Philip Huang,
Jean Hung, Nancy Levine, Liu Dik-Sung, Paula Paderni, Shen Yuan, Sun
Liping, and Yang Nianqun for their insights, which were equally important
in formulating and clarifying many of my arguments. I owe special thanks to
Liang Xiaoyan for sharing with me her acute observations of social change
in China and for her critiques of several important points that appear in the
concluding chapter.
I was also lucky to find a transcontinental community for invaluable dis-
cussions while writing. Frangoise Sabban generously invited me to be a vis-
iting associate professor at the Centre d'Etudes sur la Chine Moderne et
Contemporaine, Ecole des Hautes Etudes en Sciences Sociales (EHESS) in
May 2000. This wonderful opportunity enabled me to write Chapter 8 in a
small yet charming apartment in northern Paris, while presenting other
draft chapters in three lectures at EHESS. During the following month,
thanks to Charles Stafford's kind hospitality, I visited the Anthropology De-
partment at the London School of Economics and presented my research
results on two occasions. During my stay in Europe I also delivered materials
from this book at the Institute of Sinology at Leiden University, the Center
for Asian and South Asian Studies at the University of Amsterdam, and the
Institute of Anthropology at Oxford University. In 2001,1 gave public lec-
tures at the Institute of Sociology and Anthropology of Peking University
and at the Institute of Sociology of the Chinese Academy of Social Sciences.
I would like to thank Leo Douw, Stefan Landsberger, Luo Hongguang, Ma
Rong, and Frank Pieke for their hospitality and the participants in these sem-
inars for questions, comments, and critiques. Their input greatly strength-
ened the book; all the remaining weaknesses and errors in the study, needless
to say, are entirely my own responsibility.
Two respected scholars carefully reviewed the manuscript for Stanford
University Press, providing me with long lists of penetrating questions and
helpful advice. I cannot thank them in person because they remain anony-
mous, but I want them to know how much I appreciate their contributions.
As early as 1997, Muriel Bell of the Stanford University Press was one of the
most enthusiastic supporters of this project, and her subsequent encourage-
ment, attention, and editorial expertise carried me through the entire course
XVl PREFACE

of writing. As always, I am grateful to Nancy Hearst, whose moral support

and skillful editorial assistance made the writing much more pleasant. I also
want to thank Jonathan Jackson for compiling the index.
Part of Chapter 3 is based on materials from my article "Courtship, Love,
and Premarital Sex in a North China Village," published in The China Jour-
nal, no. 48 (2002). Part of Chapter 4 was previously published under the title
"The Triumph of Conjugality: Structural Transformation of Family Rela-
tions in a Chinese Village," in Ethnology 36, no. 3 (1997). Chapter 8 is based
on an article that appears in the French journal Etudes Rurales (nos. 161-62,
July 2002), which is entitled "Planning Birth: Changes in Fertility Culture in
a Chinese Village." I thank these journals for their permission to include the
materials here.
Thanks are due to the following institutions for financial support: the
National Science Foundation, the Wenner-Gren Foundation, the Chiang
Ching-kuo Foundation for International Scholarly Exchange (USA), the
University of California President's Office (for its Research Fellowship in
Humanities), the International and Overseas Studies Program at UCLA, and
the Academic Senate of UCLA. I also owe thanks to my colleagues in the
Anthropology Department at UCLA for providing a collegial and stimulat-
ing intellectual environment. I am grateful to Department Chair Joan Silk
and Dean Scott Waugh in the Division of Social Sciences for permitting me
to take a year-long leave in 2000 to concentrate on writing.
Finally, my deepest appreciation goes to Betty Leung, my fiancee. When
Betty and I met in 1999,1 had just started to draft the first chapter, and now,
while completing this preface, I am looking forward to our wedding in August.
Over the past three years Betty has transformed my life with laughter and love.
It is thus needless to say anything more about her contribution to this book.

YUNXIANG YAN
LOS ANGELES, FEBRUARY 2OO2
PRIVATE LIFE UNDER SOCIALISM
Introduction

The Chinese Family and the Study of Private Life

On a summer day in 1990, Mr. Hu Yanjun, a 46-year-old man in Xiajia vil-

lage, wrote the following eulogy to the ideal family:
The family is a harmonious whole
that is created by the universe;
containing the personal happiness of family life,
it is the origin of well-being
and the symbol of warmth.1
Later that year Mr. Hu renovated his house and landscaped the court-
yard, constructing a billboard-like decorative wall (about two by two-and-a-
half meters) on the right side of a formal entrance arch, facing the street. He
then had a local artist inscribe his family eulogy onto the wall. Underneath
the huge Chinese character yY# (family) that occupied half of the wall, the
main text was inscribed in a classical style of calligraphy in red against a yel-
low background with sky-blue and white borders. Mr. Hu's original purpose
 THE CHINESE FAMILY

was to use his family ideal to educate his children and grandchildren about
the beauty and significance of the family in one's life, something he had been
trying to do for years. Once the project was completed, the inscription on
the wall and his new courtyard became a landmark in Xiajia and the neigh-
boring villages.
Having worked as a main cadre in Xiajia for many years before his retire-
ment in 1988, Mr. Hu is a very capable man and probably the most power-
fid father in the village, living in a rich and close-knit extended family of ten
people in three generations, including two daughters-in-law and three grand-
children.2 Although he did not even completed his secondary school educa-
tion because of family difficulties in the early 19605, Hu likes to read and
write. He has written several dozen poems and short essays expressing his
feelings and his understanding of life, people, and the world, which he shares
with his children and other relatives. Mr. Hu has always been concerned
with the emotional and spiritual quality of family life. He told me that, in ad-
dition to frequent family meetings on important issues, he spent his leisure
time with his two married sons, watching TV, listening to popular music, or
playing mahjong. He considers his best and most successful effort to be a
special family party for family members and relatives visiting from other vil-
lages and cities during the 1991 Chinese Spring Festival.
With more than forty people in attendance, the family party began at
7:30 P.M. and ended at 2:00 A.M the next day. It was full of fun, laughter, and
emotional communication. Most of the younger guests—Mr. Hu's children,
nephews, and nieces—contributed entertainment, including speeches, songs,
and jokes, which they worked on for weeks before the party. Mr. Hu had as-
signed a special task to his only daughter (who then at the age of 19 was study-
ing at an occupational school): to comment on the strengths and weaknesses
of each family member. To everyone's surprise, when commenting on her fa-
ther, she criticized him for not treating her mother well. She said, as quoted
by Mr. Hu: "In my memory you rarely talked with my mother unless you
had to; you always went out after dinner, spending time with your colleagues
instead of with my mother. Now you have retired from the office and have
begun to spend more time with us, but you still do not spend much time
with my mother." The daughter's open criticism, as Hu recalled, shocked him
and moved his wife to tears. For a while, everyone at the party was speech-
less. After that encounter Mr. Hu indeed tried to improve his own conjugal
Another Random Scribd Document
with Unrelated Content
 jJJ Windows 3.1 Secrets [Colors] section (Controls the color
of window elements, such as title bars.) Name=red green blue Set
the following in Control Panel: ActiveBorder=128 128 128
ActiveTitle=0 64128 AppWorkspace=255 255 232 Background=192
192 192 ButtonFace=192192192 ButtonShadow=64 64 64
ButtonText=0 0 0 GrayText=192192 192 Hilight=64 64 64
HilightText=255 255 255 lnactiveBorder=255 255 255
lnad:iveTitle=255 255 255 Menu=255 255 255 MenuText=0 0 0
TitleText=255 255 255 Scrollbar=224 224 224 Window=255 255 255
WindowFrame=0 0 0 WindowText=0 0 0 0=no color; 128=1/2
intensity; 255=full intensity. Inside the foreground window frame.
The title bar of the foreground window. Area child windows are
drawn on, as in Program Manager. The Windows Desktop. Makes the
face of dialog box buttons light grey. Makes lower-right shadows of
buttons dark grey. Makes text of buttons, such as "OK," black. Makes
unavailable menu items light grey (note spelling). Makes highlighted
background dark grey (note spelling). Makes highlighted text white
(note spelling). Inside the frame of background windows. The title
bar of background windows. Area underneath menu choices. The
menu choices themselves. Text inside the title bar. Color on either
side of the "thumb" in scroll bars. Background area of an
application's main "client" window. Lines that make up the edges of
a window. Text inside "client" windows. [Compatibility] section (Lists
applications with minor bugs that Windows App Hack will work
around.) Appname=hexadecimal-flags Specifies application name
and Windows 3.1 adjustment (undocumented). SYSTEM.INI
Reference Chart [Boot] section Specifies driver files in \SYSTEM or
other directory. 286grabber=vgacolor.gr2 386grabber=vga.gr3
CachedFileHandles=12 comm.drv=comm.drv display.drv=vga.drv
drivers= filename fixedfon.fon=vgafix.fon fonts.fon=vgasys.fon Real
and standard driver that displays (grabs) DOS sessions. 386
enhanced driver that displays DOS sessions. Number of files
Windows holds in memory; 2- 12. Serial communications driver.
Driver for a specific video resolution. Determines filename or alias
for installable drivers. Fixed-pitch font used in menus by Windows
2.x apps. Proportional font used in menus by Windows 3.x apps.
 Chapter 20: The Windows MNI Files
keyboard.drv=keyboard.drv Ianguage.dll=/ir70 default}
mouse.drv=mouse.drv network.drv=/ir70 default}
oemfonts.fon=vgaoem.fon shell=progman.exe sound.drv=sound.drv
syste m . d rv=syste m . d rv TaskMan.Exe=taskman.exe Driver for a
specific flavor of keyboard. Dynamic Link Library for language
support (U.S., if blank). Driver for a specific flavor of mouse. Driver
for network support (no support, if blank). Font file that displays the
IBM PC-8 character set. Program that starts applications on LOAD=
and RUN= lines. Driver that makes the "beep" (or other sounds).
Hardware driver; replaced by Adobe Type Manager, etc. Specifies the
app that appears when you double-click the Desktop. [Boot.d section
{Text used in Windows Setup to display current choices.)
display.drv=//70 default} network.drv=/ir7o default}
Ianguage.dll=/Jr70 default} keyboard.typ=/A70 default}
mouse.drv=/ir7o default} Display resolution; for example, VGA.
Network; for example, No Network Installed; Novell Netware; etc.
Language selected; for example, English (American). Keyboard; for
example, Enhanced 101 or 102 key US and non-US. Mouse; for
example, Microsoft or IBM PS/2. [Drivers] section (Aliases for drivers
mentioned in the Drivers- entry in the [Boot] section )
a\\as=filename {options} Aliases for drivers in [Boot] section, so a
driver can have parameters. [Keyboard] section Settings for
differences between keyboards. keyboard.dll=/Jr70 default}
oemansi.bin=/no default} type=4 subtype=0 Filename that handles
keyboard (internal, if blank). Filename for non-U.S. characters
(internal U.S., if blank). Specifies major keyboard types. 1=IBM PC
or XT 83-key keyboard. 2=0livetti ICO 102-key keyboard. 3=IBM AT
84- or 86-key keyboard. 4=IBM enhanced 101- or 102-key keyboard.
Distinguishes between flavors of major keyboard types. Type 1,
Subtype 2=83-key Olivetti M24 or AT&T 6300 301 . Type 1, Subtype
4=AT&T 6300 Plus 302-type keyboard. Type 2, Subtype 1=102-key
Olivetti M24 ICO-type. [mcij section (Lists the drivers that are
installed for the Multimedia interface.) Name=filename Description of
an application that plays multimedia files. [NonWi section ( Controls
DOS sessions.) HJ CommandEnvSize=160 Hj DisablePositionSave=0
Hj FontChangeEnable=1 NetAsyncSwitching=0 ScreenLines=25
Overrides environmental size set in SHELL= command. 0=Saves
position of open DOS windows; 1=Doesn't save. Allows
customization of screen fonts for DOS sessions. Prevents switching
away from applications that use async network BIOS calls. Set to 1
to enable switching away. Lines displayed in DOS sessions; apps can
override this.
 740 Windows 3.1 Secrets SwapDisk=c.iaf/recfo/y Drive and
directory Windows copies DOS sessions to when switching away in
real and standard mode. If blank, uses the SET TEMP= directory or,
if none, the Windows directory. [Standard] section (Controls
Windows in standard mode.) FasterModeSwitch=False lnt28Filter=10
NetHeapSize=8 PadCodeSegments=0 Reserved LowMemory=0
Stacks=12 StackSize=384 Set to True for Zenith Z-248 and Olivetti
M-250-E. Case-specific. Every tenth interrupt 28 (DOS idle) is sent to
TSRs loaded before Windows. Larger values improve Windows'
speed but hang network drivers. Setting to 0 halts all TSRs. Size in
kilobytes of buffer for network transfers (if any network). Set to 1 to
work around bugs in Intel's C2 version of 80286. Sets aside n K for
certain, rare non-Windows applications. 8-64: Number of interrupt
reflector stacks used by DOS Extender. Size in kilobytes of reflector
stacks used by DOSX.EXE. [386Enh] section Disk (Controls
temporary swap file and disk space.) |U HardDiskDMABuffer=0 |H
MaxDMAPGAddress=OFFFh MaxPagingFileSize=w7W7 |H
MCADMA=False MinUserDiskSpace=500 JH OverlappedlO=True
Paging=yes PagingDrive=C VirtualHDIrq=on Kilobytes for DMA
buffer; 64 for MCA and DMA channel 3. Maximum physical page
address that can be used for DMA. Limit in kilobytes to temporary
swap file. Use 1024 or higher. True=Windows should use MCA
extensions to DMA. Size in kilobytes Windows leaves free when
creating a swap file. Allows several read and write requests to disk
before first is finished. If no, prevents swap file and disables 386
memory features. Drive letter for swap file. If blank, uses Windows
drive. Set to off to make Windows write to drives through BIOS.
[386Enh] section — DOS Apps (Statements that affect DOS sessions
[virtual machines].) AIIVMsExclusive=false AltKeyDelay=.005
AltPasteDelay=.025 Hj AutoRestore Screen=True HJ
AutoRestoreWindows=False CGA40WOA.FOI\l=///eA?3/77e
CGA80WOA.FON=///e/73/77e HJ DOSPromptExitlnstruc=True
EGA40WOA.FON=///e/7aA77e EGA80WOA.FON=///e/7ame
FileSysChange=on If true, DOS apps run exclusive full-screen,
ignoring PIFs. Increase if app requires more time to process the Alt
key. Increase if app can't paste after receiving an Alt key. Specifies
whether Windows should update DOS sessions' screens.
True=Windows saves Windows screen when switched to DOS. Fixed-
pitch font for apps in CGA 40-column mode. Fixed-pitch font for apps
in CGA 80-column mode. Displays message box when DOS session
starts. Fixed-pitch font for apps in EGA 40-column mode. Fixed-pitch
font for apps in EGA 80-column mode. Forces DOS apps to inform
File Manager of all disk writes.
 Chapter 20: The Windows *.INI Files m g§
ldleVMWakeUpTime=8 KeyBoostTime=.001 KeyBufferDelay=.2
KeyldleDelay=5 KeyPasteDelay=.003 KeyPasteTimeout=1
MinTimeSlice=20 PerVMFiles=10 ||j TrapTimerPorts=False ||
UseROMFont=True VCPIWarning=True ||] VGAMonoText=True j||
VideoBackgroundMsg=True Hj VideoSuspendDisabled=False
WindowllpdateTime=50 |g WOAFont=dosapp.fon g§
XMSUMBInitCalls=True Seconds between Windows sending timer
interrupt to DOS sessions. Time an app gets increased priority with
each keystroke. Seconds Windows waits when app's keyboard buffer
is full. Seconds Windows ignores idle calls after you press a key.
Seconds Windows waits between pasting keystrokes. Seconds
Windows waits before using slow paste method. Smallest number of
milliseconds a DOS session gets. Increase to 20 if DOS app needs
more file handles. Windows keeps correct time, even with game app
running. Use the soft font in video ROM for displaying messages.
Displays a message when starting a DOS-extender app. Forces
Windows to use B000-B7FF, the monochrome text area. Windows
displays a message when a background app is suspended. Whether
or not to suspend appswith a corrupted display. Priority that a
windowed DOS app receives. Tip: Try 200. Which font to use in DOS
sessions. Can be installed in Control Panel. Whether or not Windows
should call UMB management routines. [386Enh] section — Drivers
{Internal Windows drivers and installable filenames.) m
CGANoSnow=no Dev\ce=filename or "internal Display=*vddvga
Ebios=*ebios EISADMA=no Global=>W4 IRQ9Global=no
Keyboard=*vkd KybdPasswd=False KybdReboot=True Local=C0N
Mouse=*vmd MouseSoftlnit=true NMIReboot=false If yes, Windows
writes to CGA displays so as to avoid snow. Driver Windows loads,
from the \SYSTEM or other directory. Display handler. Same as
DEVICE=. Extended BIOS handler. Same as DEVICE=. Set to no to
turn off direct memory access on EISA PCs. Device name, in all caps,
forced to be global to the system. Set to yes if floppy drive reads
hang your system. Keyboard handler. Same as DEVICE=.
True=Enables Virtual Keyboard Device for PS/2 passwords.
True=Ctrl+Alt+Del reboots computer; False=only exits Windows.
Device name, in all caps, handled separately in each session. Mouse
handler. Same as DEVICE=. Disable if a mouse in a windowed DOS
app is a problem. If true, causes a reboot on a nonmaskable
interrupt.
 Windows 3.1 Secrets TranslateScans=no UselnstFile=false
Set to yes to correct some nonstandard keyboards. Obsolete. If true,
Windows looks for INSTANCE.386 file. [386Enh] section — Memory
(Statements that affect Windows' memory allocation.} |g
A20EnableCount=1 g} AIIEMSLocked=False §§
ALLXMSLocked=False DMABufferln1MB=no DMABufferSize=16
DualDisplay=no E M M Exc lu d e=xxxx-yyyy E M M I n c I u d
e=xxxx-yyyy E M M P a g e Fr a m e =xxxx EMMSize=65536
HighFloppyReads=yes lgnorelnstalledEMM=no j||
LocalLoadHigh=False H LRULowRateMult=10 ||
LRURateChngTime=1QQ00 |g LRUSweepFrequency=250 Jj|
LRUSweepLen=1024 ||j LRUSweepLowWater=24 JU
LRUSweepReset=500 MapPhysAddress=n || MaxPhysPage=/?/?/7/7
|| MinUnlockMem=40 NoEMMDriver=false H Page0verCommitt=4 |H
PerformBackfill=Auto ||J ReservedHighArea=xxxx-yyyy
ReservePageFrame=true HJ ReserveViideoROM=False jgj
R0MScanThreshold=20 SystemROMBreakPoint=true HJ
UseableHighArea=AXAx-yyyy Identifies the handler HIMEM.SYS is
using for extended memory. True=Locks all expanded memory;
useful for caches in expanded. True=Locks all extended memory. If
yes, places buffer below 1 MB for 8-bit bus master cards. Memory in
kilobytes for direct memory access transfers. If yes, Windows always
leaves B000-B7FF alone. Excludes adapter segment memory from
Windows' use. Forces Windows to include memory it otherwise
ignores. Specifies the starting address for the 64K page frame.
Amount of memory for mapping as expanded memory. Turns DMA
verify to E000-EFFF into a read. If yes, forces Windows to use
unknown memory manager. Windows uses all UMBs, unless set True.
Value to determine the LRU paging frequency; 1 - 65535.
Milliseconds the Virtual Memory Manager switches paging rate.
Milliseconds between LRU sweep passes. Length in memory pages of
each pass. Number of free pages below which the sweeper is
activated. Time factor for computing ACC bit reset. Specifies range in
megabytes to allocate linear address space. Hexadecimal number of
maximum physical page VMM can manage. Minimum memory that
must remain available to resume a VMM. If true, Windows omits
loading its memory manager. Physical memory times. This is
maximum virtual memory; 1 - 20. Allows Windows to determine
whether to backfill 51 2K machines. Range of memory that Windows
will not scan. Puts buffers below 640K, instead of stealing from EMS.
True=Video ROM exists in pages C6 and C7. Method used to
determine whether an area of memory is ROM. Uses break point
above F000. Memory range Windows scans for unused addresses.
 Chapter 20: The Windows MNI Files ^P [386Enhj section —
Networks (Statements that affect Windows and networks.}
lnDOSPolling=no lnt28Critical=true NetAsyncFallback=false
NetAsyncTimeout=5.0 NetDMASize=0 NetHeapSize=12
Network=*vnetbios, *dosnet PSPIncrement=2
ReflectD0Slnt2A=false TimerCriticalSection=0 TokenRingSearch=true
UniqueDOSPSP=false Set to yes if software requires critical section
for INT21. Disable if software needs critical section for INT28. If
true, forces Windows to allocate memory for NetBIOS. If
NetAsyncFallback=true, seconds for critical section. DMS buffer in
kilobytes for NetBIOS (default=32 on MCA). Size in kilobytes for
network data transfer buffers. Internal device to handle networks, or
device filename. Number of 16-byte increments to add to new DOS
sessions. If true, Windows sends INT2Ato network software.
Milliseconds Windows halts during some network activities. Set to
false if this search conflicts with a device's memory. Set to true to
start apps as specified by PSPIncrement. [386Enh] section — Ports
(Statements that configure com and parallel ports.)
C0MnAutoAssign=2 COMnBase^aGtafress CQMBoostTime=2
COMA7Buffer=128 CQMdrv30=False COM/?IRQ=x
COMIrqSharing=false C0MA7Protocol= LPT/7AutoAssign=60
MaxC0MPort=4 SGrabLPT=/7 Seconds Windows holds com port after
one app uses it. 0=Any app can use that com port at anytime.
-1=Windows asks before it assigns the port to any app. Set
C0M3Base=3E8h and C0M4Base=2E8h for com apps. Milliseconds to
allow app to process com port interrupts. Number of characters
buffered for each com port. False=Uses Windows Virtual COM
Driver; True=Uses other driver. C0M1 & 3 are usually 4, COM2 & 4
are usually 3. Set to -1 to disable a com port if it conflicts with
another device. Set to true on MCA and EISA machines that share
IRQs. Set to XOFF only if your transfers consist of plain text.
Seconds Windows holds parallel port after one app uses it. 0=Any
app can use that parallel port at anytime. -1=Windows asks before it
assigns the port to any app. Maximum number of COM ports
supported in 386 mode. Forces printer interrupts on LPT/7 to go
through Windows. [386Enh] section — System (Statements that
control Windows' own "virtual machine. ") H
BkGndNotifyAtPFault=True H MaxBPs=200 Hj SyncTime=True JU
SystemVMPriority=1 00,50 Windows warns when an app might
corrupt memory. Maximum number of break points that can be used
by the VMM. Windows periodically synchronizes its time with the
CMOS clock. Foreground and background priority for virtual
machines.
 Windows 3.1 Secrets SysVMEMSLimit=2048
SysVMEMSLocked=no SvsVMEMSRequired=0
SysVMV86Locked=false SysVMXMSLimit=2048 SysVMXMSLocked=no
SvsVMXMSRequired=0 WindowKBRequired=256
WindowMemSize=-1 WinExclusive=no WinTimeSlice=1Q0,50 Limit in
kilobytes on expanded memory Windows can claim. 0=No expanded
memory. — 1=Unlimited expanded memory. Allows Windows to
swap its expanded memory to disk. Expanded memory in kilobytes
required to start Windows. Allows Windows to swap its virtual
memory to disk. Limit in kilobytes on extended memory for drivers.
-1 =No limit. Allows Windows to swap extended memory to disk.
Extended memory in kilobytes required to start Windows.
Conventional memory in kilobytes required to start Windows. Allows
Windows to claim all conventional memory. Set this to a positive
value in kilobytes if Windows can't load in 386 mode. If yes,
Windows halts all DOS sessions when in foreground. Foreground,
background time (1 - 10000) for Windows apps. Summary In this
chapter I presented a few pieces of information on settings in your
WIN.INI and SYSTEM.INI files, including: ► Descriptions of some
little-understood settings in WIN.INI and SYSTEM.INI. Quick
reference charts that summarize all the settings in WIN.INI and
SYSTEM.INI, in one line if possible, to give you a way to glance
down the list looking for items that might require attention in your
specific system. For detailed information on each of these settings,
print the WININI*.WRI and SYSINI*.WRI files that were copied to
your hard drive when you installed Windows.
 Chapter 21 Converting Your Company to Windows In this
chapter . . . I describe a detailed procedure for converting
networked PCs in your company from DOS-based to Windows-based
workstations, including: **■ Determining the benefits that your
company can derive by converting all your PCs — or as many as
possible — to a networked Windows configuration. #* Evaluating
and preparing your company's PCs for the conversion to Windows,
including hardware upgrades that should be considered before
switching to Windows. ► Installing Windows and customizing its
WIN.INI, SYSTEM.INI, and other files for use in a company-wide,
networked environment. » Tips for customizing Novell Netware,
Banyan Vines, and LAN Manager networks for use in a networked
Windows installation. (For more information, see the Networks
chapter.) 1 he release of Windows 3 in May 1990 and its striking
success in the software marketplace have created two kinds of
companies, I've found. One type of company looked at Windows,
liked what it saw, and started converting almost everything in the
place to Windows. At companies like this, a funny thing has
happened. People who actually like Windows have emerged as
evangelists, similar in some ways to the feeling that Macintoshes
evoked in early Apple users. The other type of company isn't really
captivated by Windows, and may have succeeded in keeping
Macintoshes off the desktops all these years, too. But this kind of
company has been forced to evaluate and adopt Windows in some
form or another. Either its users have started requesting
 Windows 3.1 Secrets it, or other companies it deals with
are asking questions like, "Can we send our .PCX files over for you to
review?" Today, a company with no PCs that run Windows is almost
like a company without a fax machine. Windows is everywhere. Ever
since Microsoft shipped more than four million copies of Windows
3.0 in its first year, various market research firms have been
increasing their estimates of second-year sales. Eight million to 10
million copies of Windows is the range of annual sales now projected
by these firms. As companies become familiar with Windows and
learn how it can best be installed and used on corporate networks,
Windows is creeping onto desktops that never before saw anything
but DOS's character-based look and feel. The one major factor that
seems to be working against the growing popularity of Windows is a
vague fear of running Windows over a company's local area network
(LAN). "Windows is too slow on a network," is a fear that is
commonly expressed. "Windows is too hard to manage on a
network," or "You can't run DOS applications under Windows," are
other refrains that are frequently heard. Each of these statements is
actually a half-truth that haunts the acceptance of Windows as a
feature of PC computing in the 1990s. Each has a basis in personal
computing folklore, but like many myths of folklore, these Windows
myths melt away when a little light shines on them — as described
in this chapter. How Companies Benefit (or Suffer) from
Standardizing on Windows Windows and Windows applications
generally work better on local area networks than older DOS
applications do. The differences between Windows applications and
DOS applications appear primarily in three categories: (1) the
"networkability" of Windows, (2) the ability of network users to
move to different desks within the same company and use the same
Windows setup they are used to at their own desk, and (3) the ease
of administering Windows applications across the LAN.
 Chapter 21: Converting Your Company to Windows
Networkability Windows and most Windows applications are
somewhat more "networkaware" than older DOS applications.
Windows applications usually store a list of user preferences in an
"initialization" file with the extension .INI. (Many applications store
their preferences in Windows' master WIN.INI file if they don't write
an .INI file of their own.) These .INI files do not need to be stored in
the same directory as the corresponding application. If a Windows
application does not find its .INI file in the current directory, it
usually looks for a file of that name anywhere on the user's Path.
This allows different network users to load the same application from
the same network directory, but use separate initialization files that
store their personal preferences. The .INI file used is based on
whatever directories are included in a user's Path statement.
Compare this with older DOS applications. To start Lotus 1-2-3 2.x
with a particular set of preferences, for example, requires that you
start the program with a parameter file on the command line (such
as 123 MYPREF.SET). For a user to move from one machine to
another, type "123," and still load their preferred configuration, this
MYPREF.SET file would need to be copied to every other user's desk.
User Mobility Moving from one desk to another has become fairly
common for office workers in companies today. A large percentage
of the workforce is made up of temporary help, especially clerical
workers brought in to handle peaks of paperwork. Additionally, more
business presentations are now made on a computer screen, instead
of being sent out to a service bureau for color slides or overhead
transparencies. It is a major advantage for the creator of an on-
screen presentation to be able to walk to another PC, log onto the
network with a password, and have access to the same utilities and
files as would be expected at his or her own desk. Windows
addresses fairly well this issue of "user mobility." When a person logs
onto the network, his or her user ID can be used by the network to
set the correct Path. This Path points to network directories
containing that person's particular .INI files, as well as the
applications he or she is authorized to use. With a few exceptions,
Windows allows the complete independence of the person using the
network from the hardware resources of the particular workstation
that person is currently using. (Some workarounds for the
exceptions are described later in this chapter.) Wm
 Windows 3.1 Secrets Ease of Administration The mobility
that networked Windows potentially offers to individual users is
magnified by some benefits enjoyed by network administrators. If all
network users' .INI files are stored in network directories, for
example, it becomes a simple matter to make changes in
configurations when necessary, even when hundreds or thousands of
users are involved. If an improved video driver is obtained, switching
all users to that driver can be as easy as making one copy to a
network server, then writing an automated script routine to change
one line in SYSTEM.INI from DEVICE=DRIVERl to
DEVICE=DRIVER2. Compare this with the problem of making a one-
line change in the CONFIG.SYS file of every workstation. This file is
located on a hard drive in each PC (unless the workstations load
DOS from a boot disk or a boot ROM over the network). To change
to a new driver in CONFIG.SYS, someone must travel to every single
machine and edit the change by hand, or use a cumbersome remote
editing procedure. Networking Windows also greatly eases the
process of upgrading to a new version of software company-wide.
When Windows and Windows applications are installed on and run
from network servers, installing a new package and changing users'
network scripts to access that new directory can take as little as one
or two days. When the same package needs to be installed on
hundreds or thousands of individual hard drives, however, the
process can take months. (For a cost comparison of running
Windows on networked workstations vs. stand-alone installations,
see the sidebar, "A Tale of Two Networks.") Determining the Best
Configuration to Overcome Network Hurdles While the benefits of
networkability, mobility, and ease of administration are potentially
available to every company that converts to Windows, these benefits
do not flow to you automatically out of the box.
 Chapter 21: Converting Your Company to Windows One
reason that rumors of performance and incompatibility issues have
become common about Windows is that, if you install Windows with
its factory default settings, it can be slow and troublesome on a
network. Windows ships with certain built-in defaults that are
designed for the average stand-alone PC. Fortunately, these defaults
are usually simple to cure by merely adding one or two lines to
Windows' WIN.INI or SYSTEM.INI files. Additionally, the creators of
Windows attempted to give users the greatest flexibility by storing
personal preferences in the WIN.INI file, while moving the
specification of hardware drivers to a separate SYSTEM.INI file.
Theoretically, this should allow you to move to different machines on
the network, with Windows loading your personal WIN.INI every
time, but running the SYSTEM.INI appropriate for the configuration
of the PC you've logged on at. But this separation of powers is not
yet perfect, unfortunately. The WIN.INI file still contains some
hardware-specific information. In particular, WIN.INI defines what
hardware ports are in use on a machine and what printers are
attached to which ports. Additionally, WIN.INI specifies the video
resolution of the screen fonts that will be used (EGA vs. VGA, for
example). SYSTEM.INI, on the other hand, includes several pieces of
information on personal preferences that have nothing to do with
hardware. These preferences include what Windows shell you wish
to use (Program Manager or some other utility), and whether you
want to load drivers for such programs as Adobe Type Manager and
the Intermission screen saver. In the remainder of this chapter, I
describe in some detail the workarounds necessary to make these
and other Windows issues more manageable on your company's
network. The following procedures are based on discussions with
numerous system administrators at companies that have either
converted nearly entirely to Windows or made major steps in that
direction. In addition, some of the recommendations are derived
from a major study — "Challenges in Migrating to the Windows
Environment," released in 1990 by Corporate Software — of 14
Fortune 1000 companies that moved a total of 200 workers to
Windows simultaneously. (Corporate Software, Inc., 275 Dan Road,
Canton, MA 020219879,617-821-4500.)
 US* Windows 3.1 Secrete. A Tale of Two Networks Two
companies convert from DOS to Windows — but these companies
decide to do so in very different ways. Both companies have 100
people who use PCs, and both companies have those PCs connected
to a local area network (LAN). Company A chooses to install and run
applications from the network. Company B, on the other hand, uses
the network primarily for e-mail, and loads application programs and
data on hard drives within each of the 100 networked PCs. The
following examples illustrate the differences in costs that affect each
company. In each case, the cost of microcomputer managers' time is
estimated at $35,000 per year, plus $15,000 in benefits, desk and
office space, phone and utilities, supervisory time and other
overhead, for a total of $50,000 in total outlay, or about $200 per
day. In every case, Company B — which installed Windows
applications and data on the local hard disks of individual PCs —
paid 3 to 10 times the costs of Company A, which installed
everything on network server drives. In companies involving more
than 100 networked PC users, the difference in costs would be even
greater. In the real world, of course, microcomputer managers who
are assigned the task of upgrading PC software may take much more
than, say, one hour per PC. All real-world problems magnify the cost
differences between these two approaches even further. Installing
Windows Both companies evaluate Windows and decide to convert
to Windows applications. Company A $800 (Networked Windows)
Company B $2,500 (Stand-Alone Windows) Company A installs the
complete set of Windows disks to their four network servers, then
creates SYSTEM.INI files for different classes of hardware, such as
VGA vs. Super VGA users, and so on. Once these files are set up
over a period of about three days, an additional one day is spent
adding the directories N:\WlNDOWS and N:\INI to the Path in the
network scripts for all 100 users, for a total of four days. Company B
installs Windows to the local hard drive of all 100 workstations,
requiring about one hour each, for a total of 12.5 days. Installing a
Word Processor and a Spreadsheet Program Out of 100 PC users,
both companies have 25 users who need to use a word processing
program on a daily basis and 25 others who need a spreadsheet
daily. The rest of the 100 workers need access to these programs
only once every few days to examine or print a file created by
someone else. Company A $450 ( Networked Windows) Company B
$5,000 (Stand-Alone Windows) After testing, Company A installs
both programs on network servers, requiring two days, and adds
icons for these programs to a master Program Manager group
window, requiring two hours, for a total of 2.25 days. Company B
installs these two programs to the local hard disk of each of the 100
workstations, requiring about one hour each, for a total of 25 days.
(continued)
The text on this page is estimated to be only 27.32%
accurate

Chapter 21: Converting Your Company to Windows Uf

Upgrading Hard Drives in User Workstations The installation of
Windows and the two applications consumes about 20MB of hard
diskspace. Company A $ 1 ,800 Company A used 20MB of hard disk
space on each of its four servers, and (Networked Windows) did not
require any increase in capacity, it did purchase an additional 4MB of
RAM to act as a performance-improving disk ca che in each of their
four servers, at a total cost of $1,600. The installation required one
day, costing $200. Company B $12,500 (Stand-Alone Windows)
Company B found that about half of its 100 PCs required a larger
hard disk in order to install Windows and the two applications. Fifty
additional disks were purchased at a cost of $200 each, for a total of
$10,000. The PCs to be upgraded needed to be opened so the new
disks could be installed, requiring one hour each, for a loss of 12.5
days, or $2,500. Changing a Line in Each User's SYSTEM.INI File
Both companies discover that a bug in a device driver requires that
they replace one line in SYSTEM.lNi with a new line that loads an
improved driver file. Company A $100 (Networked Windows)
Company B $600 (Stand-Alone Windows) Company A copies the new
driver to the network servers, requiring one hour, then writes a script
file to replace the old line with the new line, requiring three hours to
write and run, for a total of 0.5 days. Company B copies the driver to
the hard drive of each of the 100 workstations and runs the editing
script on each workstation, requiring onequarter hour each, for a
total of about three days. Upgrading the Word Processor A much-
improved version of the word processor is released, and testing
shows it has features making it imperative that both companies
upgrade. Company A $200 (Networked Windows) Company B $2,500
(Stand-Alone Windows) Company A installs the new disks to the
network servers, requiring one day. Because the new application
directory has been given the same name as the old, users
automatically run the newer version the next time they log on.
Company B installs the new version over the old version on each of
the 1 00 workstations, requiring one hour each, for a total of 1 2.5
days. (continued)
The text on this page is estimated to be only 29.40%
accurate

Windows 3.1 Secrete. Restoring a User's Damaged

Database Files Someone used Ctrl+Alt+Dei to exit a DOS database
program under Windows, and a 2,GG0-record database of customer
addresses is now corrupted and will not load. Company A $25
(Networked Windows) Company B $1,100 (Stand-Alone Windows)
Since Company A stored this data file on a network server, it simply
restores the database from yesterday's backup tape, requiring one
hour. Since Company B stored this data on a local hard drive, and
local hard drives are rarely backed up, the professional staff spends
four hours trying to recover the corrupted file with a disk utility, then
decides to hire a temp to retype the address list from an old printout
and proofread the result, requiring five days, for a total of 5.5 days.
(Networked Windows) Licensing Expense for Concurrent Use of
Copies of Application Software According to international copyright
laws, companies must pay for the number of copies of copyrighted
software that they make, and the Software Publishers Association
(SPA) enforces this provision. Company A $20,250 Company A uses
— on each of their four LAN servers — a $1 ,000 software metering
utility, which costs a total of $4,000. This metering utility shows that
only 25 people at any one time are allowed to use the word
processor, and 25 may use the spreadsheet program. Company A
pays for 25 copies of the word processor and 25 copies of the
spreadsheet at $250 each, which adds up to $1 2,500. Additionally,
since only 50 people at any one time are actually running Windows,
Company A buys only 50 copies of Windows at$75 each for a total of
$3,750. This represents a grand total of $20,250 for software
licensing. Company B made 100 copies of both of the application
programs and Windows itself, since copies were made to all users'
local hard disks whether they needed to run Windows every day or
only once in a while. Since Company B does not want to be raided
by the SPA, it pays $57,500 for these 100 copies of the three
programs. Company B $57,500 (Stand-Alone Windows) Intangible
Differences People in Company A have access to virtually all of their
Welcome to our website – the ideal destination for book lovers and
knowledge seekers. With a mission to inspire endlessly, we offer a
vast collection of books, ranging from classic literary works to
specialized publications, self-development books, and children's
literature. Each book is a new journey of discovery, expanding
knowledge and enriching the soul of the reade

Our website is not just a platform for buying books, but a bridge
connecting readers to the timeless values of culture and wisdom. With
an elegant, user-friendly interface and an intelligent search system,
we are committed to providing a quick and convenient shopping
experience. Additionally, our special promotions and home delivery
services ensure that you save time and fully enjoy the joy of reading.

Let us accompany you on the journey of exploring knowledge and

personal growth!

ebookfinal.com