cmdbyk@pmvax.weeg.uiowa.edu (Karl Boyken) (05/24/91)
I didn't see this in the FAQ, so: just how do you get SYSEDIT to run? I've
tried to add it to a group, but it comes up as a DOS icon. I've tried
creating a .PIF. Either way, I get an app error when I try to run it. Could
someone please mail me the solution? TIA.
BTW, this would be a good one for the FAQ list, if it's not already there.
** _My_ views, no one else's--except those I plagiarize. **
Karl Boyken, Project Analyst | "Distant cousins, there's a limited supply,
State Health Registry of Iowa | and we're down to the dozens, and this is why:
Iowa City, IA | big-eyed beans from Venus--oh my, oh my!"
cmdbyk@pmvax.weeg.uiowa.edu | Captain Beefheartpburke@vms.macc.wisc.edu (Peter Burke, MIC, 263-7744) (05/24/91)
In article <6198@ns-mx.uiowa.edu>, cmdbyk@pmvax.weeg.uiowa.edu (Karl Boyken) writes... >I didn't see this in the FAQ, so: just how do you get SYSEDIT to run? I've >tried to add it to a group, but it comes up as a DOS icon. I've tried >creating a .PIF. Either way, I get an app error when I try to run it. Could >someone please mail me the solution? TIA. > >BTW, this would be a good one for the FAQ list, if it's not already there. > > ** _My_ views, no one else's--except those I plagiarize. ** >Karl Boyken, Project Analyst | "Distant cousins, there's a limited supply, >State Health Registry of Iowa | and we're down to the dozens, and this is why: >Iowa City, IA | big-eyed beans from Venus--oh my, oh my!" >cmdbyk@pmvax.weeg.uiowa.edu | Captain Beefheart I don't know what is wrong with your windows setup, but usually sysedit can be installed by simply adding it to a program group - either by typing the path in or by browsing through the directories and highlighting the app. I have done this on at least 20 differently configured systems and always had the blue sysedit icon come up. Maybe it's in the wrong directory? Peter
jcmorris@mwunix.mitre.org (Joe Morris) (05/24/91)
cmdbyk@pmvax.weeg.uiowa.edu (Karl Boyken) writes: >I didn't see this in the FAQ, so: just how do you get SYSEDIT to run? I've >tried to add it to a group, but it comes up as a DOS icon. I've tried >creating a .PIF. Either way, I get an app error when I try to run it. Could >someone please mail me the solution? TIA. Sounds strange. Every system I've added it to, all I needed to do was to create a new icon (FILE/NEW from the program manager menu) and point the properties box to C:\WINDOWS\SYSTEM\SYSEDIT.EXE and everything works. If you are getting the generic DOS icon I suspect that you don't have a good copy of the file. Are you pointing the icon's properites data to the copy of SYSEDIT.EXE which Windows SETUP placed in the SYSTEM directory? Are you sure that nobody tried to copy the file directly from the Windows distribution disks without executing EXPAND? >BTW, this would be a good one for the FAQ list, if it's not already there. Agreed. Joe Morris
cmdbyk@pmvax.weeg.uiowa.edu (Karl Boyken) (05/24/91)
Thanks for the replies to my question about how to get SYSEDIT to run.
I hadn't used EXPAND.EXE to extract it from the distribution disk. I guess
not all compressed files have a $ in the extension.
** _My_ views, no one else's--except those I plagiarize. **
Karl Boyken, Project Analyst | "Distant cousins, there's a limited supply,
State Health Registry of Iowa | and we're down to the dozens, and this is why:
Iowa City, IA | big-eyed beans from Venus--oh my, oh my!"
cmdbyk@pmvax.weeg.uiowa.edu | Captain Beefheartjcmorris@mwunix.mitre.org (Joe Morris) (05/25/91)
cmdbyk@pmvax.weeg.uiowa.edu (Karl Boyken) writes: >Thanks for the replies to my question about how to get SYSEDIT to run. >I hadn't used EXPAND.EXE to extract it from the distribution disk. I guess >not all compressed files have a $ in the extension. You shouldn't have had to get it from the disk (in spite of what the Cobb Group's "Inside Windows" says). The Windows installation procedure puts it in the WINDOWS/SYSTEM directory automatically. Joe Morris
ferdie@coyote.datalog.com (fred jarvis) (05/26/91)
On our 486 8 meg system, SYSEDIT works fine in the regular version of WINDOWS, but bombs in the debugging version (SDK) (...AUX...error). Ideas?