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.


Messages - ddan

Pages: 1 2 3 [4] 5 6 ... 12
46
Hardware / Re: Acer Aspire One Netbook Laptop
« on: 2008.10.21, 22:14:44 »
"None of the Realtek drivers for OS/2 seem to work with it. The driver loads but never talks through the port."

This sounds typical of crossed interrupts; it's the behavior I got with an audio card that was recognized but wouldn't actually play until I re-arranged interrupts (probably by turning off unused COM port in BIOS). Think I'm safe saying that if the driver loads then it recognizes the corresponding hardware present. The SCSI ASC.ADD thread has an ongoing flail about interrupts; seems to be a growing problem for OS/2.

47
Setup & Installation / Re: SCSI ASC.ADD
« on: 2008.10.21, 22:00:23 »
Since most of the interrupt assignment is done by BIOS, you may be able to shorten the try/look cycle by booting DOS from floppy, then running PCI.EXE and checking the table info. I did that (successfully) at least once.

48
RobertM: Thank you. The point is taken here. I just got fed up and decided to run him ragged as politely as I could manage, and without exactly whining to moderators, who I'm sure want to be NICE and keep giving one more chance. I don't in any degree complain about inaction, but when a thread I'm interested in is being clearly diverted to NO purpose, then I consider the action I took to be appropriate.

49
Setup & Installation / Re: SCSI ASC.ADD
« on: 2008.10.20, 20:55:33 »
Okay, I'm at the limit of my knowledge, but clearly interrupt assignment is the problem, and looks to me as though you MUST free up at least one that the card can use. Or, use PCI.EXE and with its list try more re-arranging. I'm assuming you tried swapping slots as Warpcafe suggested.

50
Setup & Installation / Re: SCSI ASC.ADD
« on: 2008.10.20, 18:12:33 »
Newer systems get sticky as to hardware interrupts, which may be impossible to resolve -- with given hardware, because so many ports are hard-wired -- so unless you've tested on the exact same hardware, that's where I'm leaning toward as the essential cause. You can use PCI.EXE to look at the interrupts and see if two or more are shared, always a bad sign for OS/2. If you get down to this, you can try turning off unused COM ports in BIOS, in fact just for a trial turn off everything that can be, to change how the interrupts are assigned. Also, think that OS/2 never uses an interrupt for VGA cards, so turn it off -- if possible. All hardware not strictly necessary for booting turned off (or removed) would likely give an indication as to whether interrupts are the root cause.

51
Patrick: a review of your thread should be enough to demonstrate that the saborion2 program does nothing but entice you off-topic, will never supply you with even wrong advice. I'm sorry to be using your thread to elicit responses from it for my research, but as with any virus, it doesn't give a darn what nuisance it makes for we humans. So I ask and advise you to ignore it, and to also ignore my probing of it.

52
Setup & Installation / Re: 4.52 Convenience Pack CD's
« on: 2008.10.20, 03:59:27 »
Patrick: I'm a bit less amiable than my usual surly self this weekend, for no particular reason (though there is a pesky robot attempting to hijack this thread). Sorry as appropriate. I'm willing to advise, BUT I'm cursed with only being able to tell you what has worked for me. I stick to safe and simple.

Now, here again, I don't believe that you have to bother config.sys at all, and that you're going on a snipe hunt with that, and I'm simply not going to follow you. From what you've said, that you got to LVM, then evidently your hardware doesn't have any problems getting to points that in my experience mean that all will go well once you've done FDISK as I describe.

As I mentioned in my first post, you don't yet believe that the cause is SIMPLE, that LVM isn't able to touch drives that it doesn't like the partitioning of, when its exact purpose is to SET that, but it's typical from what I've seen, one of the charming quirks of OS/2.


