331
Programming / Re: files (and directories) not showing up in WPS
« on: March 09, 2017, 02:03:07 am »
actually a couple of files in a directory
OS2 World Community Forum
OS/2, ArcaOS and eComStation - Warp Community
News:
OS2World.com Forum is back !!!
Remember to visit OS2World at:
http://www.os2world.com
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
332
Programming / Re: files (and directories) not showing up in WPS
« on: January 22, 2017, 03:06:25 pm »
BTW Andreas,
Off topic but thanks for your work on NEPM. The package is excellent.
Off topic but thanks for your work on NEPM. The package is excellent.
333
Programming / Re: files (and directories) not showing up in WPS
« on: January 22, 2017, 02:45:46 pm »
Excellent advice!
Removing the EAs - running noEa filename - fixed the problem. The file now appears in the WPS drives/folder on the server.
Thanks for the help.
Removing the EAs - running noEa filename - fixed the problem. The file now appears in the WPS drives/folder on the server.
Thanks for the help.
334
Programming / files (and directories) not showing up in WPS
« on: January 22, 2017, 04:22:17 am »
I recently (last week) installed from scratch ECS beta 2.2. I noticed tonight that I have a file which does not show up in the WPS drives object. It does show up in and command window with a DIR, and it does show up in Larsen Commander and FM/2 stuff, but it does not appear in a DETAILS, or any other WPS view of the directory.
This particular file is on an ECS server which I recently recreated. But I have seen the issue before locally, with entire directories not showing up in the WPS when they do show up other ways, e.g. DIR from command line and in other file managers.
Anyone have any idea what is going on, and how to fix it?
Oh - to make matters even stranger, the file that doesn't show up is a data file, and I cannot set the default action to something other than Properties and have it stick. When I double click on it (in one of the file managers like FM/2 or Larsen) it doesn't follow the association - meaning it doesn't start the program associated with the file. And when i open the properties to change the default action on open to the one associated with the file it ignores the setting and goes back to Properties.
system: ecs beta 2.2. xWorkplace 1.0.11,
This particular file is on an ECS server which I recently recreated. But I have seen the issue before locally, with entire directories not showing up in the WPS when they do show up other ways, e.g. DIR from command line and in other file managers.
Anyone have any idea what is going on, and how to fix it?
Oh - to make matters even stranger, the file that doesn't show up is a data file, and I cannot set the default action to something other than Properties and have it stick. When I double click on it (in one of the file managers like FM/2 or Larsen) it doesn't follow the association - meaning it doesn't start the program associated with the file. And when i open the properties to change the default action on open to the one associated with the file it ignores the setting and goes back to Properties.
system: ecs beta 2.2. xWorkplace 1.0.11,
335
Programming / Re: Crash on Boot with JFS
« on: January 22, 2017, 04:12:46 am »
I ended up reformtting the hard drive and reinstalling ECS 2.2 beta from scratch. I finally decided I would probably spend less time doing that in the long run than trying the other alternatives.
And I found out that you do indeed need SYSINSTX.COM to make the partition bootable, even if you have zipped the system files (e.g. zip -r9S)
But now I have an issue with the WPS - which I will post on a new thread.
And I found out that you do indeed need SYSINSTX.COM to make the partition bootable, even if you have zipped the system files (e.g. zip -r9S)
But now I have an issue with the WPS - which I will post on a new thread.
336
Programming / Re: Crash on Boot with JFS
« on: January 13, 2017, 11:30:05 am »
Yes.
I "secure erased" the Samsung SSD using Samsung's utility which is supposed to remove everything from the drive.
repartitioned (or actually re-volume-ized) the hard drive with different sized volumes using the disk maintenance tool on the ECS boot CD. Formatted the volumes from the command line of the ECS CD,
ran SYSINSTX.COM (which I guess I didn't need to do),
unzipped the contents of all the volumes back onto the volumes,
Ran the ECS install choosing to not format the drive - which means it installs in migration mode,
And after the install completed recopied my CONFIG.SYS (which had been zipped) back, and the problem reappeared.
DFSEE did not say which driver was corrupt. I was using DFSEE on the assumption that the something was wrong with the file system or the master boot record or one of those hard drivey type things that sometimes goes wrong. I was using DFSEE after booting from my maintenance partition.
I "secure erased" the Samsung SSD using Samsung's utility which is supposed to remove everything from the drive.
repartitioned (or actually re-volume-ized) the hard drive with different sized volumes using the disk maintenance tool on the ECS boot CD. Formatted the volumes from the command line of the ECS CD,
ran SYSINSTX.COM (which I guess I didn't need to do),
unzipped the contents of all the volumes back onto the volumes,
Ran the ECS install choosing to not format the drive - which means it installs in migration mode,
And after the install completed recopied my CONFIG.SYS (which had been zipped) back, and the problem reappeared.
DFSEE did not say which driver was corrupt. I was using DFSEE on the assumption that the something was wrong with the file system or the master boot record or one of those hard drivey type things that sometimes goes wrong. I was using DFSEE after booting from my maintenance partition.
337
Programming / Re: Error with Vbox
« on: January 12, 2017, 11:16:41 pm »
That is a good suggestion. Haven't been able to find the problem that way , although I have not made the order of how the drivers appear in the CONFIG.SYS identical. Guess I have to try that.
338
Programming / Re: Crash on Boot with JFS
« on: January 12, 2017, 11:13:56 pm »
Thanks for the advice on full vs quick format. Since it is a SSD my understaning is full format just uses up more of the life of the drive and doesn't buy anything. On rotating media I always due a slow or full format, and for SCSI drives I always do a low level format with the adapter. Learned that (as I have most things in life) the hard way.
My C partition/ drive is 2 GB. I install a number of WinOS2 applications and some of those cannot handle a drive with more than 2 GB. It is easier to keep the boot partition at or less than 2 GB and install the WinOS2 stuff there than it is to use those programs that appear to consume free space on the drive in order to fool the WinOS2 install program.
As a consequence I keep most programs on another partition and keep between 500 MB to 1 GB of free space on the boot drive/partition.
I reformatted by boot drive (C:) today, and unzipped the files I had zipped off the drive, rebooted and got the same error.
So I reformatted the drive again, unzipped the data back to the drive (C:) again, and tried a migration install of ECS 2.2 beta. It booted a couple of times successfully during the install, but when I got to the end of the install I got the same message.
I also tried DFSEE yesterday to fix up the JFS paritition and that sorta of work, but at one point it stopped and complained that a driver was corrupt.
So to recap: I can ALT-F1 boot to a command prompt. I cannot ALT-restore an archive, or ALT-revert to VGA.
I am beginning to think there is some interaction or conflict between the JFS driver/IFS stuff and some other driver or drivers. I just can't for the life of me figure out which. I don't think it is a format issue since reformatting and doing a migration install eventually lead to the exact same error.
Is there some debug/logging facility for either JFS or boot-up that might help point to the conflict?
My C partition/ drive is 2 GB. I install a number of WinOS2 applications and some of those cannot handle a drive with more than 2 GB. It is easier to keep the boot partition at or less than 2 GB and install the WinOS2 stuff there than it is to use those programs that appear to consume free space on the drive in order to fool the WinOS2 install program.
As a consequence I keep most programs on another partition and keep between 500 MB to 1 GB of free space on the boot drive/partition.
I reformatted by boot drive (C:) today, and unzipped the files I had zipped off the drive, rebooted and got the same error.
So I reformatted the drive again, unzipped the data back to the drive (C:) again, and tried a migration install of ECS 2.2 beta. It booted a couple of times successfully during the install, but when I got to the end of the install I got the same message.
I also tried DFSEE yesterday to fix up the JFS paritition and that sorta of work, but at one point it stopped and complained that a driver was corrupt.
So to recap: I can ALT-F1 boot to a command prompt. I cannot ALT-restore an archive, or ALT-revert to VGA.
I am beginning to think there is some interaction or conflict between the JFS driver/IFS stuff and some other driver or drivers. I just can't for the life of me figure out which. I don't think it is a format issue since reformatting and doing a migration install eventually lead to the exact same error.
Is there some debug/logging facility for either JFS or boot-up that might help point to the conflict?
339
Programming / Re: Crash on Boot with JFS
« on: January 10, 2017, 09:19:31 pm »
Andi - thanks for the suggestion. That will probably be the shortest way to fix the problem.
The hard drive is a Samsung 128 GB EVO SSD. It is about 1 1/2 years old.
chkdsk /F reports no errors and no corrections. It appears from CHKDSK that everything is fine.
The hard drive is a Samsung 128 GB EVO SSD. It is about 1 1/2 years old.
chkdsk /F reports no errors and no corrections. It appears from CHKDSK that everything is fine.
340
Programming / Re: Error with Vbox
« on: January 10, 2017, 08:53:30 pm »
My only drive is a Samsung EVO SSDD
What is odd is that CHKDSK /F:3 reports no errors when run from the ECS install CD or when run from my maintenance partition.
I am puzzled why I can ALT-F1 to a command line, which is essentially booting to the C: partition, but when I attempt to boot normally it crashes. I assume booting to the command line is using the same file system as booting normally, meaning I don't think it is really a JFS file system problem.
What is odd is that CHKDSK /F:3 reports no errors when run from the ECS install CD or when run from my maintenance partition.
I am puzzled why I can ALT-F1 to a command line, which is essentially booting to the C: partition, but when I attempt to boot normally it crashes. I assume booting to the command line is using the same file system as booting normally, meaning I don't think it is really a JFS file system problem.
341
Programming / Crash on Boot with JFS
« on: January 10, 2017, 07:13:43 pm »
Rebooted this morning and got the following message
The system detected an internal processing error at
location ##1800:05b5 - 0003:05b5
65535, 9051
JFSBOOT: Error reading in FS
1386090f
Inental revision 14.106_SMP
The system is stopped. Record all of the above information and
contact your service representative.
I can ALT-F1 and boot to the command prompt.
I can boot to a maintenance partition and access the boot drive (C:)
I cannot ALT-F1 and restore my last archive
The crash happens after Loading OS2LVM.DMD appears at the bottom of the screen.
Any ideas on how to fix?
Or how to restore the system?
Alternatives I am considering
1) re-install ECS as an update rather than a new install
2) xcopy C:\OS2\ARCHIVES, xcopy rest of the drive EXCEPT C:\OS2, reinstall ECS as fresh (i.e. format drive), copy back drive except C:\OS2, ALT-F1 and restore my last archive
3) ??
The system detected an internal processing error at
location ##1800:05b5 - 0003:05b5
65535, 9051
JFSBOOT: Error reading in FS
1386090f
Inental revision 14.106_SMP
The system is stopped. Record all of the above information and
contact your service representative.
I can ALT-F1 and boot to the command prompt.
I can boot to a maintenance partition and access the boot drive (C:)
I cannot ALT-F1 and restore my last archive
The crash happens after Loading OS2LVM.DMD appears at the bottom of the screen.
Any ideas on how to fix?
Or how to restore the system?
Alternatives I am considering
1) re-install ECS as an update rather than a new install
2) xcopy C:\OS2\ARCHIVES, xcopy rest of the drive EXCEPT C:\OS2, reinstall ECS as fresh (i.e. format drive), copy back drive except C:\OS2, ALT-F1 and restore my last archive
3) ??
342
Programming / Re: Error with Vbox
« on: January 10, 2017, 07:03:29 pm »
I have the exact same error - same except for the value after the "Error reading in FS"
The system detected an internal processing error at
location ##1800:05b5 - 0003:05b5
65535, 9051
JFSBOOT: Error reading in FS
1386090f
Inental revision 14.106_SMP
The system is stopped. Record all of the above information and
contact your service representative.
This appears to happen after (or while) loading OS2LVM.DMD - at least that is the last thing I see on the screen before the crash.
I can boot to a maintaince partion, or from the ECS CD and access the boot drive (C:). It appears that I can get to all the files.
I can also ALT-F1 and boot to a command prompt.
I cannot ALT-F1 and restore my last archive.
Is there anyway of just replacing the part that is messing up JFS and preserving the rest of the install?
If I xcopy the entire C drive to another partition and re-install ECS, can I xcopy back what I saved and have it work?
Suggestions?
The system detected an internal processing error at
location ##1800:05b5 - 0003:05b5
65535, 9051
JFSBOOT: Error reading in FS
1386090f
Inental revision 14.106_SMP
The system is stopped. Record all of the above information and
contact your service representative.
This appears to happen after (or while) loading OS2LVM.DMD - at least that is the last thing I see on the screen before the crash.
I can boot to a maintaince partion, or from the ECS CD and access the boot drive (C:). It appears that I can get to all the files.
I can also ALT-F1 and boot to a command prompt.
I cannot ALT-F1 and restore my last archive.
Is there anyway of just replacing the part that is messing up JFS and preserving the rest of the install?
If I xcopy the entire C drive to another partition and re-install ECS, can I xcopy back what I saved and have it work?
Suggestions?
343
Networking / Re: ECS client Cannot log on to OS/2 domain
« on: September 29, 2016, 06:56:56 pm »
You are correct. The MMRE driver works. I guess I somehow got the wrong driver hooked up.
Thanks again
Thanks again
344
Networking / Re: ECS client Cannot log on to OS/2 domain
« on: September 28, 2016, 12:47:06 am »
Thanks Douglas for the advice.
The problem indeed appears to be the NIC driver.
I disabled the on-board NIC and installed an Intel 1000 PCI card and "Intel Pro/1000 Network Connection" driver and it now works fine.
The interesting thing is I tried installing the latest R8169 driver from Arca Noae and the system crashed on reboot. When I replaced the R8169.OS2 with the one from my client the system booted OK and appeared to work ok, except for not allowing logons to the domain.
The strange thing is I can now log on to the domain (with the Intel card in the server) using a client machine with the R8169 driver, but the server will not accept domain logons with the same R8169 driver. (my client and server machines have the same motherboards: Asus M5A 78L-M USB3)
Thanks again for your response.
The problem indeed appears to be the NIC driver.
I disabled the on-board NIC and installed an Intel 1000 PCI card and "Intel Pro/1000 Network Connection" driver and it now works fine.
The interesting thing is I tried installing the latest R8169 driver from Arca Noae and the system crashed on reboot. When I replaced the R8169.OS2 with the one from my client the system booted OK and appeared to work ok, except for not allowing logons to the domain.
The strange thing is I can now log on to the domain (with the Intel card in the server) using a client machine with the R8169 driver, but the server will not accept domain logons with the same R8169 driver. (my client and server machines have the same motherboards: Asus M5A 78L-M USB3)
Thanks again for your response.
345
Networking / ECS client Cannot log on to OS/2 domain
« on: September 26, 2016, 09:07:31 pm »
Previous WSEB server (ECS with file sharing removed and WSeB server stuff added) crashed, after running for years.
Built new machine.
Installed ECS 2.2 beta with R8169 network driver.
Deleted file sharing and installed LAN server 5 (WSeB server stuff)
SERVER0 is the only server and also domain controller
Server starts ok. Netlogon service shows to be active in the Lan Server Administration GUI. I can logon to the domain from the server.
But my ECS client (REQ1) cannot log on to my domain.
Netbios appears to running OK on the server because I can NET USE W: \\REQ1\DDRIVE from the server and it works OK (after starting PEER on REQ1)
However I cannot logon to DOMAIN (my domain name) from the requester machine REQ1, and I
I cannot NET USE x: \\server0\cdrive from REQ1 (after login on locally). Error message says network path is not found
Second requester, a laptop, also cannot logon to server
Any suggesting?
Built new machine.
Installed ECS 2.2 beta with R8169 network driver.
Deleted file sharing and installed LAN server 5 (WSeB server stuff)
SERVER0 is the only server and also domain controller
Server starts ok. Netlogon service shows to be active in the Lan Server Administration GUI. I can logon to the domain from the server.
But my ECS client (REQ1) cannot log on to my domain.
Netbios appears to running OK on the server because I can NET USE W: \\REQ1\DDRIVE from the server and it works OK (after starting PEER on REQ1)
However I cannot logon to DOMAIN (my domain name) from the requester machine REQ1, and I
I cannot NET USE x: \\server0\cdrive from REQ1 (after login on locally). Error message says network path is not found
Second requester, a laptop, also cannot logon to server
Any suggesting?