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 - R.M. Klippstein

Pages: 1 ... 10 11 [12] 13 14 ... 21
166
Programming / Another GCC error I can't seem to fix!
« on: January 08, 2016, 09:14:59 pm »
I'm compiling VirtualBox source and after I get "Linking SUPR3HardenedStatic" I get this  No rule to make target error:
No Rule to  make target 'F:/2.1.4-SUP/src/vbox/HostDrivers/Support/$(PATH_SUPR0)/SUPR0.def' needed by F:/2.1.4-SUP/out/os2.x86/release/obj/SUPR0/SUPR0.lib stop
SUPR0.def is located in F:/2.1.4-SUP/src/vbox/HostDrivers/Support/SUPR0.def
Can anybody tell me how to make the needed target so that GCC can find SUPR0.def?

Thanks for any ideas,  klipp

167
Hardware / Re: Kingston memory stick problem
« on: November 25, 2015, 08:14:34 pm »
Thanks guzzi, That worked GREAT!

klipp

168
Hardware / Kingston memory stick problem
« on: November 25, 2015, 07:20:32 pm »
I have a couple of these Kingston memory sticks (16gb) and they work fine on eCS/os2. I just purchased another one and it works fine on Linux and Windoz but not on eCS/os2. Its formatted fat32 like my other sticks but DFSee says: Large Floppy Format - Fat32, First sector is a regular boot record (large floppy format) Large Floppy Format will not work on os/2 or eCS!
  This stick looks identical to my other sticks,  I guess they've changed how they prepare them now for sale. Is there any way I can make it work on eCS?
  Thanks for any advice.   klipp

169
Applications / Re: VBOX does not start anymore
« on: November 12, 2015, 11:54:26 pm »
Hey Andi, You should also be able to enable any valid .vdi file by opening virtualbox and opening "File" and then opening the Virtual Disk Manager and  clicking on add and then telling it where the .vdi file is located. This works for me when I have .vdi files on other partitions.
Hope you're making progress.

klipp

170
Applications / Re: VBOX does not start anymore
« on: November 12, 2015, 09:02:34 pm »
WoW! Its getting complicated! Here's what you might try, Don't delete anything anywhere! But do a new install in the drive you are trying to use, but do the install in a different directory on that drive. I believe the new install will encounter and use the vdi's from the drive they are installed currently on. At any event, FIRST, make sure you have those backed up somewhere safe, you might need to copy them to the home directory (x:/home/default/.virtualbox/VDI) of the drive you are working on.

klipp

171
Applications / Re: VBOX does not start anymore
« on: November 12, 2015, 06:40:34 pm »
You should have a VDI directory  that contains your VBox images. Do a scan of your Hard drive looking for *.vdi's You may have them installed somewhere else. Before you do anything you need to make certian you still have those .vdi files.

klipp

172
Applications / Re: VBOX does not start anymore
« on: November 12, 2015, 03:59:09 pm »
Hi Andi B. Can you tell if you're x:/home/default/.virtualbox is still intact? It should contain a machines and a vdi directory. If these contain the the details of the virtual machines you were using, you might be able to just re-install vbox. At any rate before you do anything, back up x:/home/default/.virtualbox.

klipp

173
Programming / Re: GCC "phase error detected at end of assembly"
« on: November 10, 2015, 04:39:52 pm »
Hey Dave & Daniel, Thanks! Doing more passes solved it,it was NASM!

klipp

174
Programming / GCC "phase error detected at end of assembly"
« on: November 07, 2015, 11:47:30 pm »
Could somebody please explain what this GCC error is trying to tell me.
/src/Vbox/VMM/VMMSwitcher/32BitTo32Bit.asm error: phase error detected at end of assembly
 thanks,  klipp

175
Hi Dave, You were right once more! It was the AHCI Driver. I got rid of it in the phase1 config.sys and the accompanying .add file in phase2 config.sys and the hard drive works fine now! Now that I think about it ACHI Driver was one of the original bugs when BetaII was released a couple of years ago.
   Thanks for bailing me out.

klipp

176
Hey Doug, I plugged the disk into the Lenovo and it worked just as you described. There is apparently something screwed up in my ASUS M4A88TD as it NEVER displays the screen saying "No installable volumes were found on you're system. The volume manager will now start" it goes to “Failed to inialize Logical Volume Management- LVM.EXE –etc”. instead. It never starts the Logical Volume Manager!
I don't see how this can be anything screwed up in either the Hard Drive or the eCS install CD !
Any ideas? I'm going "Brain Dead" over this!

Thanks, klipp

177
Doug, The eCS installer never Fixes the "no partition" problem, I can only quit the attempted install. Supposedly eCS will install a basic partition, but it never does! This is what is causing the problem and I can't seem to figure out how to get eCS to setup that initial partition.
Thanks for the replies & help.

klipp

178
Hi ivan & Doug, This is turning out to be a REAL S.O.B:! First of all, this is on an AMD motherboard (Asus M4A88TD-v EVO/USB3) Drive #1 is WD6400 -Sata, 600gb, Drive #2 is Seagate ST3500413a -Sata, 500gb. The drive I'm trying to add as Drive #3 is WD5000AKS -Sata, 500gb.
  I wiped the drive like Doug said and then tried installing with just Drive's 1 & 3 connected  – no go said there was no partition on drive, I installed 2 partitions, using DFSee one OS2-LVM and a FAT 32, both installed an were usable from both Windoz & Linux. Then back to eCS install which crapped out with the “Failed to inialize Logical Volume Management- LVM.EXE –etc”. So next I Disconnected all drives and just connected the WD5000 and re-ran eCS install – same error! The next thing I'm going to do tomorrow is to try installing the WD500 on a Lenovo Desktop, it only has space for one H.D. So it will be a direct install from the eCS beta II CD.
  It looks to me that there are two different possibilities – The WD500 has problems (even though it works well with Windos & Linux or (God forbid) My ASUS has problems (it is a production machine!)
I guess I'll maybe know more tomorrow after I try it on the Lenovo.
Anybody got any further ideas?

Thanks  klipp

179
I'm trying to add a third hard drive to existing setup, this third drive is a WD500AKS. I can't install eCS-bII on it because of the problem with LVM not being able to be initiated because partitions on this new drive cannot be tagged as startable. I've tried everything I know of to get around this problem, but  – no luck. The latest thing I tried was using DFSee and creating a Primary partition as FAT32 and was able to tag is as startable, but then trying to install eCS to it resulted in the usual Failed to initialize Logical Volume Magament – Please close LVM.EXE – etc!
Hopefully someone knows how to cure this problem, Thanks for  any ideas.
  Ohh, by the way, I also tried removing the other H.D drives and tried to install to just the WD500AKS
and that didn't work either.

klipp

180
Setup & Installation / Re: eCS 2.1 hangs on boot - OS2LVM.DMD
« on: September 17, 2015, 09:52:25 pm »
H i Roderick, Thanks for the reply! I'm still fighting this problem but have a possible solution I'm hesitant to apply. It looks like I've lost the LVM Table for this particular partition (it is 1 of 8 partitions on this hard drive). There are 2 other eCS JFS partitions also on this drive that boot just fine. And yes I can boot from the eCS 2.1 install disk as well. I would like to try the "ReCreate LVM Tables" option, but I don't know if it will screw up the other partitions on this disk, if that happened that would make this small disaster into a really fatal disaster. Does "ReCreate LVM Tables" do just that without loosing any data or messing up other partitions on this same drive?

Thanks again  klipp

Pages: 1 ... 10 11 [12] 13 14 ... 21