53
SMART does report to BIOS, but like many good ideas, it's not used beyond a message because a) BIOS is too simple to do anything with it, and b) what CAN you do with a flaky drive except replace it? -- Actually, think SMART's only intent is to warn of IMPENDING failure. In the too many times (I've acquired many old drives probably abused by wearing FAT tracks out with FAT32) that I've seen those warnings in BIOS, the drive was still working but not reliable. To avoid nuisance, I've turned off the warning, and used at least one 3.2 heavily for months thereafter.  -- But any warning always means BACK UP NOW. -- When a drive dies, usually get nothing but a hang in BIOS, doesn't bother informing BIOS even that it has died. Online report via smartctl.exe gives ambiguous and mysterious numbers. The 250G that I mention elsewhere as slow to report to BIOS yet reliable for data returns some alarming numbers for retries and other items, but at least it's  stable in its behavior.

By the way, I've seen a few HDs "refurbished" by a machine an acquaintance has, but not over a third of those tried. -- On the other hand, I actually trust "factory refurbished" better than "new", besides that they're cheaper. Odds are that any given drive won't have TWO total failures, if it actually had any in the first place (many items returned are perfectly good).

54
Congratulations.

But does leave unanswered whether your drive is flaky. Chkdsk doesn't actually check data of every file of course, only the allocation structures, nor does the hot patching notion always work, besides doesn't inform of its action, so you may have relocated a crucial file to a physically good spot. Keep in mind the possibility if you get file errors down the road; a bad drive can be extremely puzzling. You could try the smartctl.exe that I believe comes with the DANI driver, but I've never been able to make use of its reports.

55
Setup & Installation / Re: 4.52 Convenience Pack CD's
« on: 2008.10.19, 07:08:54 »
saborion2, I make an exception to my own and other's resolve to ignore you to note that you fail the Turing test: no human would make ANY connection between my post and the random news item that you posted. I could write a REXX program that could make your post above. -- Having determined that you are clearly not human, reckon I'm free from here to exercise my wit without any accusation of a personal attack being even possible.

But just this once I'll also be serious with you: what has happened to you? I ran across some of your old posts, and you were cogent and helpful. But now you're just a rather lame troll, neither interesting enough nor clever enough to draw anyone out. I for one would welcome the old saborion2 back...

56
Setup & Installation / Re: 4.52 Convenience Pack CD's
« on: 2008.10.19, 00:29:53 »
Patrick: you're winging it, man! Going where no OS/2er has gone before! NAMECHANGE.EXE in The Google gets 10 hits, none obviously useful. A search of my CP2 installation turns up no such file, nor have I ever encountered it. You may have found a situation where the driver queries the drive for actual size but BIOS believes it's smaller.

Seriously, if you ignore what I know works -- after all, I'm only running CP2 on a 60G that I re-used after DOS 6.22 FDISKing -- and even ignore Saijin_Naib's LONG way that'd eventually work -- then I can only wonder why you've asked for advice.

57
Setup & Installation / Re: 4.52 Convenience Pack CD's
« on: 2008.10.18, 15:30:51 »
Well, Saijin_Naib, another one-line input that subtracts and distracts. Whether your intent or not, that's the effect. Let me be clear that it's the BREVITY of your post that I object to here. Please take time to consider whether you ADD anything with a post. Casually throwing out a possible but expert level solution does not help someone just trying to get the basics going as quickly as possible.

To use DFSEE, one would have to boot DOS at least. So, instead of a minute with its simple FDISK, you advise fooling around with the "exceedingly daunting" DFSEE? -- Of course having downloaded and unpacked it first, then read its extensive detailed instructions, nearly all of which are for exotic options. -- And use of DFSEE is certainly dangerous in the given situation of multiple partitions.

Back to Patrick: if you use DOS 6.22 to prepare a DOS-bootable partition and check that you can actually boot from it, all after should go smoothly with CP2, BUT with multiple partitions, you're going to run into a major tangle. When experimenting with ANY OS, you should always use a spare drive, nothing else on it, all other drives physically disconnected. I'm sure you know, but perhaps got carried away with enthusiasm.

58
Setup & Installation / Re: 4.52 Convenience Pack CD's
« on: 2008.10.18, 02:34:07 »
Old topic, throws everyone encountering it because not obvious. I installed on a 60G without the new drivers on floppy, though installed them later because faster.

First, HPFS has a limit of 64G. You'll need to partition the drive.

Second, more major, whether 30 or 300, you must use DOS 6.22 to get rid of previous partitioning. Just use it to make a 2G partition that LVM finds, then you can resize it up to 64G.

Start here:
http://www.os2world.com/component/option,com_smf/Itemid,63/topic,1042.0/

Particular attention to #10. DOS 6.22 is essential unless you start with a truly bare new drive. Nothing else, no other technique, works that I've found.

59
Setup & Installation / Re: SCSI ASC.ADD
« on: 2008.10.18, 01:17:09 »
Life is too short to fool around with obscure hardware. Ditch it.

I have numerous Adaptec 2940s, in nearly all varieties, that I'd be happy to mail you at cost of postage. PM me.

60
Rexx / Re: Rapidshare nagger
« on: 2008.10.14, 18:27:36 »
As I feared, Rapidshare has changed yet again and returned to delays between allowed downloads. Modified program complete below, too complex to specify edits. Still useful to prompt, though a bit confused when other d/ls are going too. You should hit a key to end the nagging before opening the Rapidshare window; this is intentional for purposes of nagging, but I already dislike it, may modify to watch automatically.

----------------------------------------------------------------------------------
/* PARTY helps maximize downloading from Rapidshare by automated nagging. */
/* Chirps while 'RapidShare:' is in window list, then monitors .part files. */
/* October 2008: changes, 15 minute waits between downloads, NAGS for new. */
/* now less useful with more than rapidshare files being d/led (by FireFox) */

call rxfuncadd 'sysloadfuncs', 'rexxutil', 'sysloadfuncs'
call sysloadfuncs

/* monitor this directory for .part files; trill when appear */
mondir= 'C:\TEMP'
/* sleep period in seconds; sets how often window list is queried */
sleepqwl= 10
/* poll window list for this string every sleepqwl secs */
monwl= 'RapidShare:'
/* seconds to wait after monwl is present before chirping */
after= 75
/* number of sleepqwl loops sets period of checking dir for .part files */
nloops= 3
/* wait minutes between allowed downloading (for small files, may be less) */
between= 15
/* period of NAGGING loop after between file wait, make "ended" sound */
NAGtime= 60

np= 0
lc= 0
do forever
  fl= 1 /* flag used to wait through the normal countdown period */
  do until notpresent = 1  /* monitor window list for text in monwl */
    call sysqueryswitchlist "wl."
    notpresent= 1
    do n= 1 to wl.0  /* check all entries */
      if pos(monwl, wl.n) > 0 then notpresent= 0
    end
    if notpresent = 0 & fl = 1 then do
      say '"'monwl'" present! Sleeping for 'after' seconds before nagging...'
      call syssleep after
      fl= 0
    end
    if notpresent = 0 then do /* after first loop, periodic chirping */
      call chirp
      call syssleep sleepqwl
      lc= 0 /* reset counter so goes right to check / trill */
    end
  end
  if lc = 0 then do
    lc= 0
    rc= sysfiletree(mondir||'\*.part', 'parts.', 'FO')
    say ' 'time('N')'  Previous = 'np'  Now present = 'parts.0
    if np < parts.0 then call trill
    if np > parts.0 then do
      say 'Sleeping for 'between' minutes (assumes only RS files downloading)'
      do n= between to 1 by -1  /* however, since url is placed in EA, it's */
        call charout, n'... '   /* possible to ignore non-RS files; the fix */
        call syssleep 60        /* awaits it becoming a problem for me */
      end
      say
      say 'You MUST hit a key to end the NAG loop!'
      do while chars() = 0  /* _REALLY_ NAG LOOP */
        call ended
        do nag= 1 to 10
          call syssleep NAGtime / 10 /* for faster response */
          call charout, 'Nag '
          if chars() > 0 then do
            say 'Nagging ended; monitoring for 'monwl
            nag= 11
          end
        end
      end
      k= sysgetkey('noecho') /* read just to clear chars() test */
    end
    np= parts.0
  end
  call syssleep sleepqwl
  lc= lc + 1
  if lc > nloops then lc= 0
end

chirp:
do n= 0 to 2; call beep 2500, 50; call syssleep 0.1; end; return

trill:
do n= 0 to 9; call beep 2000 + 200 * n, 50; end; return

ended:  /* once used to this, might have to nag until a key is pressed... */
do n= 9 to 0 by -1; call beep 1000 + 50 * n, 200; end; return

Pages: 1 2 3 [4] 5 6 ... 12